6 ms·
Curious why Jenkins over GitLab's CI/CD?
by AsyncAwait 6y ago
Curious why Jenkins over GitLab's CI/CD?
- ryanmcdonough 6y agoI’d imagine they were already using it with their prior SC setup and didn’t want to move source control and everything else at once.
- flatiron 6y agoYep. We were svn using “beanstalk” when I joined our company and pushed for a git migration. But we already had Jenkins running with tons of stuff set up on cloud bees. Then they kicked us off for some reason (forgot why) so it started our own migration to AWS
- sytse 6y agoIf you are still considering moving CI from Jenkins to GitLab we're publicly testing a Jenkins Wrapper to make it more gradual to move https://gitlab.com/gitlab-org/gitlab/-/issues/215675 https://gitlab.com/gitlab-org/gitlab/-/issues/215675
- cgidriver 6y agoIntegration errors are hard to chase in Gitlab (For example: Something went wrong while creating your Kubernetes cluster Unexpected status; ROLLBACK_FAILED) - this does not give the user any information. Perhaps I could get some help here on this.
- flatiron 6y agoFamiliarity mainly. We have a dual Jenkins setup (one internal one at our clients site) so we have a metric ton of Jenkins stuff from years and years of work. I can also write Jenkins pipelines in my sleep from doing it so often and have probably read about GitLab’s yaml format for a few hours. Maybe one day we think about getting rid of Jenkins but I am quite fond of it.
- unixhero 6y agoIf anything upgrade from Jenkins to a proper workflow manager, such as Apache Airflow! Edit: I realize it might be more suitable for data pipelines than continuous integration.
- orlovs 6y agoWhen you have got a lot of things already ready written