Stand Alone (CD) Deployment Yaml
Problem to solve
As a developer I want to manage my deployment phase easily.
Intended users
User experience goal
Proposal
Extract the deployment portion from the .gitlab-ci.yml file into a new YAML file called .gitlab-cd.yml
Further details
Today the deploy stage is part of a .gitlab-ci.yml file. The file has become pretty long and any syntax error in any stage or job affects all other jobs. It makes sense to break-off the deployment phase into its own gitlab-cd.yml and be called from a master yml file.
We could even think about using parent-child pipelines for this and to support multiple deployment targets
or possibly using includes from the .gitlab-ci.yml file Sometimes different permissions are needed for deployment - and extracting this into a spereate file may make it easier to accomplish this
Permissions and Security
Documentation
Availability & Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
Links / references
Edited by Orit Golowinski