search

microsoft / cobalt

Infrastructure turn-key solution for app service workloads
MIT License
115 stars 79 forks source link

Variable groups in Fork - N - Go process have hard-coded names and cannot vary by pipeline #240

Open nmiodice opened 5 years ago

nmiodice commented 5 years ago

Description

As a fork n go customer, I'd like to use my own variable groups for my pipeline in order to not have to share variable groups across all pipelines

Acceptance Criteria

Reference: [Done-Done Checklist] (https://github.com/Microsoft/code-with-engineering-playbook/blob/master/Engineering/BestPractices/DoneDone.md)

Also, here are a few points that need to be addressed:

  1. Constraint 1;
  2. Constraint 2;
  3. Constraint 3.

Resources

Technical Design Document Mockups

Tasks

Stories are intended to be completed in a single sprint; if task breakdown creates addition work then team should discuss promoting the Story to an Epic. Reference: [Minimal Valuable Slices] (https://github.com/Microsoft/code-with-engineering-playbook/blob/master/Engineering/BestPractices/MinimalSlices.md)

Reference: [How to Write Better Tasks] (http://agilebutpragmatic.blogspot.com/2012/04/splitting-story-into-tasks-how-to-write.html)

Assignee should break down work into tasks here

awkwardindustries commented 5 years ago

Related discussion: https://github.com/MicrosoftDocs/vsts-docs/issues/3702. Since our pipeline build definitions templates utilize variable values -- such as the environment -- linking to a variable group must be manually done via the Az DevOps portal.