As far as I can tell, the Jira dependencies are that powerfully bad.
The initial report of JENKINS-43106 is months before the release of Jira
plugin 2.5.1. I believe there is a real bug in that area which is
independent of Jira plugin 2.5.1, but downgrading from Jira plugin 2.5.1 to
Jira plugin 2.5.0 resolves many of the reports of JENKINS-43106. I am
unable to duplicate JENKINS-43106, but I believe it is there. I don't
think it is in the git plugin, but I'm ready to be proven wrong about that
I have not seen JENKINS-43106 in my environment, but I downgraded from Jira
plugin 2.5.1 to Jira plugin 2.5.0 shortly after seeing the discussions
about the possibility of blacklisting Jira plugin 2.5.1.
On Wed, Feb 7, 2018 at 5:53 PM Michael Neale <mne...@cloudbees.com> wrote:
> This seems related to: https://issues.jenkins-ci.org/browse/JENKINS-43106
> as myself and a few others were seeing the same thing with github
> specifically and git rev-list - so not specific to pipeline.
> The JIRA dependencies are *that* powerfully bad?
> On Wednesday, February 7, 2018 at 9:00:06 PM UTC+11, Christoph wrote:
>> I found the solution in this thread:
>> Just downgrade the jira-Plugin to 2.5.0
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
To view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.