Work on onboarding and adoption is needed to actually deliver on the vision of people using GitLab for getting their ideas into production. The demo is great, but we have a long way to go to make it easy for everyone to use. This should be fleshed out and planned for immediately.
There's a grab-bag of ideas already. The trick is to figure out which minimal set of these (or new ideas) will make the most difference and result in a clean flow from beginning to end.
Auto Deploy has been a great experiment, but feels like it's hitting the end of its runway in value, until we improve things elsewhere. In particular, we can make it easier to create and manage kubernetes clusters, or better yet, provide some amount of compute for free to make it really easy to get started.
We can improve Auto Deploy, now in Auto DevOps.
- Auto DevOps++: #38366 (closed)
But while Auto Deploy makes a great demo, it's opaque, not configurable, and doesn't teach people how to grow their CI/CD usage over time. We can make using CI/CD Pipelines easier. Make it easier to create
.gitlab-ci.yml, or make it unnecessary to create one at all.
- Auto DevOps (beta): #37115 (closed)
- Auto DevOps++: #35712 (closed)
- New project from template (rails, node/express, spring): #32420 (closed)
- Pro-active .gitlab-ci.yml creation: #28351
- CI/CD onboarding: #31166 (closed)
- Implied gitlab-ci.yml: #34777 (closed)
- Make auto deploy "zero click" configuration: #28908 (closed)
- Enable CI/CD with checkboxes: #32553 (closed)
- Show job configuration: #30737
- CI language generator (wizard): #14266
- Visual editor for
- GUI builder comes to mind immediately to help here, with perhaps an integrated samples library that could eventually have intelligence eventually to suggest steps or even a full YML.
- Long shot, but could we have an importer for other CI tools? Detect a Travis CI file and convert?
- Notification emails for Auto DevOps:
We could also make it easy to make the other components of a good CI/CD pipeline such as:
- Creation of Docker containers
- Since we are starting from (I think) an assumption we are running on a cloud provider here, could we help people create Dockerfiles? If we do this, CI may still be manual but CD could get really easy? (Note, we now have Dockerfile templates)
- Creation of Helm chart
For ChatOps onboarding, we need:
- Instance-wide chat integration: #32713
- Group-wide chat integration
- Support multiple projects with single chat trigger word: #24770
Application Performance Monitoring onboarding (Prometheus):
- Single click deploy of Prometheus to k8s cluster: #28916 (closed)
- Leveraging proxy API to seamlessly connect to internal k8s resources (like Prometheus) #30480 (closed)
- Then of course the 9.3 main deliverable of autodetecting and adding metrics: #30369 (closed)