4 ms·

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.

• flatiron 6y ago
  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
  • sytse 6y ago
    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 https://gitlab.com/gitlab-org/gitlab/-/issues/215675
    • flatiron 6y ago
      Not sure how that would work with our double Jenkins (inside and outside) setup but I’ll check. Thanks!
      • sytse 6y ago
        Awesome! Feel free to comment in the linked issue if you want some help.