[JIRA] (JENKINS-34313) SAXParseException from parallel SCM checkout

6 views
Skip to first unread message

jglick@cloudbees.com (JIRA)

unread,
Jan 22, 2019, 2:53:03 PM1/22/19
to jenkinsc...@googlegroups.com
Jesse Glick updated an issue
 
Jenkins / Bug JENKINS-34313
SAXParseException from parallel SCM checkout
Change By: Jesse Glick
Summary: Exceptions by SAXParseException from parallel SCM checkout
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

dnusbaum@cloudbees.com (JIRA)

unread,
Jan 22, 2019, 3:02:02 PM1/22/19
to jenkinsc...@googlegroups.com
Devin Nusbaum commented on Bug JENKINS-34313
 
Re: SAXParseException from parallel SCM checkout

Studying the fix of JENKINS-47201 by Devin Nusbaum I suspect it was incomplete, as this block is not synchronized as a whole, and so two concurrent branches could both pick the same changelog file.

Looks like it, I think we could reorder some statements in the method so that we could lock Run when looking for the file without needing to lock prev as well, although maybe that code could be refactored to use the temp file APIs or something to be more robust.

dnusbaum@cloudbees.com (JIRA)

unread,
Jan 22, 2019, 4:45:05 PM1/22/19
to jenkinsc...@googlegroups.com
Devin Nusbaum edited a comment on Bug JENKINS-34313
{quote}

Studying the fix of JENKINS-47201 by Devin Nusbaum I suspect it was incomplete, as this block is not synchronized as a whole, and so two concurrent branches could both pick the same changelog file.
{quote}


Looks like it, I think we could reorder some statements in the method so that we could lock {{Run}} when looking for the file without needing to lock {{prev}} as well, although maybe that code could be refactored to use the temp file APIs or something to be more robust.

dnusbaum@cloudbees.com (JIRA)

unread,
Jan 22, 2019, 4:45:08 PM1/22/19
to jenkinsc...@googlegroups.com
Devin Nusbaum started work on Bug JENKINS-34313
 
Change By: Devin Nusbaum
Status: Open In Progress

dnusbaum@cloudbees.com (JIRA)

unread,
Jan 22, 2019, 4:45:10 PM1/22/19
to jenkinsc...@googlegroups.com
Change By: Devin Nusbaum
Status: In Progress Review

dnusbaum@cloudbees.com (JIRA)

unread,
Jan 22, 2019, 4:45:12 PM1/22/19
to jenkinsc...@googlegroups.com
Devin Nusbaum assigned an issue to Devin Nusbaum
Change By: Devin Nusbaum
Assignee: Devin Nusbaum

david.aldrich@emea.nec.com (JIRA)

unread,
Jan 28, 2019, 5:20:02 AM1/28/19
to jenkinsc...@googlegroups.com
David Aldrich commented on Bug JENKINS-34313
 
Re: SAXParseException from parallel SCM checkout

The SAXParseException is now occuring repeatedly (every build) for us.

dnusbaum@cloudbees.com (JIRA)

unread,
Jan 28, 2019, 9:21:05 AM1/28/19
to jenkinsc...@googlegroups.com
Devin Nusbaum updated an issue
 
Change By: Devin Nusbaum
Attachment: workflow-scm-step-2.8-rc326.7286a182d923.hpi

dnusbaum@cloudbees.com (JIRA)

unread,
Jan 28, 2019, 9:21:06 AM1/28/19
to jenkinsc...@googlegroups.com
Devin Nusbaum commented on Bug JENKINS-34313
 
Re: SAXParseException from parallel SCM checkout

David Aldrich I've attached an incremental build of the Pipeline SCM Step Plugin that contains PR #32. Feel free to try it out (preferably in a test environment first) to let us know if it addresses the problem. I am not sure when I will have time to test the code further myself and merge/release that change, so if you are blocked I would recommend testing that build.

workflow-scm-step-2.8-rc326.7286a182d923.hpi

david.aldrich@emea.nec.com (JIRA)

unread,
Jan 28, 2019, 10:38:03 AM1/28/19
to jenkinsc...@googlegroups.com

Thanks Devin, I will give it a try.

david.aldrich@emea.nec.com (JIRA)

unread,
Feb 18, 2019, 8:44:03 AM2/18/19
to jenkinsc...@googlegroups.com

Devin Nusbaum I have been running workflow-scm-step-2.8-rc326.7286a182d923.hpi for 3 weeks and have not seen a single instance of the SAXParseException. So it looks as though PR #32 fixes the problem.

Please will you consider releasing a formal update of the plugin?

david.aldrich@emea.nec.com (JIRA)

unread,
Feb 18, 2019, 8:48:02 AM2/18/19
to jenkinsc...@googlegroups.com
David Aldrich edited a comment on Bug JENKINS-34313
[~dnusbaum] I have been running workflow-scm-step-2.8-rc326.7286a182d923.hpi for 3 weeks and have not seen a single instance of the SAXParseException.   It has also been running fine with no resource locks for 3 days. So it looks as though  PR #32 fixes the problem.

Please will you consider releasing a formal update of the plugin?

benj_boyer@hotmail.com (JIRA)

unread,
Mar 30, 2019, 10:40:03 PM3/30/19
to jenkinsc...@googlegroups.com
Benjamin Boyer assigned an issue to Benjamin Boyer
 
Change By: Benjamin Boyer
Assignee: Devin Nusbaum Benjamin Boyer

benj_boyer@hotmail.com (JIRA)

unread,
Mar 30, 2019, 10:41:02 PM3/30/19
to jenkinsc...@googlegroups.com
Benjamin Boyer assigned an issue to Devin Nusbaum
Change By: Benjamin Boyer
Assignee: Benjamin Boyer Devin Nusbaum

benj_boyer@hotmail.com (JIRA)

unread,
Mar 30, 2019, 10:45:03 PM3/30/19
to jenkinsc...@googlegroups.com
Benjamin Boyer commented on Bug JENKINS-34313
 
Re: SAXParseException from parallel SCM checkout

Hi Devin Nusbaum,

I'm having the same issue for. I'll use workflow-scm-step-2.8-rc326.7286a182d923.hpi to confirm if it's fixing the "ConcurrentModificationException". I'll test it against 100+ parallelized repositories (in groups fo 12 concurrent extractions)

Thanks in advance

benj_boyer@hotmail.com (JIRA)

unread,
Mar 30, 2019, 10:47:02 PM3/30/19
to jenkinsc...@googlegroups.com
Benjamin Boyer edited a comment on Bug JENKINS-34313
Hi [~dnusbaum],

I'm having the same issue for. I'll use workflow-scm-step-2.8-rc326.7286a182d923.hpi to confirm if it's fixing the "ConcurrentModificationException". I'll test it against 100+ parallelized repositories (in groups fo of 12 concurrent extractions)

Thanks in advance

amorales.ericsson@gmail.com (JIRA)

unread,
Apr 8, 2019, 1:16:04 AM4/8/19
to jenkinsc...@googlegroups.com
Andre Morales updated an issue
 
Change By: Andre Morales
Attachment: stable.PNG

amorales.ericsson@gmail.com (JIRA)

unread,
Apr 8, 2019, 1:19:03 AM4/8/19
to jenkinsc...@googlegroups.com
Andre Morales commented on Bug JENKINS-34313
 
Re: SAXParseException from parallel SCM checkout

I was having the same issue with a pipeline of 23 parallel  checkouts. It was failing randomly. 

I have installed plugin workflow-scm-step-2.8-rc326.7286a182d923.hpi and everything goes well now.  Since installation, all 23 agents running in parallel are checking out correctly.

 

wolfgang.issovits@gmail.com (JIRA)

unread,
May 7, 2019, 11:08:04 AM5/7/19
to jenkinsc...@googlegroups.com

Is there a chance to get a new release of the plugin with this fix included?
That would be great as this issue is really problematic for larger parallel pipelines.

torsten.werner@assyst-intl.com (JIRA)

unread,
May 15, 2019, 7:18:03 AM5/15/19
to jenkinsc...@googlegroups.com

Please, release the fix. The issue is really a problem for us.

dnusbaum@cloudbees.com (JIRA)

unread,
Jun 5, 2019, 5:10:03 PM6/5/19
to jenkinsc...@googlegroups.com
 

A fix for this issue was just released in Pipeline SCM Step Plugin version 2.8.
Change By: Devin Nusbaum
Status: In Review Resolved
Resolution: Fixed
Released As: workflow-scm-step 2.8
Reply all
Reply to author
Forward
0 new messages