Vincent Robert I don't think it is enough to disable the Jira plugin. I believe that you need to downgrade the Jira plugin from 2.5.1 to 2.5.0 or earlier. There was a discussion of possibly "blacklisting" Jira plugin 2.5.1.
Refer to JENKINS-48357 for the details of the types of damage done to critical libraries by the 2.5.1 release.
[~vrobert78] I don't think it is enough to disable the Jira plugin. I believe that you need to downgrade the Jira plugin from 2.5.1 to 2.5.0 or earlier. There was a discussion of possibly "blacklisting" Jira plugin 2.5.1 and that has been implemented about a week ago in the Jenkins update center.
Refer to JENKINS-48357 for the details of the types of damage done to critical libraries by the 2.5.1 release.
[~vrobert78] I don't think it is enough to disable the Jira plugin. I believe that you need to downgrade the Jira plugin from 2.5.1 to 2.5.0 or earlier. There was a discussion of "blacklisting" Jira plugin 2.5.1 and that has been implemented about a week ago in the [ Jenkins update center|https://github.com/jenkins-infra/backend-update-center2/commit/47580ef481d5c103bfcd5c9943d604029a151ebe].
Refer to JENKINS-48357 for the details of the types of damage done to critical libraries by the 2.5.1 release.
Mark Waite , since disabling the three plugins (JIRA plugin, JIRA Integration for Blue Ocean and Blue Ocean), hangs have gone. Everything has running fine yesterday.
Vincent Robert thanks very much for your investigation and for sharing your results. I'd like to close this bug as a duplicate of JENKINS-48357. JENKINS-43857 will remain open until the fix is released in the Jira plugin. Is that OK?
[~vrobert78] thanks very much for your investigation and for sharing your results. I'd like to close this bug as a duplicate of JENKINS-48357. JENKINS-4385748357 will remain open until the fix is released in the Jira plugin. Is that OK?