-
Suggestion
-
Resolution: Unresolved
It would be useful to be able to access the artifacts of a pipeline from the rest API. We want to write some automation that downloads artifacts from completed pipelines to test them on some physical devices within our network, but as far as I can tell from the API the artifacts are not exposed as part of the pipeline response.
Workaround
Artifacts can be uploaded to the Downloads section of the repository using the following pipe:
They can then be retrieved using a curl call with our API as follows:
curl -sL -u bb_username:app_password "https://api.bitbucket.org/2.0/repositories/workspace_id/repo_name/downloads/build.zip" --output "build.zip"
[BCLOUD-19330] Add pipelines artifacts API endpoint
Re-opening this ticket as we've had renewed interest in exposing artifacts and caches via a REST API.
This is quite an important feature for us. We want to use a build plan that is generated within a Pull Request, in the eventual execution once the Pull Request is merged. To make sure we actually execute what we approved (the PR plan), we want to use the PR Artifact to share the plan with the master pipeline.
This is relevant with the `terraform plan -out=tfplan` set up (https://developer.hashicorp.com/terraform/tutorials/automation/automate-terraform?utm_source=WEBSITE&utm_medium=WEB_IO&utm_offer=ARTICLE_PAGE&utm_content=DOCS#terraform-plan-out-tfplan-input-false).
- PR is created
- PR creates an execution plan (dry-run)
- Plan is approved, and the PR is merged to master
- master branch wants to use this execution run to make sure only what is approved is being executed (as the state could have been changed between merging the PR and opening the PR)
I was looking for a feature like this. We have multiple repositories that have their own build steps, but they all share the same post-build steps. It's possible do this in Jenkins by having a separate job for the post-build steps, and we pass along the required artifacts. It would be nice if Bitbucket Pipelines supported this modular approach to CI/CD. If someone has other suggestions for making pipelines modular, I'm all ears.
This is a feature I was looking for... I have 2 repositories, for frontend and backend code. The backend repo gets deployed and it includes the frontend build as well. To automate this process I want to use the frontend build artifacts into the backend build.
I have asked this question on the community - https://community.atlassian.com/t5/Bitbucket-questions/How-to-use-build-artifact-from-one-pipeline-into-another/qaq-p/2025317#M81669
Hi everyone,
Thank you for bringing this suggestion to our attention.
As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.
Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it.
While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.
Thank you again for providing valuable feedback to our team!
This is a feature I was also looking for.
I was trying to build an integration that would visualise reports coming out of a command run in a pipeline.
I was hoping that the pipeline could artifact the report file, and the integration could pull out the report and visualise it.
Using the downloads API would mean we only get one report from the latest successful build. But if we could get the artifacts from builds themselves, it would be much more powerful, and make setting up this integration easier.