Provide a way to store / view artifacts / assets generated by test run

Issue #13114 resolved
Mike Bissett
created an issue

Many test setups allow you to generate reports such as coverage reports or auto generated documentation, would be nice to be able to view these assets after a test run.

Comments (12)

  1. Matt Ryall staff

    Thanks for continuing to vote and watch this issue.

    We'd really like to have an easy way to do this within Pipelines, but in the meantime some of our crazy engineers at Atlassian have found a reasonable workaround for this using the build status API in Bitbucket.

    Here's how it works in a nutshell:

    1. Upload your test results or other artifacts to an S3 bucket yourself, using our S3 example, AWS CLI or similar.
    2. Create a Bitbucket app password for Pipelines and configure it as an environment variable.
    3. Use curl to link your S3 artifact URLs to your commits in Bitbucket using the build status API, authenticated with the app password.

    You can see a screenshot of the result and detailed instructions on how to do it in our documentation: Publish and link your Bitbucket Pipelines build artifacts.

    I've just written up this document now by piecing together disparate examples, so if there are any glitches with it, please let me know.

    We'll leave this feature request open pending proper support for downloadable artifacts in Pipelines and the build UI.

  2. Aaron Roller

    I too have interest of keeping artifacts around for reviewing coverage reports.

    Such artifacts have a short lifespan of value so it would be reasonable to keep hosting costs down by cleaning up artifacts of a certain age...the most recent pipeline build having a longer lifespan than prior builds.

    Regardless if such storage is developer or Atlassian costs, it would be nice to have the cleanup built in.

  3. Samuel Tannous staff

    Hi all,

    We're pleased to announce that Bitbucket Pipelines now stores artifacts for 7 days after a pipeline completes and makes them available for download via the UI. It'll also store artifacts from failed steps so that you can capture test reports and screenshots from failed tests.

    Screen Shot 2018-07-31 at 5.29.07 PM.png

    Artifacts are configured in the YML file as they have always been. Please see our documentation for examples and further information: https://confluence.atlassian.com/bitbucket/using-artifacts-in-steps-935389074.html

    Also note that this is NOT intended as permanent storage. Artifacts are irreversibly deleted after 7 days. If you require permanent and reliable artifact storage you must continue to use your own storage solution, like Amazon S3 or a hosted artifact repository like JFrog Artifactory.

  4. Log in to comment