Attach any file as an Artifact to the Build

Japanese translation unavailable

This page has not been translated into Japanese yet - we apologise for the inconvenience! If you’re interested in helping us out, feel free to translate any article in the jp folder of the DevCenter repository and open a PR!

このページは日本語への翻訳がまだ完了しておりません。ご不便をおかけして申し訳ございません! もしお手伝いできる方がいらっしゃれば、ご自由にjpフォルダの記事を日本語に訳していただき、PRを開いてください

For this example we’ll attach the OS X system.log to the Build as an Artifact, but this works for any file, even for ones that you generate during the build, you just have to replace the example path we use (/var/log/system.log) with the path you want to deploy. You can of course use Environment Variables in the path too, like $HOME/.

Deployed Artifacts appear on the Build’s page, in the Artifacts & Apps section, and anyone who has access to the Build page can download it from there.

To do this:

A YAML configuration example of the step & input:

    - deploy-to-bitrise-io:
        - deploy_path: "/var/log/system.log"

That’s all, your next build will attach the OS X system log file to your build - you’ll see it at the top of the Build’s page.

By default the Deploy to will always run

By default the Deploy to will always run, even if a previous step fails, so you can deploy failed step/tool logs too.

Deploy a directory

The Deploy to step accepts both file and directory path as its input, but by default it does not deploy files recursively, from sub directories if you specify a directory as it’s deploy_path input.

If you want to do that and deploy the whole directory with every sub directory and the files in the sub directories, you have to enable the “Compress” option of the step.

In this mode the step will compress (zip) the whole directory, and deploy the compressed file, instead of deploying files one by one.

An example configuration:

    - deploy-to-bitrise-io:
        - deploy_path: /deploy/this/directory/recursively
        - is_compress: 'true'

Note: as every input’s, is_compress’s value have to be a string, that’s why _true_ is surrounded with quotes.

Using more than one Deploy to step

You can use as many Deploy to steps as you want to, even in a single build / workflow. Alternatively of course you can move all the files you want to deploy into a single directory, and deploy that directory with the step, it’s up to you to decide which solution works best for you.