Bump org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source from 933.v7119e94e8f56 to 933.0.1 in /bom-weekly

[dependabot]

Bumps org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source from 933.v7119e94e8f56 to 933.0.1.

Release notes

Sourced from org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source's releases.

933.0.1

🐛 Bug fixes

• JENKINS-74972 - BitbucketUsernamePasswordCredentialMatcher returns invalid CQL (#940) @​KalleOlaviNiemitalo

Full Changelog: jenkinsci/bitbucket-branch-source-plugin@933.v7119e94e8f56...933.0.1

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[darinpope]

Maintainers removed CD from the plugin. I haven't dug into the issue, but from the BOM PR log:

07:12:44  [ERROR] Failed to execute goal org.jenkins-ci.tools:maven-hpi-plugin:3.42-rc1409.669de6d1a_866:resolve-test-dependencies (default-cli) on project sample: Execution default-cli of goal org.jenkins-ci.tools:maven-hpi-plugin:3.42-rc1409.669de6d1a_866:resolve-test-dependencies failed: org.kohsuke.github.GHFileNotFoundException: https://api.github.com/repos/jenkinsci/bitbucket-branch-source-plugin/git/refs/tags/cloudbees-bitbucket-branch-source-933.0.1 {"message":"Not Found","documentation_url":"https://docs.github.com/rest/git/refs#get-all-references-in-a-namespace","status":"404"} -> [Help 1]

If you change cloudbees-bitbucket-branch-source-933.0.1 to 933.0.1, it works, so I'm guessing the CD removal, the tagging changed too. However, visually the tag looks ok.

[darinpope]

Looks like it's probably this change.

[krisstern]

I see the following in the logs:

[2024-12-12T13:56:50.435Z] [ERROR] 'dependencies.dependency.artifactId' for org.eclipse.platform:org.eclipse.swt.${osgi.platform}:jar with value 'org.eclipse.swt.${osgi.platform}' does not match a valid id pattern. @ 

[krisstern]

Can confirm that the offending PR should be this one: jenkinsci/bitbucket-branch-source-plugin#942.

[MarkEWaite]

I think that the maintainer will need to release a new version. I think that the pom file of the release includes the wrong value for the SCM tag.

The released pom file has the value cloudbees-bitbucket-branch-source-933.0.1 but the actual tag is 933.0.1 (consistent with the other tags in the repository).

The branch that released the 933.0.1 release has removed the setting that is on the master branch. I think we'll need to close the BOM pull request because the released pom file contains a non-existing git tag.

Pull request proposing to fix the issue is:

• Use tagNameFormat to include correct tag in released pom file bitbucket-branch-source-plugin#943

[nfalco79]

I think that the maintainer will need to release a new version. I think that the pom file of the release includes the wrong value for the SCM tag.

933.0.2 released

the actual tag is 933.0.1 (consistent with the other tags in the repository).

Yes I did for that reason but I only realized the tag behaviour after I released it.

[krisstern]

Should I close this issue and wait for the one with tag 933.0.2?

[MarkEWaite]

Should I close this issue and wait for the one with tag 933.0.2?

Yes, this should be closed, since it won't be able to merge.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

[krisstern]

Thanks @MarkEWaite for confirming!