Deploys build artifacts to make them available for the user on the build's Artifacts tab. Sends test results to the Test Reports (build's Tests tab). Uploads Pipeline intermediate files to make them available in subsequent Workflows and also uploads Bitrise and user generated html reports.
The Step accesses artifacts from a directory specified as the $BITRISE_DEPLOY_DIR where artifacts generated by previous Steps gets stored.
These artifacts are then uploaded on the Artifacts tab of any given build. For installable artifacts, such as IPAs or APKs, the Step can create a public install page that allows testers to install the app on their devices.
You can also use the Step to notify users about the build. If you wish to use the Test Reports, you must add this Step in your Workflow since the Step converts test results to the right format and sends them.
The Step can also share Pipeline intermediate files. These files are generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.
Also it collects and uploads all of the html reports located in the BITRISE_HTML_REPORT_DIR folder.
$BITRISE_DEPLOY_DIR Env Var which is exposed by the Bitrise CLI.
If you provide a directory, everything in that directory, excluding sub-directories, gets uploaded.
If you provide only a file, then only that file gets uploaded.
To upload a directory's content recursively, you should use the Compress the artifacts into one file? which will compress the whole directory, with every sub-directory included.everyone. If you wish to notify based on user roles, add one or more roles and separate them with commas, for example, developers, admins. If you don't want to notify anyone, set the input to none.true by default. It creates a long and random URL which can be shared with those who do not have a Bitrise account.
If you set this input to false, the Notify: Emails input will be ignored and the Notify: User Roles will receive the build URL instead of the public install URL.true, you can compress the artifacts found in the Deploy directory into a single file.
You can specify a custom name for the zip file with the zip_name option. If you don't specify one, the default Deploy directory name will be used.
If the Compress the artifacts into one file? is set to false, the artifacts in the Deploy directory will be deployed separately.BITRISE_PERMANENT_DOWNLOAD_URL_MAP so that the next Step can render the output.
The next Steps will use this input to generate the related output in the specified format. The output contains multiple permanent URLs for multiple artifacts.
Provide a language template description using https://golang.org/pkg/text/template so that the Deploy to Bitrise.io Step can build the required custom output.The Files to share between Pipeline Workflows input specifies the files meant to be intermediate files shared between the Pipeline Workflows. When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the Files to share between Pipeline Workflows input.
The inputs path:env_key values will be saved together with the file and later automatically reconstructed by the Pull Pipeline intermediate files Step.
You can use a shorthand of just env_var for $env_var:env_var, when the env_var holds the path to the file(s) you want to share with subsequent Workflows.
The directories you specify will be archived and uploaded as a single file.
If you wish to use any of the Step’s debug features, set the following inputs:
Deploy directory name is used.
Please note that this input only works if you set the Compress the artifacts into one file? input to true.true, the Step prints more verbose logs. It is false by default.false, no email notifications will be sent.Uploads binaries (.ipa / .pkg files) to App Store Connect.
