3 ms·

> Gitlab CI with your own runners that are forbidden from direct Internet access Yes. Absolutely yes. GitLab (CI) is SO. GOOD. Use it! It's incredibly flexibl

by movedx 5y ago

> Gitlab CI with your own runners that are forbidden from direct Internet access Yes. Absolutely yes. GitLab (CI) is SO. GOOD. Use it! It's incredibly flexible and powerful.

mschuster91 5y ago
I agree, but it has a couple of annoyances. - One thing I'm missing to ditch Jenkins permanently is general purpose job stuff... like "synchronize the production database to integration". Yes there are workarounds but all of them are ugly. - Developing pipelines in Gitlab CI is tedious at best. With Jenkins I don't need to switch between applications during development, with Gitlab I need to switch between browser (to see logs), command line (git) and an editor for the pipeline. - Holy hell it's dog slow sometimes. A runner with Docker executors always builds a whole new instance for each goddamn step of the pipeline, ALWAYS. Jenkins is intelligent enough to re-purpose executors.
- yjftsjthsd-h 5y ago
  > Gitlab I need to switch between browser (to see logs), command line (git) and an editor for the pipeline. Fwiw, you can do it all in-browser with gitlab's editor.
- tpxl 5y ago
  > - One thing I'm missing to ditch Jenkins permanently is general purpose job stuff... like "synchronize the production database to integration". Yes there are workarounds but all of them are ugly. We had a job that backed up some data to a git repo and the gitlab ci cronjobs were really easy to use. It was a simple java -jar, git pull, git commit, git push script and tbh it couldn't have been simpler.
- KptMarchewa 5y ago
  >One thing I'm missing to ditch Jenkins permanently is general purpose job stuff... like "synchronize the production database to integration". Yes there are workarounds but all of them are ugly. Oh, I have a wonderful setup consisting of just 30 different tools. Let's start with proper Kubernetes cluster...

3 ms·

> Gitlab CI with your own runners that are forbidden from direct Internet access Yes. Absolutely yes. GitLab (CI) is SO. GOOD. Use it! It's incredibly flexibl

by movedx 5y ago

> Gitlab CI with your own runners that are forbidden from direct Internet access Yes. Absolutely yes. GitLab (CI) is SO. GOOD. Use it! It's incredibly flexible and powerful.

mschuster91 5y ago
I agree, but it has a couple of annoyances. - One thing I'm missing to ditch Jenkins permanently is general purpose job stuff... like "synchronize the production database to integration". Yes there are workarounds but all of them are ugly. - Developing pipelines in Gitlab CI is tedious at best. With Jenkins I don't need to switch between applications during development, with Gitlab I need to switch between browser (to see logs), command line (git) and an editor for the pipeline. - Holy hell it's dog slow sometimes. A runner with Docker executors always builds a whole new instance for each goddamn step of the pipeline, ALWAYS. Jenkins is intelligent enough to re-purpose executors.
- yjftsjthsd-h 5y ago
  > Gitlab I need to switch between browser (to see logs), command line (git) and an editor for the pipeline. Fwiw, you can do it all in-browser with gitlab's editor.
- tpxl 5y ago
  > - One thing I'm missing to ditch Jenkins permanently is general purpose job stuff... like "synchronize the production database to integration". Yes there are workarounds but all of them are ugly. We had a job that backed up some data to a git repo and the gitlab ci cronjobs were really easy to use. It was a simple java -jar, git pull, git commit, git push script and tbh it couldn't have been simpler.
- KptMarchewa 5y ago
  >One thing I'm missing to ditch Jenkins permanently is general purpose job stuff... like "synchronize the production database to integration". Yes there are workarounds but all of them are ugly. Oh, I have a wonderful setup consisting of just 30 different tools. Let's start with proper Kubernetes cluster...