[JIRA] (JENKINS-42885) wfapi incorrectly reporting build job status
Title: Message Title
Matthew Hall updated an issue
Jenkins / JENKINS-42885
wfapi incorrectly reporting build job status
Change By:
Matthew Hall
The wfapi can end up reporting an incorrect status for a child job it the original trigger job's result is forced to unstable.The following test case has two jobs the trigger job and the child job. The trigger job builds the child job, waits on it and then sets its own results to UNSTABLE. The child job finishes with a success result.What I expect is to be able to look into the wfapi and see that the child job actually was a success, however it is marked as unstable.In a similar case where the trigger job result is set to FAILURE the status of the child job is SUCCESSTestcase:{noformat}Child Job:node { currentBuild.setResult("SUCCESS")}Trigger Job:stage ('run'){ def parallel_info build job: "expected_success", propagate: falsecurrentBuild.setResult('UNSTABLE')}{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
[JIRA] (JENKINS-42885) wfapi incorrectly reporting build job status
Title: Message Title
Matthew Hall created an issue
Jenkins / JENKINS-42885
wfapi incorrectly reporting build job status
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-api-plugin
Created:
2017/Mar/17 2:40 PM
Priority:
Minor
Reporter:
Matthew Hall
The wfapi can end up reporting an incorrect status for a child job it the original trigger jon's result is forced to unstable. The following test case has two jobs the trigger job and the child job. The trigger job builds the child job, waits on it and then sets its own results to UNSTABLE. The child job finishes with a success result. What I expect is to be able to look into the wfapi and see that the child job actually was a success, however it is marked as unstable. In a similar case where the trigger job result is set to FAILURE the status of the child job is SUCCESS Testcase:
Child Job:
node {
currentBuild.setResult("SUCCESS")
}
Trigger Job:
stage ('run'){
def parallel_info
build job: "expected_success", propagate: false
currentBuild.setResult('UNSTABLE')
}
[JIRA] (JENKINS-42616) Restarted Jobs consume Nodes when not necessary
Title: Message Title
Matthew Hall commented on JENKINS-42616
Re: Restarted Jobs consume Nodes when not necessary
A work around for this issue is to not populate the map that is passed to the parallel step inside a node:
def run_function (String words){
return {
node (){
sleep(300)
println words
}
}
}
Map parllel_map
node () {
println "Using my frist node"
}
parllel_map = [
'A': run_function("A")
]
parallel parllel_map
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42616) Restarted Jobs consume Nodes when not necessary
Title: Message Title
Matthew Hall updated an issue
Jenkins / JENKINS-42616
Restarted Jobs consume Nodes when not necessary
Change By:
Matthew Hall
May be related to # JENKINS-40771 In the following situation, we have a single job that runs a function which requires a node.Upon restart the job consumes 1 more mode than expected.I expect only a single node to be used at any time. Before restart this is the case, after restart this is not.The additional node is consumed until the parallel call is finished.If this additional node happens to be the only available node then the pending jobs will be stuck waiting for executor.Pictures attached.To reproduce: # Run the following pipeline script # Once its running restart server # Observe the build queueThis has been tested using the windows service and running from the cmdline using: "java -jar jenkins.war --httpPort=8082"{noformat}def run_function (String words){ return {node (){ sleep(300) println words} }}Map parllel_mapnode () { println "Using my frist node" parllel_map = [ 'A': run_function("A") ]}parallel parllel_map{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42616) Restarted Jobs consume Nodes when not necessary
Title: Message Title
Matthew Hall updated an issue
Jenkins / JENKINS-42616
Restarted Jobs consume Nodes when not necessary
Change By:
Matthew Hall
In the following situation, we have a single job that runs a function which requires a node.Upon restart the job consumes 1 more mode than expected.I expect only a single node to be used at any time. Before restart this is the case, after restart this is not.The additional node is consumed until the parallel call is finished.If this additional node happens to be the only available node then the pending jobs will be stuck waiting for executor. Pictures attached.To reproduce: # Run the following pipeline script # Once its running restart server # Observe the build queueThis has been tested using the windows service and running from the cmdline using: "java -jar jenkins.war --httpPort=8082" {noformat}def run_function (String words){ return {node (){ sleep(300) println words} }}Map parllel_mapnode () { println "Using my frist node" parllel_map = [ 'A': run_function("A") ]}parallel parllel_map{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42616) Restarted Jobs consume Nodes when not necessary
Title: Message Title Matthew Hall updated an issue Jenkins / JENKINS-42616 Restarted Jobs consume Nodes when not necessary Change By: Matthew Hall Attachment: 42616.PNG Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42616) Restarted Jobs consume Nodes when not necessary
Title: Message Title Matthew Hall updated an issue Jenkins / JENKINS-42616 Restarted Jobs consume Nodes when not necessary Change By: Matthew Hall Summary: Restarted Jobs consume Nodes when not necassary necessary Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42616) Restarted Jobs consume Nodes when not necassary
Title: Message Title
Matthew Hall updated an issue
Jenkins / JENKINS-42616
Restarted Jobs consume Nodes when not necassary
Change By:
Matthew Hall
In the following testcase situation , upon we have a single job that runs a function which requires a node.Upon restart the job consumes 1 more mode than expected.I expect only a single node to be used at any time. Before restart this is the case, after restart this is not.The additional node is consumed until the parallel call is finished.If this additional node happens to be the only available node then the pending jobs will be stuck waiting for executor.{noformat}def run_function (String words){ return {node (){ sleep(300) println words} }}Map parllel_mapnode () { println "Using my frist node" parllel_map = [ 'A': run_function("A") ]}parallel parllel_map{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues"
[JIRA] (JENKINS-42616) Restarted Jobs consume Nodes when not necassary
Title: Message Title
Matthew Hall updated an issue
Jenkins / JENKINS-42616
Restarted Jobs consume Nodes when not necassary
Change By:
Matthew Hall
In the following testcase, upon restart the job consumes 1 more mode than expected.I expect only a single node to be used at any time. Before restart this is the case, after restart this is not.The additional node is consumed until the parallel call is finished. If this additional node happens to be the only available node then the pending jobs will be stuck waiting for executor. {noformat}def run_function (String words){ return {node (){ sleep(300) println words} }}Map parllel_mapnode () { println "Using my frist node" parllel_map = [ 'A': run_function("A") ]}parallel parllel_map{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an
[JIRA] (JENKINS-42616) Restarted Jobs consume Nodes when not necassary
Title: Message Title Matthew Hall updated an issue Jenkins / JENKINS-42616 Restarted Jobs consume Nodes when not necassary Change By: Matthew Hall Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42616) Restarted Jobs consume Nodes when not necassary
Title: Message Title
Matthew Hall updated an issue
Jenkins / JENKINS-42616
Restarted Jobs consume Nodes when not necassary
Change By:
Matthew Hall
In the following testcase, upon restart the job consumes 1 more mode than expected.I expect only a single node to be used at any time. Before restart this is the case, after restart this is not. The additional node is consumed until the parallel call is finished. {noformat}def run_function (String words){ return {node (){ sleep(300) println words} }}Map parllel_mapnode () { println "Using my frist node" parllel_map = [ 'A': run_function("A") ]}parallel parllel_map{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42616) Restarted Jobs consume Nodes when not necassary
Title: Message Title Matthew Hall updated an issue Jenkins / JENKINS-42616 Restarted Jobs consume Nodes when not necassary Change By: Matthew Hall Environment: ChromeJenkins ver. 2.19.4Pipeline 2 / . 5 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42616) Restarted Jobs consume Nodes when not necassary
Title: Message Title
Matthew Hall updated an issue
Jenkins / JENKINS-42616
Restarted Jobs consume Nodes when not necassary
Change By:
Matthew Hall
In the following testcase, upon restart the job consumes 1 more mode than expected.I expect only a single node to be used at any time. Before restart this is the case, after restart this is not. { quote noformat } h6. {{ def run_function (String words) \ { }} {{ return \ { }} {{ node () \ { }} {{ sleep(300) }} {{ println words }} h6. } } {{ } }} h6. {{ Map parllel_map }} {{ node () \ { }} {{ println "Using my frist node" }} h6. {{ parllel_map = [ }} {{ 'A': run_function("A") }} {{ ] }} {{ } }} h6. {{ parallel parllel_map }} { quote noformat }
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-42616) Restarted Jobs consume Nodes when not necassary
Title: Message Title
Matthew Hall created an issue
Jenkins / JENKINS-42616
Restarted Jobs consume Nodes when not necassary
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
after restart.png, before restart.png
Components:
workflow-api-plugin
Created:
2017/Mar/09 11:50 AM
Environment:
Chrome Jenkins ver. 2.19.4 Pipeline 2/5
Priority:
Minor
Reporter:
Matthew Hall
In the following testcase, upon restart the job consumes 1 more mode than expected. I expect only a single node to be used at any time. Before restart this is the case, after restart this is not. def run_function (String words){ return { node (){ sleep(300) println words {{ }}} {{ }}} } Map parllel_map node () { println "Using my frist node" parllel_map = [ 'A': run_function("A") ] } parallel parllel_map
Add Comment
[JIRA] (JENKINS-42225) Provide a way to add a configuration label when publishing during a parallel branch
Title: Message Title
Matthew Hall updated an issue
Jenkins / JENKINS-42225
Provide a way to add a configuration label when publishing during a parallel branch
Change By:
Matthew Hall
Hello,When a multiConfig job publishes test result resulst it is easy to see the test results per config.When a pipeline publishes multiple sets of test results, in the case of multiple configurations running in a parallel block, the published test results show no differentiation between configs or files .I would like to be able to add a label to the publish Junit step to allow me to create similar test result view as the multi config jobs.Screenshot attached of the multiConfig job view and the pipeline job viewHere is a script that fits the described use case: {noformat}def publicjJunit_test () {node (){writeFile file: 'junit.xml', text: """Details about failure """junit 'junit.xml'}}Map multi_junit = [ 'junit_1': publicjJunit_test(),'junit_2': publicjJunit_test(),'junit_3': publicjJunit_test()]{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-42225) Provide a way to add a configuration label when publishing during a parallel branch
Title: Message Title
Matthew Hall updated an issue
Jenkins / JENKINS-42225
Provide a way to add a configuration label when publishing during a parallel branch
Change By:
Matthew Hall
Comment:
Here is a script that fits the described use case:def publicjJunit_test () {node (){writeFile file: 'junit.xml', text: """Details about failure """junit 'junit.xml'}}Map multi_junit = [ 'junit_1': publicjJunit_test(),'junit_2': publicjJunit_test(),'junit_3': publicjJunit_test()]
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42225) Provide a way to add a configuration label when publishing during a parallel branch
Title: Message Title
Matthew Hall updated an issue
Jenkins / JENKINS-42225
Provide a way to add a configuration label when publishing during a parallel branch
Change By:
Matthew Hall
Hello,When a multiConfig job publishes test result it is easy to see the test results per config.When a pipeline publishes multiple sets of test results, in the case of multiple configurations running in a parallel block, the published test results show no differentiation between configs.I would like to be able to add a label to the publish Junit step to allow me to create similar test result view as the multi config jobs.Screenshot attached of the multiConfig job view and the pipeline job view Here is a script that fits the described use case:{noformat}def publicjJunit_test () {node (){writeFile file: 'junit.xml', text: """Details about failure """junit 'junit.xml'}}Map multi_junit = [ 'junit_1': publicjJunit_test(),'junit_2': publicjJunit_test(),'junit_3': publicjJunit_test()]{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-42225) Provide a way to add a configuration label when publishing during a parallel branch
Title: Message Title
Matthew Hall commented on JENKINS-42225
Re: Provide a way to add a configuration label when publishing during a parallel branch
Here is a script that fits the described use case: def publicjJunit_test () { node () { writeFile file: 'junit.xml', text: """Details about failure """ junit 'junit.xml' } } Map multi_junit = [ 'junit_1': publicjJunit_test(), 'junit_2': publicjJunit_test(), 'junit_3': publicjJunit_test()]
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42225) Provide a way to add a configuration label when publishing during a parallel branch
Title: Message Title
Matthew Hall updated an issue
Jenkins / JENKINS-42225
Provide a way to add a configuration label when publishing during a parallel branch
Change By:
Matthew Hall
Hello,When a multiConfig job publishes test result it is easy to see the test results per config.When a pipeline publishes multiple sets of test results, in the case of multiple configurations running in a parallel block, the published test results show no differentiation between configs.I would like to be able to add a label to the publish Junit step to allow me to create similar test result view as the multi config jobs.Screenshot attached of the multiConfig job view and the pipeline job view Here is a script that fits the described use case:{{def publicjJunit_test () {node (){writeFile file: 'junit.xml', text: """Details about failure """junit 'junit.xml'}}Map multi_junit = [ 'junit_1': publicjJunit_test(),'junit_2': publicjJunit_test(),'junit_3': publicjJunit_test()]}}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-42225) Provide a way to add a configuration label when publishing during a parallel branch
Title: Message Title
Matthew Hall created an issue
Jenkins / JENKINS-42225
Provide a way to add a configuration label when publishing during a parallel branch
Issue Type:
New Feature
Assignee:
Unassigned
Attachments:
multiConfig.png, pipeline.png
Components:
junit-plugin
Created:
2017/Feb/21 4:53 PM
Priority:
Minor
Reporter:
Matthew Hall
Hello, When a multiConfig job publishes test result it is easy to see the test results per config. When a pipeline publishes multiple sets of test results, in the case of multiple configurations running in a parallel block, the published test results show no differentiation between configs. I would like to be able to add a label to the publish Junit step to allow me to create similar test result view as the multi config jobs. Screenshot attached of the multiConfig job view and the pipeline job view Here is a script that fits the described use case: {{ def publicjJunit_test () { node () { writeFile file: 'junit.xml', text: """Details about failure """ junit 'junit.xml' } } Map multi_junit = [ 'junit_1': publicjJunit_test(), 'junit_2': publicjJunit_test(), 'junit_3': publicjJunit_test()] }}
[JIRA] (JENKINS-40771) Pipeline causes job to hang infinitely on Jenkins restart
Title: Message Title
Matthew Hall commented on JENKINS-40771
Re: Pipeline causes job to hang infinitely on Jenkins restart
This is another case, i've copied the following from JENKINS-33761
Hello, I have recently also come across the bug of jobs not restarting, I can also provide a testcase to help with investigation, three jobs are required:
Job 1 will trigger job_40_sec and job_50_sec in parallel
If jenkins restarts or is killed when job_40_sec and job_50_sec are both running, then, when Jenkins comes back online only one of the jobs is restarted whilst the other hangs indefinitely
Please let me know if you need any more information or if this is the wrong place for this information
Pipeline scripts:
Job 1
Map parallel_jobs = ['branch_1': {build job: 'job_50_sec'},
'branch_2': {build job: 'job_40_sec'}]
parallel parallel_jobs
job_40_sec
node { sleep(40) }
job_50_sec
node { sleep(50) }
Add Comment
[JIRA] (JENKINS-33761) Ability to disable "resume" build.
Title: Message Title
Matthew Hall commented on JENKINS-33761
Re: Ability to disable "resume" build.
Hello, I have recently also come across the bug of jobs not restarting, I can also provide a testcase to help with investigation, three jobs are required: Job 1 will trigger job_40_sec and job_50_sec in parallel If jenkins restarts or is killed when job_40_sec and job_50_sec are both running, then, when Jenkins comes back online only one of the jobs is restarted whilst the other hangs indefinitely Please let me know if you need any more information or if this is the wrong place for this information Pipeline scripts: Job 1
Map parallel_jobs = ['branch_1': {build job: 'job_50_sec'},
'branch_2': {build job: 'job_40_sec'}]
parallel parallel_jobs
job_40_sec
node { sleep(40) }
job_50_sec
node { sleep(50) }
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36243) ArrayIndexOutOfBoundsException with matrix and multiple simultaneous builds
Title: Message Title
Matthew Hall edited a comment on JENKINS-36243
Re: ArrayIndexOutOfBoundsException with matrix and multiple simultaneous builds
This problem can also occur in pipeline jobs.Specifically it happens if a pipeline job is forcibly killed, via the 'Click here to forcibly kill entire build' and then build it again:[Pipeline] Allocate node : StartRunning on jslave [agent - lin3 name] in ~ / home/siadmin/jenkins/w/jendev/ll_self_host_12345 job_name @2[Pipeline] node {[Pipeline] Change current directory : StartRunning in / home path / siadmin/jenkins/w/jendev/ll_self_host_12345 job_name @2/ job_dsl dir_name [Pipeline] dir {[Pipeline] checkout[Pipeline] } //dir[Pipeline] Change current directory : End[Pipeline] } //node[Pipeline] Allocate node : End[Pipeline] End of Pipelinejava.lang.ArrayIndexOutOfBoundsException: 1 at org.jenkinsci.plugins.p4.tasks.AbstractTask.setEnvironment(AbstractTask.java:109) at org.jenkinsci.plugins.p4.PerforceScm.checkout(PerforceScm.java:292) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:109) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:83) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:73) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:49) at hudson.security.ACL.impersonate(ACL.java:213) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745)Finished: FAILURE
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36243) ArrayIndexOutOfBoundsException with matrix and multiple simultaneous builds
Title: Message Title
Matthew Hall edited a comment on JENKINS-36243
Re: ArrayIndexOutOfBoundsException with matrix and multiple simultaneous builds
This problem can also occur in pipeline jobs.Specifically it happens if a pipeline job is forcibly killed, via the 'Click here to forcibly kill entire build' and then build it again: [Pipeline] Allocate node : StartRunning on jslave-lin3 in /home/siadmin/jenkins/w/jendev/ll_self_host_12345@2[Pipeline] node {[Pipeline] Change current directory : StartRunning in /home/siadmin/jenkins/w/jendev/ll_self_host_12345@2/job_dsl[Pipeline] dir {[Pipeline] checkout[Pipeline] } //dir[Pipeline] Change current directory : End[Pipeline] } //node[Pipeline] Allocate node : End[Pipeline] End of Pipelinejava.lang.ArrayIndexOutOfBoundsException: 1 at org.jenkinsci.plugins.p4.tasks.AbstractTask.setEnvironment(AbstractTask.java:109) at org.jenkinsci.plugins.p4.PerforceScm.checkout(PerforceScm.java:292) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:109) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:83) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:73) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:49) at hudson.security.ACL.impersonate(ACL.java:213) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745)Finished: FAILURE
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36243) ArrayIndexOutOfBoundsException with matrix and multiple simultaneous builds
Title: Message Title
Matthew Hall edited a comment on JENKINS-36243
Re: ArrayIndexOutOfBoundsException with matrix and multiple simultaneous builds
This problem can also occur in pipeline jobs.Specifically it happens if a pipeline job is forcibly killed, via the 'Click here to forcibly kill entire build' and then rerun build it again:[Pipeline] Allocate node : StartRunning on jslave-lin3 in /home/siadmin/jenkins/w/jendev/ll_self_host_12345@2[Pipeline] node {[Pipeline] Change current directory : StartRunning in /home/siadmin/jenkins/w/jendev/ll_self_host_12345@2/job_dsl[Pipeline] dir {[Pipeline] checkout[Pipeline] } //dir[Pipeline] Change current directory : End[Pipeline] } //node[Pipeline] Allocate node : End[Pipeline] End of Pipelinejava.lang.ArrayIndexOutOfBoundsException: 1 at org.jenkinsci.plugins.p4.tasks.AbstractTask.setEnvironment(AbstractTask.java:109) at org.jenkinsci.plugins.p4.PerforceScm.checkout(PerforceScm.java:292) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:109) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:83) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:73) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:49) at hudson.security.ACL.impersonate(ACL.java:213) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745)Finished: FAILURE
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36243) ArrayIndexOutOfBoundsException with matrix and multiple simultaneous builds
Title: Message Title Matthew Hall commented on JENKINS-36243 Re: ArrayIndexOutOfBoundsException with matrix and multiple simultaneous builds This problem can also occur in pipeline jobs. Specifically it happens if a pipeline job is forcibly killed, via the 'Click here to forcibly kill entire build' and then rerun Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
