Radek Antoniuk
Radek Antoniuk
davidbrown92: A month ago we upgraded to Jenkins 1.651.3 although we are still using JIRA plugin version 1.38. I acknowledge that I should consider updating to a newer version of...
warden: Still thinking about it... could this be anyhow related to JENKINS-32884?
davidbrown92: Just to say that we're now on Jenkins 1.651.3 with Jira plugin v 2.3.1 and JIRA v7.2.7 and we still face this issue. We upgraded the Jira plugin a...
davidbrown92: I've been looking into this further and trying to work out why some builds have posted comments to cases which are not in the build manifest. I noticed that...
warden: Just checking, are you still facing this issue and need help?
jedavis: Anyone happen to know if this is working in current builds of Jenkins? I have 2.25 asnd 2.30 in place with JIRA plugin 2.2.1 and I've noticed that downstream...
jedavis: The break occurred between version 2.1 (working) and 2.2 (feature broken). Rolling back to 2.1 helps with using fingerprints to mark issues from upstream jobs, but then we lose...
warden: I guess you'd expect the build to fail in case the comment is too long?
@huanyushi any reason this should not be part of the upstream?
@abronin this feature would be useful for me as well, any thoughts on this PR?