Introducing the Jenkins to Bitbucket Pipelines Migration Tool Beta

[#1]

Hi everyone! 

We’re thrilled to launch the beta version of the Jenkins to Bitbucket Pipelines Migration Tool! This tool is here to simplify your CI/CD migration from Jenkins to Bitbucket Pipelines, helping you make the switch to a cloud-based environment with ease.

This community will be your go-to space for support, feedback, and collaboration throughout the beta. Feel free to ask questions, share your experiences, and suggest additional Jenkins plugins you'd like to see supported.

Core Supported Plugins

The tool currently supports following plugins:

• archiveArtifacts

• dir

• echo

• junit

• pwd

• sh

• tar

• timeout

• touch

• unarchive

• untar

Coming Soon

In the next few weeks and months, we’ll be expanding support to include these additional plugins:

• deleteDir

• error

• mail

• sleep

• sshagent

• sshCommand

• sshGet

• sshPut

• sshRemove

• sshScript

• unzip

• zip

To learn more, check out our open-source repository tool and blog post. We’re excited to hear your feedback and help you get started!

[Sreedhar Butta]

Hi Team,

This is fantastic, we are looking for this type of tool to migrate our projects from Jenkins to Bitbucket. Can you please check the below plugins will support in Bitbucket?

1. The below plugins will help manage the script and multiple branches in the same Repo

Pipeline: Declarative 

Pipeline: Multibranch

Email Extension Plugin

HTML Publisher plugin

Pipeline: Job

2. Also Jenkins provides server level access to copy the project specific files, like dependencies, Is this possible in Bitbucket? 

Regards,

Sreedhar Butta

LLA DevOps

[Hamreet Kaur]

Hi @Sreedhar Butta ,

Thanks for reaching out! The migration tool currently supports Pipeline Declarative, Pipeline Jobs, and generally, Pipelines are well-supported. However, we don't support the Email extension at this time. Instead, we support a different plugin called mail. We'll also look into the other two plugins you mentioned and provide an update within the week.

Regarding Pipelines, they come with a built-in caching mechanism that allows you to cache dependencies and transfer them between builds, so users don’t need to redownload them each time. This functionality is provided automatically by Pipelines. Additionally, if you need to extract specific files or directories from a build, you can use the artifact functionality to do so.

Here are links to our support documentation for more details:

• Cache dependencies

• Pipeline artifacts

Let me know if you have any other questions!

[Joshua Tang]

Hi @Sreedhar Butta

To expand on Hamreet's comment, Bitbucket Pipelines offers a feature similar to the multibranch plugin in Jenkins through its start conditions, particularly the branch start condition. At this time, Bitbucket Pipelines does not support the automatic mapping of Jenkinsfiles from different branches into a single configuration with the appropriate start conditions. However, you can use the migration tool with various Jenkinsfiles and then merge them into a single Pipelines configuration with the necessary start conditions.

Regarding the HTML Publisher, Bitbucket Pipelines does not provide a direct equivalent for viewing HTML reports. Nevertheless, you can upload HTML files as artifacts in Pipelines, which you can then download later for review.

I hope this information assists you in your migration process.

Kind regards,
Joshua