Multiple Application Environments for a single Global Environment Stage Hot

by Kevin Lee on May 08, 2015

Users typically have multiple Application Environments at a specific stage, i.e. UAT 1, UAT 2, UAT 3. Any of these environments can be targetted to be deployed to. Currently they have to create a Global Environment for each of these Application Environments which does not make sense. It would be better to be able to create multiple Application Environments from a single Global Environment.

  • When a user Adds an Environment they should be able to "split" the Global Environment and select a subset of resources from the Global Environment, to create a number of Application Environments, i.e. UAT 1, UAT 2, UAT 3. The Global Environment will probably be matched to a Resource Group, but the Application Environments should be able to select individual resources from inside this Resource Group (not just the Group itself as happens currently).

    This will also require some changes in the Pipeline functionality. Typically if any of the Application Environments for a stage have been deployed to, i.e. any of UAT 1, 2 or 3 but not necessarily all, then the pipeline can be moved onto the next stage, i.e. Production. 

    Ideas

    Status
  • Please login to view any attachments.

  • We have exactly this problem. A number of environments for each testing phase, only one of which needs to be deployed to to be able to run the testing
    Sam Wrankmore Commented by Sam Wrankmore July 03, 2015
    Top 50 Reviewer  -  

    We have exactly this problem. A number of environments for each testing phase, only one of which needs to be deployed to to be able to run the testing

     

PrintEmail

Recent Tweets