Re:Gitlab.com Is Moving to 13.0
by flatiron on Sunday May 10, 2020 @04:12PM
(#23135751)
Already upgraded our gitlab RDS instance to PostgreSQL 11. AWS makes stuff like that very easy. We use the free version of gitlab and find it very capable. That plus Jenkins plus artifactory we have a nice little setup.
[ Parent
| on HN ]
Re:Gitlab.com Is Moving to 13.0
by AsyncAwait on Sunday May 10, 2020 @04:14PM
(#23135765)
Curious why Jenkins over GitLab's CI/CD?
Re:Gitlab.com Is Moving to 13.0
by ryanmcdonough on Sunday May 10, 2020 @04:18PM
(#23135784)
I’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.
Yep. 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
If 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
Not sure how that would work with our double Jenkins (inside and outside) setup but I’ll check. Thanks!
Awesome! Feel free to comment in the linked issue if you want some help.
Familiarity 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.
If 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.
Can you sell me on it? Never heard of it.
Let me go ahead and outsource that: