Deploying a Branch

Deploying a Branch can be very useful if you want to apply a small fix to the currently deployed version in the Production system. 

Please note, this doesn't work on Windows.

However, this isn't built into the Deployment App in Backstage or our Continuous Integration system but you can still deploy a certain branch on Staging and Production.

To deploy a branch with JavaScript or CSS changes, you must build a release yourself which you can do by following the steps below. If you only have changes in the PHP stack, you can skip step one (Preparing a Build). 

Prepare a new Build inside your VM or Docker container by executing the below command:
ant package

Usually, files are generated that are unstaged and might not be committed if they're not added during this step.

Create a Git change set with freshly built assets by executing the below command on the host (your computer):
git add . && git commit -m 'Built assets for release'
Create and Publish a Git tag for the current HEAD by using the below command. The deployable tags must have the following format: /^\d{4}\.\d{2}\.\d{2}\.\d{2}\.\d{2}$/, e.g. 1981. We generally use the current date for the release tags.
git tag `date '+%Y.%m.%d.%H.%M'` && git push --tags

This is the most important step and must be executed before deploying anything.

Deploy this tag to the Staging or Production system by using the deploy curl command found in the Deployment App in Backstage. This tag will not be listed in the drop downs, so you have to use the curl command or the SlackBot if it's active for you.

‹ Back to Article List

Next Article ›

Go Live Preparation

Still need help? Contact Us Contact Us