Skip to main content

Build artifacts online

Abstract

A build on Bitrise can and often does produce artifacts: for example, test reports, images, executable binaries. If you select a build of your app, on the Artifacts tab, you can check out the artifacts which have been generated during the build.

A build on Bitrise can and often does produce artifacts: for example, test reports, images, and executable binaries. To check out the artifacts generated during a build, just click on the build and then go to Artifacts.

builds-artifacts-tab.png

All file types are supported and will be available in Artifacts. Depending on the type of the file, you can either view your artifacts inline if you click on the eye icon or download them to your local computer.

There is no limitation on the number of files deployed to Artifacts per build. There is a limitation, however, on the file size which is 2GB per file.

Deploying files into artifacts

Artifacts are deployed into the Artifacts section in your build’s page with the help of the Deploy to Bitrise.io Step. It deploys all the files which have been generated during the build and stores them in the $BITRISE_DEPLOY_DIR directory.

To deploy the artifacts, insert the Deploy to Bitrise.io Step AFTER the Step(s) that generate the artifacts or even better if the Deploy to Bitrise.io Step is at the very end of your Workflow.

Put the Step in the right place

Add the Deploy to Bitrise.io Step in the right place. If you insert the Step before other Steps that generate files during the build, then Deploy to Bitrise.io will have nothing to deploy.

Note that the content of any sub-directories found in the deploy directory will not be displayed in the Artifacts section of your build. You can, however, compress your artifacts into a zip file if you modify the default false value to true in the Compress the artifacts into one file field in the Deploy to Bitrise.io Step. This will compress the whole directory along with its sub-directories and deploy to Artifacts.

Modifying the target directory path

You can modify the target directory path to another one but make sure you reference the same directory paths in other Steps of your Workflow to ensure that the generated files get collected to the same directory.

Viewing artifacts if your build has failed

With the Run if previous Step failed toggle enabled, you can access your build artifacts - only those that have been successfully generated - even if your build has failed. For example, you can detect bugs in your failed build by looking into the generated test report files.

Who can access build artifacts?

The artifacts at Artifacts are accessible for everyone who is the owner, admin, developer, tester/QA of the app. Besides these roles, if you keep the default config of the Enable public page for the App feature, then anyone who receives the URL, will be able to access your app and its artifacts.