depend on jersey2-api

[jetersen]

to avoid class path conflicts. Currently class path conflicts exist between gitlab-api plugin and jira plugin

cc @basil @dcendents

jenkinsci/jersey2-api-plugin#19

🚨 Please review the guidelines for contributing to this repository.

• Make sure you are requesting to pull a topic/feature/bugfix branch (right side) and not your master branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did
• Link to relevant issues in GitHub
• Link to relevant pull requests, esp. upstream and downstream changes
• Ensure you have provided tests - that demonstrates feature works or fixes the issue

[jetersen]

Need release of
jenkinsci/bom#1022

[jetersen]

@rantoniuk would you be able to take the HPI and do some sanity testing?
https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/jira/3.8-rc1363.0a_029e634220/

I don't have test setup for Jira 😅

[basil]

I think @dcendents had a way of reproducing the problem? It would be nice to get confirmation that the incremental build from this PR resolves the issue.

[jetersen]

@rantoniuk I think you can remove the waiting for LTS label.

Nothing has changed from the HPI point of view. Though I appreciate if someone would be able to test it. I don't use Jira 😅

[dcendents]

As I mentionned before we don't really use the JIRA plugin but since we have a JIRA instance here I tried the incremental build.

It correctly scanned the JIRA issue from the git comment and added a link in the jenkins changes section.
jiraComment pipeline script correctly adds a comment to the issue in JIRA.

I could not see any errors in the logs (but I am plagued by https://issues.jenkins.io/browse/JENKINS-68057 so hopefully I didn't miss it)

[basil]

Thanks for doing a smoke test Daniel. From my perspective this is ready to land.

[rantoniuk]

It's waiting for @olamy since he asked to stop merging any PRs temporarilly because of preparing a security release.