jl-gitlab

Hey there, product manager at GitLab for review apps here. I'd love to hear about the warts that you ran into that caused you to move to k8s. We're always working on improving the product and feedback like yours is really the most valuable thing for us.

If you have any advice or learnings for us, feel free to jump into that issue. :)

CI/CD product manager from GitLab here. We're actually already looking at adding this - we're starting with some experimentation in our internal item at https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues.... Some folks here at GitLab already have this set up and working at a small scale, so it's certainly possible (with a couple caveats.)

Check out that issue for more info.

The very next thing you teach them after the theoretical knowledge of how the pieces move is to sit on their hands, to avoid making impulsive moves.

No worries, I understand how you could come to that conclusion. I've opened up an issue to see if we can make that more clear: https://gitlab.com/gitlab-org/gitlab-ce/issues/52144

The documentation link you shared was for AutoDevOps, a different (but related) feature from CI/CD. It's a build and deployment solution specifically for Kubernetes/Containers, which is why it has those requirements.

GitLab CI/CD documentation can be found at the link that I shared, and it can build and deploy truly all kinds of software, and does not require k8s.

Hey there, I'm the product manager for CI/CD at GitLab. AutoDevOps is one of our more advanced features to get up and running in a k8s environment quickly, but is not required if you just want basic CI.

Our documentation on getting started with CI/CD is here: https://docs.gitlab.com/ee/ci/

Interesting idea. We already sort of have a special-case MR (WIP) where merge is disabled until the work-in-progress status is removed. It could be interesting to have an RFC equivalent where no merge is clearly ever intended, but you still get the conversation flow, review app, and so on.

Thanks for the feedback, that's awesome to hear!

Hey, PM at GitLab for CI/CD here. We're making a lot of investments in both the infrastructure supporting gitlab.com as well as the functionality and reliability of the CI pipelines themselves, including looking at intermittent issues and other patterns of reports coming in through our support team.

I'm really glad to hear you're excited about the way we integrate everything together.. that's something we're really proud of with our product and an area we're going to continue to invest in as well. This year we're going to explicitly plan things out so that we're building a breadcrumb trail back for all users to start taking advantage of those more advanced features.

You can check out the rest of our vision for 2019 here: https://about.gitlab.com/direction/verify - would love to hear your thoughts and feedback on it.

To add on, we are actively working on balancing how we deliver new and deep solutions, CI in particular is an area where we want to provide better solutions for more complex problems (as well as address some of the challenges like hung builds or other issues people are running into.) You can read about our vision for CI here: https://about.gitlab.com/direction/verify/

I'd also be up for a chat sometime if you'd like to talk about some of the issues that are impacting you and what we might be able to do to help. twitter.com/j4lenn

Really sorry to hear you've had that experience. I'm the PM for CI and we're really proud of how our CI product in particular has been rated by industry analysts, and how we've maintained interoperability, though of course that doesn't speak to where you've struggled with our solution. If you'd like to chat about it sometime I'd definitely be up for it.