CODEWITHSUNDEEP
azure-pipelines
Matt M
Matt M

Reputation: 3779

Environments in VSTS releases

I'm trying to wrap my head around how we can configure our release management to use Environments. Let's say our architecture has an Angular front-end and WebApi projects that sit on the web server and a WCF project that sits on our app server (so 3 projects total). In addition, we have Test, Stage, and Production environments.

Am I correct in my understanding that we would create 1 Release definition with 3 environments. Would each environment definition consist of the tasks to deploy the necessary artifacts for all 3 projects to the necessary folders/servers for that environment?

Is this how it should work? The documentation isn't bad, but I need more of a real world, concrete example.

Upvotes: 0

Views: 391

Answers (1)

starian chen-MSFT
starian chen-MSFT

Reputation: 33708

This scenario is similar to database and web tiers of an application.

These should be modeled as a single environment because you want the two to be in sync. If you model these as separate environments, you risk deploying one build to the database environment and a different build to the web tier environment.

Not clear about the relationship between WCF project with other projects. If Angular app needs retrieve data from WCF too, you can create a release definition with 3 environments (Test, Stage and Production), then the workflow will be like this:

  1. Deploy these projects to corresponding servers for Test environment
  2. After testing, approve to deploy to Stage
  3. Approve to deploy Production

If there isn’t the relationship between WCF project with other projects, you can create another release definition with 3 environments for this project.

Upvotes: 1

Related Questions