Faster, Easier Initial CD Setup
Problem to Solve
We should have an easy way (or ways) to deploy a project on GitLab. There are at least two situations to consider:
- Open source (or team-private) project on GitLab
- Open source project on GitHub(/Bitbucket)
Which leads to considering options in both the GitLab interface, and a button that can be placed in a Readme, similar to Heroku Buttons.
Since we have Auto DevOps, we could imagine just forking the project as enough to trigger Auto DevOps to run, which would result in a deployment (#35674). But we could also consider making it more explicit, with a
Deploy button. That button could even work external to an existing CI/CD pipeline, maybe just focus on the deployment part and skip the CI part. I mean, it's an open source project you just want to deploy, do you really need to run tests and code quality on it first? You just want it deployed. So it's not the same scope as Auto DevOps.
To start, it might have to be a fairly laborious process as you'll have to bring your own cluster or set up a new GKE cluster. But we could have a goal of reducing the total number of steps over time, down to zero steps where everything is available .
(Include use cases, benefits, and/or goals)
What does success look like, and how can we measure that?
(If no way to measure success, link to an issue that will implement a way to measure this)