You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Does anyone have an experience with moving from Jenkins to bitbucket pipelines?
I would like to know about the transition, advantages, disadvantages, issues that raise in the middle or others.
Using Bitbucket Pipelines, you have your CI/CD process codified - meaning you benefit from a documented process that sits with the code itself, as well as any code review/PR process you have configured
Depending on your architecture, one of the downsides can be moving away from the Jenkins controller/agent model if you're not using containers or similar. If your Jenkins setup has a remote agent pulling code/artifacts from your Bitbucket repo, then copying files around (say in to your web server doc root) then achieving the same via Bitbucket pipelines would mean something like allowing remote access (ssh/sftp etc) to that server which may not be possible/advisable. With Bitbucket pipelines, it'd be ideal to run any tests, build artifacts then package what's needed in to a more Cloud native approach (build and deploy a new container revision, deploy a zip to S3 which triggers a deployment action within AWS or something).