Failed to parse changelogN.xml error when starting pipeline jobs
Hello,
I'm getting the following error pretty frequently (~25% of the time) when
starting pipeline jobs on one of our Jenkins servers. It occurs in the scm
step of our pipelines, and I've seen it in all 3 of our pipelines on this
server:
Failed to parse
/opt/jenkins/inst/jobs/nightly.build/builds/43/changelog1.xml: ' '
See stage logs for more detail.
The stage logs do not have any more details - console output for that stage
step is:
[nightly.build] $ hg showconfig paths.default
[nightly.build] $ hg pull --rev default
pulling from
no changes found
[nightly.build] $ hg update --clean --rev default
108 files updated, 0 files merged, 0 files removed, 0 files unresolved
[nightly.build] $ hg log --rev . --template {node}
[nightly.build] $ hg log --rev . --template {rev}
[nightly.build] $ hg log --rev 629ca14eef09b0e09c37627a94ea51c0d5129bfb
--template exists\n
exists
[nightly.build] $ hg log --template "{desc|xmlescape}{file_adds|stringify|xmlescape}{file_dels|stringify|xmlescape}{files|stringify|xmlescape}{parents}\n"
--rev "ancestors('default') and not
ancestors(629ca14eef09b0e09c37627a94ea51c0d5129bfb)" --encoding UTF-8
--encodingmode replace
[nightly.build] $ hg log --rev . --template {node}
[nightly.build] $ hg log --rev . --template {rev}
The contents of the changelog look OK to me:
/export/on-gate/usr/fish $ cat
/opt/jenkins/inst/jobs/nightly.build/builds/43/changelog1.xml
Jenkins 2.46.2 LTS, Mercurial plugin 1.59, java 1.8.0_131, hg 4.1
Any ideas? I've never seen this error on any of our other Jenkins
instances, and it's killing us on this one.
Thanks!
Adam
--
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
https://groups.google.com/d/msgid/jenkinsci-users/5526c2dd-73d2-4495-8d78-42ab11ece6b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Failed to parse changelogN.xml error when starting pipeline jobs
Any thoughts on what this may be or how to debug?
On Wednesday, May 3, 2017 at 7:36:27 AM UTC-7, Adam Paul wrote:
>
> Hello,
>
> I'm getting the following error pretty frequently (~25% of the time) when
> starting pipeline jobs on one of our Jenkins servers. It occurs in the scm
> step of our pipelines, and I've seen it in all 3 of our pipelines on this
> server:
>
> Failed to parse
> /opt/jenkins/inst/jobs/nightly.build/builds/43/changelog1.xml: ' version="1.0" encoding="UTF-8"?> '
> See stage logs for more detail.
>
> The stage logs do not have any more details - console output for that
> stage step is:
>
> [nightly.build] $ hg showconfig paths.default
> [nightly.build] $ hg pull --rev default
> pulling from
> no changes found
> [nightly.build] $ hg update --clean --rev default
> 108 files updated, 0 files merged, 0 files removed, 0 files unresolved
> [nightly.build] $ hg log --rev . --template {node}
> [nightly.build] $ hg log --rev . --template {rev}
> [nightly.build] $ hg log --rev 629ca14eef09b0e09c37627a94ea51c0d5129bfb
> --template exists\n
> exists
> [nightly.build] $ hg log --template " author='{author|xmlescape}' rev='{rev}'
> date='{date}'>{desc|xmlescape}{file_adds|stringify|xmlescape}{file_dels|stringify|xmlescape}{files|stringify|xmlescape}{parents}\n"
> --rev "ancestors('default') and not
> ancestors(629ca14eef09b0e09c37627a94ea51c0d5129bfb)" --encoding UTF-8
> --encodingmode replace
> [nightly.build] $ hg log --rev . --template {node}
>
> [nightly.build] $ hg log --rev . --template {rev}
>
> The contents of the changelog look OK to me:
>
> /export/on-gate/usr/fish $ cat
> /opt/jenkins/inst/jobs/nightly.build/builds/43/changelog1.xml
>
>
>
>
> Jenkins 2.46.2 LTS, Mercurial plugin 1.59, java 1.8.0_131, hg 4.1
>
> Any ideas? I've never seen this error on any of our other Jenkins
> instances, and it's killing us on this one.
>
> Thanks!
> Adam
>
--
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
https://groups.google.com/d/msgid/jenkinsci-users/34b31be7-73df-4dde-b5c9-991c51eba71b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Failed to parse changelogN.xml error when starting pipeline jobs
Hihi,
For anyone searching for this later, this is:
https://issues.jenkins-ci.org/browse/JENKINS-43176
and a workaround is to put sleeps of different durations in each branch
before the SCM step(s) so the parallel branches are not executing SCM steps
at the same time.
Rgds,
Adam
On Sunday, May 7, 2017 at 8:30:24 AM UTC-7, Adam Paul wrote:
>
> Any thoughts on what this may be or how to debug?
>
> On Wednesday, May 3, 2017 at 7:36:27 AM UTC-7, Adam Paul wrote:
>>
>> Hello,
>>
>> I'm getting the following error pretty frequently (~25% of the time) when
>> starting pipeline jobs on one of our Jenkins servers. It occurs in the scm
>> step of our pipelines, and I've seen it in all 3 of our pipelines on this
>> server:
>>
>> Failed to parse
>> /opt/jenkins/inst/jobs/nightly.build/builds/43/changelog1.xml: '> version="1.0" encoding="UTF-8"?> '
>> See stage logs for more detail.
>>
>> The stage logs do not have any more details - console output for that
>> stage step is:
>>
>> [nightly.build] $ hg showconfig paths.default
>> [nightly.build] $ hg pull --rev default
>> pulling from
>> no changes found
>> [nightly.build] $ hg update --clean --rev default
>> 108 files updated, 0 files merged, 0 files removed, 0 files unresolved
>> [nightly.build] $ hg log --rev . --template {node}
>> [nightly.build] $ hg log --rev . --template {rev}
>> [nightly.build] $ hg log --rev 629ca14eef09b0e09c37627a94ea51c0d5129bfb
>> --template exists\n
>> exists
>> [nightly.build] $ hg log --template "> author='{author|xmlescape}' rev='{rev}'
>> date='{date}'>{desc|xmlescape}{file_adds|stringify|xmlescape}{file_dels|stringify|xmlescape}{files|stringify|xmlescape}{parents}\n"
>> --rev "ancestors('default') and not
>> ancestors(629ca14eef09b0e09c37627a94ea51c0d5129bfb)" --encoding UTF-8
>> --encodingmode replace
>> [nightly.build] $ hg log --rev . --template {node}
>>
>> [nightly.build] $ hg log --rev . --template {rev}
>>
>> The contents of the changelog look OK to me:
>>
>> /export/on-gate/usr/fish $ cat
>> /opt/jenkins/inst/jobs/nightly.build/builds/43/changelog1.xml
>>
>>
>>
>>
>> Jenkins 2.46.2 LTS, Mercurial plugin 1.59, java 1.8.0_131, hg 4.1
>>
>> Any ideas? I've never seen this error on any of our other Jenkins
>> instances, and it's killing us on this one.
>>
>> Thanks!
>> Adam
>>
>
--
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
https://groups.google.com/d/msgid/jenkinsci-users/e75762e9-d6a7-42ee-8e85-ace08e464e22%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Best/most idiomatic way to do parallel tasks that are largely the same?
Hello,
Let's say I have a product that needs to build on two different
architectures (indeed, I do). The build steps are exactly the same, only
the architecture differs. What is the best way to do this in parallel in a
pipeline without duplicating the code for each architecture. The example
below is simple, but my real world one isn't so much.
eg. instead of:
parallel(
"sparc": {
def arch="sparc"
do_stuff(arch)
do_more_stuff(arch)
},
"i386": {
def arch="i386"
do_stuff(arch)
do_more_stuff(arch)
}
)
There is:
def testList = ["sparc","i386"]
def branches = [:]
for (int i = 0; i < testList.size() ; i++) {
String arch=testList[i]
stage ("branch_${arch}"){
branches["branch_${arch}"] = {
node (){
do_stuff(arch)
do_more_stuff(arch)
}
}
}
}
parallel branches
which works, but I'm wondering if there is a better/more idiomatic way to
do this?
Thanks!
Adam
--
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
https://groups.google.com/d/msgid/jenkinsci-users/b7a18396-5e0b-467c-8e08-9bfcbb1d7e33%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
