Environments

For most projects, every branch / commit is automatically deployed to our Development server. However, each Git ref (branch, tag) has its own environment. The environments will be displayed within a GitLab project on certain places:

  • In the corresponding GitLab CI pipeline job

  • In the merge requests

  • Via Operations > Environments

To deploy something on the development server and route the HTTP(S) requests according to this naming scheme, have a look at the Routing requests chapter.

Review Environment

Review environments are created for each feature / hotfix branch. They are available under the following URL scheme:

{branch}-{project}.review.confirm.ch

Important

Review environments are ephemeral and they will automatically be undeployed when the associated branch is deleted.

Testing Environment

The testing environments is created from the master branch. It is available under the following URL scheme:

{project}.testing.confirm.ch

Important

The testing environment is an eternal environment and will never be undeployed. When the master branch is updated, the old testing environment will be replaced.

Release Environment

The release environment is created from a release-* branch. It is available under the following URL scheme:

{project}.release.confirm.ch

Important

The release environment is ephemeral and will automatically be undeployed when the associated release branch is deleted. There’s also only one release environment, thus having multiple concurrent release-* branches will not work.

Live Environment

The live environment is created from a tag. It is available under the following URL scheme:

{project}.confirm.ch

Important

The live environment is an eternal environment and will never be undeployed. When a new tag is pushed, the old live environment will be replaced.