-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins 2.401.3
Upgrading the Bitbucket Server Integration plugin from 3.5.0 to 3.6.0 caused the "Manage Old Data" page of Jenkins to show notices about "branchName" in several builds. This seems to have been caused by https://github.com/jenkinsci/atlassian-bitbucket-server-integration-plugin/pull/403 (for JENKINS-71289), which modified BitbucketRevisionAction.java to replace private final String branchName with private final String refName.
Please document in the 3.6.0 release notes of the plugin:
- That Jenkins will show "branchName" as old data.
- Whether there will be problems if a Jenkins administrator downgrades the plugin back to 3.5.0 or lower, after some builds have been done with 3.6.0 or higher.
Please also consider whether hpi.compatibleSinceVersion should be set as described in Mark a new plugin version as incompatible with older versions.
- is caused by
-
JENKINS-71289 Build status URL for tag builds sent through as refs/heads/refs/tags/<tagname>
-
- Fixed but Unreleased
-
- links to
[JENKINS-71770] Document "branchName" serialization compatibility between Bitbucket Server Integration 3.5.0 and 3.6.0
Kalle Niemitalo
created issue -
Kalle Niemitalo
made changes -
| Summary | Original: Document the "branchName" compatibility between Bitbucket Server Integration 3.5.0 and 3.6.0 | New: Document "branchName" serialization compatibility between Bitbucket Server Integration 3.5.0 and 3.6.0 |
Kalle Niemitalo
made changes -
| Link |
New:
This issue is caused by |
Kalle Niemitalo
made changes -
| Description |
Original:
Upgrading the Bitbucket Server Integration plugin from 3.5.0 to 3.6.0 caused the "Manage Old Data" page of Jenkins to show notices about "branchName" in several builds. This seems to have been caused by [https://github.com/jenkinsci/atlassian-bitbucket-server-integration-plugin/pull/403], which modified BitbucketRevisionAction.java to replace {{private final String branchName}} with {{private final String refName}}.
Please document in the 3.6.0 release notes of the plugin: - That Jenkins will show "branchName" as old data. - Whether there will be problems if a Jenkins administrator downgrades the plugin back to 3.5.0 or lower, after some builds have been done with 3.6.0 or higher. Please also consider whether {{hpi.compatibleSinceVersion}} should be set as described in [Mark a new plugin version as incompatible with older versions|https://www.jenkins.io/doc/developer/plugin-development/mark-a-plugin-incompatible/]. |
New:
Upgrading the Bitbucket Server Integration plugin from 3.5.0 to 3.6.0 caused the "Manage Old Data" page of Jenkins to show notices about "branchName" in several builds. This seems to have been caused by [https://github.com/jenkinsci/atlassian-bitbucket-server-integration-plugin/pull/403] (for [ Please document in the 3.6.0 release notes of the plugin: - That Jenkins will show "branchName" as old data. - Whether there will be problems if a Jenkins administrator downgrades the plugin back to 3.5.0 or lower, after some builds have been done with 3.6.0 or higher. Please also consider whether {{hpi.compatibleSinceVersion}} should be set as described in [Mark a new plugin version as incompatible with older versions|https://www.jenkins.io/doc/developer/plugin-development/mark-a-plugin-incompatible/]. |
Kalle Niemitalo
made changes -
| Remote Link | New: This issue links to "Update changelog to explain that upgrading from 3.5.0 will cause Bran… · Pull Request #421 · jenkinsci/atlassian-bitbucket-server-integration-plugin (Web Link)" [ 28862 ] |