We are excited to announce the general availability (GA) of the Jenkins to Bitbucket Pipelines migration tool! Since its beta launch a few months ago, we’ve added support for 12 new plugins to simplify your migration process.
Bitbucket Pipelines is a scalable CI/CD tool that is fully integrated into Bitbucket Cloud. With Bitbucket Pipelines, you can:
- Run builds on Atlassian’s cloud runners that scale on demand with no servers to manage. Or connect to your own runners behind the firewall.
- Build DevSecOps workflows with native tools for secret scanning, dependency scanning, and IaC scanning. Customize your workflow further with 100+ out-of-the-box integrations via Pipes.
- Manage code compliance at scale by defining company-wide CI/CD policies, and enforcing them across your organization.
- And since it’s fully integrated into Bitbucket Cloud, developers have real-time visibility into pipeline status for faster feedback loops, so they can get to production faster.
What’s new in this GA release
With the GA release of the Jenkins to Bitbucket Pipelines migration tool, we’ve introduced several key updates to enhance your migration experience.
We’ve added support for 12 additional plugins and allowing parallel stages in Jenkins to be mapped to parallel steps in Bitbucket Pipelines. This improvement makes it easier to migrate even more complex Jenkins pipelines. For more details on this update and to review the full list of supported plugins, be sure to check out our community post.
Additionally, the tool now supports a significantly increased range of Jenkins plugins. Any plugin used in more than 5% of Jenkins instances is now supported, ensuring that the vast majority Jenkins setups can be smoothly migrated to Bitbucket Pipelines.
Plugins used in less than 5% of Jenkins instances are currently not supported for automated migration. In these cases, the tool handles any parts of the pipeline translation using plugins it is familiar with, and then copies the unsupported sections of the Jenkinsfile to the outputted bitbucket-pipelines.yml in its original format. These unconverted elements are clearly marked in the output so users can manually review and translate them as needed.
For situations where you want to automate this manual review/translation process, the tool is built to allow customers to write their own custom translation logic. This feature ensures that Jenkins workflows using custom functionality can still be efficiently migrated.
Additionally, you can share plugin requests in the community space, where we’ll consider user feedback for future releases. This collaborative approach ensures the tool evolves to better meet diverse use cases over time based on customer needs.
How to get started
Ready to begin your Jenkins-to-Pipelines migration? Follow these steps:
- Access the tool: Find the migration tool in our open-source repository.
- Follow the documentation: Our step-by-step guide covers each phase of the migration, reviews its core capabilities, provides setup instructions, configuration tips, and best practices.
Explore further and join the community
Want to explore further? Check out our guided demo below.
Become a part of the Bitbucket Pipelines community for support, collaboration, and latest updates. This community is your go-to space for continuous assistance, feedback, and discussions. If you need help or have plugin requests, just start a post, and we’ll be happy to assist you.
The Jenkins to Bitbucket Pipelines migration tool is built to help teams fully embrace Bitbucket Pipelines, delivering a scalable and cloud-based CI/CD solution. Stay tuned as we continue to enhance the tool to meet the evolving needs of our users!