Publish artifacts to Cloudsmith directly from Bitbucket Pipelines
Cloudsmith provides an officially maintained Bitbucket pipe that drops straight into your existing pipeline YAML. Authenticate once with an API key, declare your format and repository, and every tagged build pushes your artifacts to Cloudsmith automatically - no custom scripts, no manual uploads.
How we support Bitbucket Pipelines
Why teams integrate Cloudsmith with Bitbucket Pipelines
Frequently asked questions
Add the pipe as a step in your bitbucket-pipelines.yml file using the cloudsmith-io/publish identifier. You specify your Cloudsmith repository, API key variable, package format, and package path. The pipe is available by default in all Bitbucket workspaces with no installation required.
Cloudsmith supports over 30 package formats including Python, npm, Docker, Maven, Debian, RPM, NuGet, Helm, Cargo, and more. You specify the format using the PACKAGE_FORMAT variable in the pipe configuration, and Cloudsmith handles indexing and serving.
Store your Cloudsmith API key as a secured repository or workspace variable named CLOUDSMITH_API_KEY in Bitbucket. Secured variables are masked in logs and injected at runtime. For tighter scoping, create a Cloudsmith service account with only the permissions your pipeline needs.
Yes. The Cloudsmith Publish pipe is part of Bitbucket's officially maintained pipes collection. It is maintained by the Cloudsmith team and updated as new features and format support are added to the platform.
Yes. If you prefer more control, install the Cloudsmith CLI in your pipeline step and use cloudsmith push commands directly. This approach works for all formats and gives you access to advanced options like tagging, retention overrides, and bulk uploads.
Yes. Every package uploaded to Cloudsmith is automatically scanned for vulnerabilities and evaluated against your active policies. You can configure Cloudsmith to quarantine or block packages that fail checks before they become available to downstream consumers.
Yes. Cloudsmith repositories are independent of your Bitbucket workspace structure. You can publish from any number of Bitbucket repositories to the same Cloudsmith repository, or route artifacts to separate repositories based on team, environment, or format.
Cloudsmith records metadata for every uploaded package including the upload source, timestamp, and user or service account that performed the action. You can query this via the Cloudsmith UI, API, or audit logs to build a full provenance trail from pipeline run to deployed artifact.
Yes. You can mirror Bitbucket's environment stages in Cloudsmith by using separate repositories for development, staging, and production. Packages can be promoted between Cloudsmith repositories without re-uploading, preserving artifact integrity and keeping bandwidth costs low.
Full setup instructions, YAML examples, and configuration options are available at docs.cloudsmith.com under the Bitbucket Pipelines integration guide. The official pipe README on Bitbucket also includes variable references and worked examples for common formats.