Hey op - Wanted to chime in here some of the things you said aren’t accurate anymore. GitLab CI has the ability to do SSH on the Runners. You deploy a runner a

Hey op - Wanted to chime in here some of the things you said aren’t accurate anymore. GitLab CI has the ability to do SSH on the Runners. You deploy a runner and configure it to use SSH. Then it won’t use containers at all and instead use SSH. The same is true for configuring the runner in a shell capacity. You can then reuse the same environments over and over just like Jenkins does. As for Maven and NodeJS if you’re using containers, you simply build a dockerimage with those baked in, and use it for your builds. GitLab also has container storage that allows your images to work seem less and quickly with the runners. For independent tasks without commits. You can easily configure a gitlab job to trigger only if a pipeline variable is present. Then trigger the pipeline via HTTP POST Request, via the UI or vi an event. I talk about and demonstrate all of these topics on my blog www.lackastack.com - Shameless plug, but I hope it helps.