Skip to main content

Configuring an app for publishing with Ship

Abstract

To publish an app on Ship, you need to build a binary with a Workflow that is exposed to Ship, with the settings properly configured.

To publish an app on Ship, you need to:

iOS and Android apps have their own set of settings on the Settings page; for cross-platform app, both iOS and Android settings must be configured.

Exposing a Workflow's artifacts to Ship

Exposing a Workflow’s artifacts means that the products of the Workflow will be available in Ship: for example, if your Workflow produces an APK, you can publish that using Ship. By default, all Workflows are exposed if they contain the correct version of the Deploy to Bitrise.io Step. If you are happy with that, just leave the field as is.

If, however, you add a Workflow here, only that Workflow will be exposed.

To expose a Workflow’s artifacts to Ship:

  1. Go to your app’s Ship page.

  2. Click Settings in the top right corner.

  3. Go to the General tab.

  4. In the Expose Artifacts From the Selected Workflow to Ship text box, add all the Workflows you need.

    Settings___android-test-test.png

    Be aware that if your app is cross-platform, there are TWO such text boxes: one for iOS and one for Android. Separate the different Workflow names with a comma (for example, build, deploy, release_build_android) .

  5. Scroll down to the bottom of the page and click Save.

Code signing files

Code signing files are required to publish an app to any online store, or to install them to test devices.

On the Settings page, you can choose between different code signing files. You can upload these files - iOS provisioning profiles and certificates, Android keystore files and Service Account JSON files - to the Code Signing tab of your Bitrise app:

In this section:

A Workflow is a collection of Steps, Environment Variables, and other configurations. When Bitrise starts a build, it runs one or more Workflows according to the configuration defined in the bitrise.yml file.

A Step is a block of script execution that encapsulates a build task on Bitrise: the code to perform that task, the inputs and parameters you can define for the task, and the outputs the task generates.

An app on Bitrise represents a Git repository that stores source code and has been connected to Bitrise to be able to run builds on it. As such, a Bitrise app isn't necessarily an actual application: it's just the code on which you run builds with Bitrise.