CI/CD onboarding
Brain storm
Auto deploy, CI/CD is not as accessible as it could be, right now. I think we should work hard on an onboarding flow that ends with users deploying their project. This will lead us to implement natural improvements. Auto deploy can be a part of this.
If you have a project without CI setup, you should be prompted to "Build or Deploy this project". This will bring you into an onboarding flow with concrete steps
- Deploy immediately or do something custom
- IF Kubernetes is set up, present: "Deploy now (this will commit to your repo)". This will do auto deploy and prefill any information that is need. On GitLab.com, this could deploy to our Cloud (or give the user the option to)
- IF K8s is not set up, present: "Connect to cluster and deploy" => Go to 2
- Offer alternative: Customize deploy => Go to 3 (Default if we can't recognize the project type)
- Choose or setup a cluster
- Set up Kubernetes
- Connect a different cloud / cluster
- .gitlab-ci.yml wizard
- Select your type of project (like current template selection)
- Buttons to create stages, connect to particular clusters, build docker containers, etc
- Connect to cluster => Go to 2
The first step would reduce the amount of clicks of I2P significantly.
Other problems this solves:
- setting up integration with external cluster
- help building .gitlab-ci.yml
- make GitLab.com hosting and external hosting a single experience that can be reused