Radek Antoniuk
Radek Antoniuk
alexeiz: I showed this ticket to the team and one of the guys commented this: Leandro Loos @alexei.znamensky: from what I saw, when we configure a job that finally succeeds,...
alexeiz: As a matter of fact, the job 1806 message went to 4 tickets: one that appears to be the right one, and then other three had no messages whatsoever,...
davidbrown92: This sounds like the same issue we are facing (using Jenkins version 1.598 and JIRA plugin version 1.38). What I've noticed is that the incorrect updates have only the...
davidbrown92: Hi Alexei Znamensky, Just curious, what version of Jenkins and JIRA plugin are you seeing this issue in please? As I said, I'm seeing the issue with JIRA plugin...
alexeiz: hi David Brown , we are currently running: Jenkins ver. 1.642 JIRA plugin 2.1 (2.2 is out there, going to update soon)
davidbrown92: Thank you for your update, Alexei Znamensky.
davidbrown92: We are seeing two different formats to the message. A valid message has multiple lines including the JIRA reference, commit comments and changeset details. Incorrect (misleading) messages contain a...
warden: Is this possible that there were concurrent builds running on the same jenkins slave when this happened?
davidbrown92: Thank you for your response, Radek. That is possible, yes, as we do tend to have a number of builds running concurrently on the same slave. I have tried...
warden: Interesting, so this might some other issue too, did you try with the latest version?