Good morning. Some general question: Concerning ci/cd for Spryker projects - what are pros and cons from your point of view of using Jenkins vs Bitbucket ci (or gitlab ci, as it is similar)? Assuming you have one of these two options to choose. Thank you.

IMO Jenkins is not good for docker jobs. Travis has no way to share docker artifactes or caches, so each job download all images from scratch.

Re-adding to thread: To me it really doesn't matter what's the Job Runner exactly since I use other tools to wrap the Jobs / Deployment. The CI tool essentially just becomes a runner. Both Bitbucket CI and GitLab CI are very near the code (Jenkins can be nowadays, too, although it requires a bit of effort) but that's the only "difference" that would matter to me.

@high-pencil-62400 Can you please say a couple of words, why, in your opinion, Jenkins is not good for docker jobs? Thank you.

I’ve a long discussion with them to find a way to share docker images cache between builds. It is not possible they’ve said. So now each our docker job spends 3-4 minutes for downloading images from scratch.

Very precious information. Thx a lot.

I cannot advise on that as I have no XP with docker + gitlab/bitbucket. I remember that is bitbucket is more docker friendly then Travis. But no real knowledge. Sorry.