Releases

A release is always exciting because we will push new code online. Although we have already tested the release thoroughly, we have established some rules to quickly resolve any issues that may arise after a release.

Requirements

A release

1. Can only be carried out in consultation with the consultant/support specialist or customer.
2. Must be performed before 14:00 on working days.
3. Should never be performed on a Friday.
4. Must be tested after the release.

How to Prepare a Release

The following steps ensure that a release meets the requirements.

Consult with Your Colleague

Make sure you know exactly what issues or functionality should be included in the release. Discuss this with the responsible consultant or support specialist.

Merge to the Default Branch

Depending on whether the theme in question is a Mosaic Templates theme, make sure to always merge your branch to the default branch in GitLab with everything related to this release.

How to Release a Mosaic Templates Theme

After merging your branch into the default branch, the process differs slightly for Mosaic Templates themes. The following steps outline what to do after merging your branch into the develop branch.

1. Merge develop into master.
2. Go to the latest pipeline as a result of the merge in step 1.
3. Wait for all the jobs to finish running (except for the job deploy to production).
4. Open the job deploy to production.
5. Click on Run job.
6. Optional: If the changes made include widget changes, copy them from test to production.
7. Check the production environment when the job is done.
8. Make sure to test if everything has been released as expected.
9. Inform the consultant of the successful release.

How to Release a Regular Theme

After the previous preparations, you are ready to release. This part is straightforward.

1. Merge the default branch (usually develop) into master. (If the default branch is master, you can skip this step.)
2. Go to the project's pipelines.
3. Select the master pipeline being run.
4. Select the deploy master to production job.
5. Click on Run job.
6. If the changes made include widget changes, copy them from test to production.
7. Check the production environment when the job is done.
8. Make sure to test the release.
9. Inform the consultant of the successful release.