Team-based Pipelines

As a temporary measure to increase the number of parallel deployments to Azure that contain a full service deployment now that we have moved away from using Vagrant, Team Pipelines have been created that contain an environment per team member, identified by their initials.

To provision an environment using the team-based pipelines, the process is mostly the same as /wiki/spaces/RedboxHome/pages/2562764310, with a few minor differences.

The team pipelines that have been created follow our existing team naming convention, for example, Team Alpha have a pipeline called Team Alpha, Team Beta have one called Team Beta, and so on.

The first difference you will notice is that there are now multiple stages defined, instead of a the original "Development1" environment.

The next difference is that when a new release is created, you no longer specify an environment tag.

This is because the environment name is now derived from the stage name. For example, if your name is John Doe, you will have a stage defined called JD. Then when your Azure VM is provisioned, it will be dev-vm-<your initials>.westeurope.cloudapp.azure.com. In cases where initials are shared between people, the environment name takes the first two letters of their first name and the initial of their last name. For example, if there was also a Jane Doe, her environment would be JAD.

Creating a new release will now also require you to approve a deployment to your environment. This is because when a new release is created, it will trigger a release to all environments within the team. For deployments not approved or rejected, they will automatically be rejected after 24 hours.