Skip to main content

ZERO TO STORES GUIDE

Version Promotion

Tutorial Video

Video recording in progress. Available soon.

You have now successfully deployed and app in the staging environment and created a patch. It's now time to promote the app to the production environment. Let's go over how Codika handles version promotion.

Understanding Version Promotion​

You might ask yourself wether we need to rebuild the app or not when promoting a version. Can't we just use take the ipa and apk files and upload them to the production environment?

The answer is no.

When an app is built, the app gets binded to a specific environment. This means that the app that is built in the staging environment will be different from the app that is built in the production environment.

Promote to Production​

To promote an app from stag to prod you can use the following command :

codika app promote

Selecting the source version​

The CLI will ask you to select from which environment you want to promote. For this guide choose staging. Then you'll see a list of versions that you can promote to production. Since we have only one version in the staging environment, your list will only have one option.

Once you've selected the version the CLI will once again ask you to select which version of that version you want to promote. This is because we have created a patch. You could push the initial version or any intermediate patched version to production. But most probably if you've created a patch you want to push latest patched version to production.

Once you've selected the version, the CLI will start the promotion process.

Promoting the version​

Just like for the release process, the command will create a new branch called release/v1.0.1-prod. This will trigger a new build in Codemagic and use the production configuration files.

Here is what the version summary should look like after promotion :

$ codika app versions

╭───────────┬───────────────┬───────────────╮
│ Version   │     Stag      │     Prod      │
├───────────┼───────────────┼───────────────┤
│ 1.0.1     │       ● (+1)  │       ●       │
╰───────────┴───────────────┴───────────────╯

Patching the production version​

Creating a patch version for the production version is exactly the same as creating a patch for the staging version. Switch to the release/v1.0.1-prod branch using the codika app checkout command. Modify your code, commit and push. Then use the codika app patch command to create a patch.

What's Next?​

Congratulation you've now promoted your app to the production channel. This doesn't mean your app is on the stores yet.

Let's see this in the next section.