How do people get started with GitLab CI/CD?
Background:
I've heard anecdotes that people either love getting started with GitLab CI and find it really easy and well documented, or people find it poorly documented and don't know how to start. I'd like to reconcile those viewpoints and understand how easy it really is to get started, and how we can improve things.
What questions are you trying to answer?
How do people get started with GitLab CI/CD? How can we improve getting started?
Are you looking to verify an existing hypothesis or uncover new issues you should be exploring?
My hypothesis is that if someone is coming from another CI tool like Jenkins, and if their use-case is documented, then they find GitLab CI/CD to be really easy. But if they're trying to do something that isn't documented well, or perhaps if they have little CI experience, it can be daunting.
What is the backstory of this project and how does it impact the approach?
What do you already know about the areas you are exploring?
There are a lot of things we do, that we don't have documented. I mean, the underlying primitives are documented, but not how to put it all together. I think we could improve things by providing a better tutorial, perhaps one that spans getting started with GitLab all the way to deploying to production. Also, perhaps providing scenario specific documentation, like iOS development, Java development, and AWS deployments.
What does success look like at the end of the project?