When we introduced native Pipelines authentication for Bitbucket Packages, we made it easier to publish artifacts from CI/CD without relying on personal credentials. Now we’re extending that integration further: package artifacts published through the Pipelines integration can display a Source Pipeline, making it easy to trace an artifact back to the pipeline run that created it.

This gives teams a simpler way to understand where a package came from, investigate issues faster, and verify that published artifacts were produced by the expected workflow.

Why this matters

One of the most common questions after a package is published is simple: which build created this artifact? Until now, answering that often meant manually comparing package versions, timestamps, commits, and pipeline history.

With Source Pipeline linking, that context is available directly from the package artifact view. Instead of piecing together clues across multiple screens, teams can jump straight from the artifact to the pipeline that published it.

  • Faster investigation: Quickly identify the pipeline run behind a published artifact.
  • Better traceability: Connect package versions to the CI/CD workflow that produced them.
  • More confidence in releases: Verify that an artifact was published through the expected automated process.
  • Simpler debugging: Move directly from an artifact to the associated build logs and execution context.

How it works

When a package is published using the Bitbucket Pipelines integration, Bitbucket can associate that artifact with the publishing pipeline and show a Source Pipeline in the package artifact details.

This means teams using the built-in Pipelines integration get traceability at the point where they need it most: right alongside the artifact itself.

If your team is already publishing packages through the Pipelines integration, this enhancement fits naturally into your existing workflow and does not require a new release process.

In the package artifact view, users will now see a Source Pipeline reference for artifacts published through Pipelines. Selecting it takes them to the pipeline run that produced the artifact.

  • Was this artifact produced by the expected branch or commit?
  • What happened in the build that created it?

Things to know

  • The Source Pipeline is shown for package artifacts published through the Pipelines integration. You can learn more in our documentation.
  • The experience is designed to improve artifact traceability without adding extra manual steps for users.

Share your feedback

We’re continuing to improve the connection between Bitbucket Packages and Pipelines so teams can publish, trace, and manage artifacts with more confidence. Source Pipeline linking is a small but meaningful step toward making package provenance clearer and day-to-day workflows simpler.

If you’re already publishing packages through Pipelines, look for the Source Pipeline on newly published artifacts and let us know how it improves your workflow.