it looks like that the latest version of the Jackson API Plugin (2.13.1-244.v773c36c5b330) introduced a regression in the Jira Plugin (downstream ticket: https://github.com/jenkinsci/jira-plugin/issues/398 )
I don't know if it should be fixed on the Jira plugin or in the Jackson API plugin tho.
See the exception:
{{}}
java.lang.ClassNotFoundException: org.glassfish.jersey.internal.RuntimeDelegateImpl
at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1417)
at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1372)
at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1127)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)
at java.base/java.lang.Class.forName0(Native Method)
at java.base/java.lang.Class.forName(Class.java:315)
at javax.ws.rs.ext.FactoryFinder.newInstance(FactoryFinder.java:87)
at javax.ws.rs.ext.FactoryFinder.find(FactoryFinder.java:185)
at javax.ws.rs.ext.RuntimeDelegate.findDelegate(RuntimeDelegate.java:111)
Caused: java.lang.RuntimeException
at javax.ws.rs.ext.RuntimeDelegate.findDelegate(RuntimeDelegate.java:129)
at javax.ws.rs.ext.RuntimeDelegate.getInstance(RuntimeDelegate.java:96)
at javax.ws.rs.core.UriBuilder.newInstance(UriBuilder.java:72)
at javax.ws.rs.core.UriBuilder.fromUri(UriBuilder.java:83)
at com.atlassian.jira.rest.client.internal.async.AsynchronousJiraRestClient.<init>(AsynchronousJiraRestClient.java:58)
at hudson.plugins.jira.extension.ExtendedAsynchronousJiraRestClient.<init>(ExtendedAsynchronousJiraRestClient.java:14)
at hudson.plugins.jira.JiraSite$ExtendedAsynchronousJiraRestClientFactory.create(JiraSite.java:647)
at hudson.plugins.jira.JiraSite.createSession(JiraSite.java:554)
at hudson.plugins.jira.JiraSite.getSession(JiraSite.java:523)
at hudson.plugins.jira.JiraSite.lambda$getSitesFromFolders$2(JiraSite.java:1335)
at java.base/java.util.Arrays$ArrayList.forEach(Arrays.java:4390)
at hudson.plugins.jira.JiraSite.getSitesFromFolders(JiraSite.java:1335)
at hudson.plugins.jira.JiraSite.get(JiraSite.java:1366)
at hudson.plugins.jira.pipeline.IssueSelectorStep$IssueSelectorStepExecution.run(IssueSelectorStep.java:86)
at hudson.plugins.jira.pipeline.IssueSelectorStep$IssueSelectorStepExecution.run(IssueSelectorStep.java:71)
at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47)
at hudson.security.ACL.impersonate2(ACL.java:449)
at hudson.security.ACL.impersonate(ACL.java:461)
at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
Release 2.13.1-246.va8a9f3eaf46a of jackson2-api is available from: https://repo.jenkins-ci.org/public/org/jenkins-ci/plugins/jackson2-api/2.13.1-246.va8a9f3eaf46a/
Release 2.35-1 of jersey2-api is available from: https://repo.jenkins-ci.org/artifactory/public/io/jenkins/plugins/jersey2-api/2.35-1/
massimeddu oskaraskurmis warden Can you please test the jackson2-api and jersey2-api releases mentioned above and confirm the issue is resolved? For instructions on how to install a custom build, see: https://www.jenkins.io/doc/book/managing/plugins/#advanced-installation