Bitbucket and digitalocean update warns of incompatible versions

[Koen De Groote]

I'm seeing the following warnings in the plugin update list: 

These seem to be referencing eachother. Seems like recursive dependencies, or at least in the need for updates.

Reading the release notes, it seems the main cause of this, is this plugin update: https://plugins.jenkins.io/cloudbees-bitbucket-branch-source/releases/#version_936.0.1

It says that if you have version at least 2.x and newer, it should all be fine and you can just update. It seems that these instructions were written for people still running version 1.8 and thus have not updated in 8 years.

Going over the issue tracker, someone made an issue saying they updated but the warnings persist: https://issues.jenkins.io/browse/JENKINS-75606

Which gets me worried. Considering my version numbers, can I just update and everything will be fine? Or is there an issue still ongoing?

Regards,

Koen De Groote

[Mark Waite]

On Friday, May 23, 2025 at 1:13:19 PM UTC-6 Koen De Groote wrote:

I'm seeing the following warnings in the plugin update list: 

These seem to be referencing eachother. Seems like recursive dependencies, or at least in the need for updates.

It is not recursive dependencies.  Blue Ocean plugin depends on the Bitbucket Pipeline for Blue Ocean plugin.  The Bitbucket Pipeline for Blue Ocean plugin depends on the Bitbucket Branch Source plugin.  The Bitbucket plugin optionally depends on the Bitbucket Branch Source plugin.

 

Reading the release notes, it seems the main cause of this, is this plugin update: https://plugins.jenkins.io/cloudbees-bitbucket-branch-source/releases/#version_936.0.1

It says that if you have version at least 2.x and newer, it should all be fine and you can just update. It seems that these instructions were written for people still running version 1.8 and thus have not updated in 8 years.

Bitbucket branch source plugin 936.0.1 switched from the Apache HTTP Client 4 API to the Apache HTTP Client 5 API in pull request 963.  I believe that the Bitbucket branch source plugin maintainer wanted to alert users that they may not be able to revert to a version of the plugin before 936.0.1 after upgrading to 936.0.1 because job definitions are changed by the switch from Apache HTTP Client 4 API to the Apache HTTP Client 5 API.

I believe that is why the warning text includes the phrase "you may not be able to cleanly revert to the prior version without manually restoring old settings".

 

Going over the issue tracker, someone made an issue saying they updated but the warnings persist: https://issues.jenkins.io/browse/JENKINS-75606

Which gets me worried. Considering my version numbers, can I just update and everything will be fine? Or is there an issue still ongoing?

I'm not aware of any ongoing issue related to plugin upgrades.  There are issues reported on the Bitbucket branch source plugin.  You may want to review those issues to assure yourself that none of them affect your use of the plugin.

I believe that the compatibility warnings are intended to help Jenkins administrators decide how much they need to test a plugin upgrade.  If your Jenkins controller is business critical, then you should test more.  If your Jenkins controller is used casually and can be offline if there is an issue, then less testing may be needed.

Mark Waite