[JIRA] (JENKINS-38765) Stage view renders incorrectly with stages appearing multiple times.
Title: Message Title Nick Sonneveld commented on JENKINS-38765 Re: Stage view renders incorrectly with stages appearing multiple times. Sam Van Oort Unfortunately I still see this behaviour. This is with the new workflow-api 2.8 (all other plugins are up to date as well) 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-38765) Stage view renders incorrectly with stages appearing multiple times.
Title: Message Title Nick Sonneveld updated an issue Jenkins / JENKINS-38765 Stage view renders incorrectly with stages appearing multiple times. Change By: Nick Sonneveld Attachment: Screen Shot 2016-12-02 at 5.59.45 PM.png 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-39092) Pipeline branches SCM polling properties for multibranch has broken behaviour.
Title: Message Title Nick Sonneveld commented on JENKINS-39092 Re: Pipeline branches SCM polling properties for multibranch has broken behaviour. Hrm just witnessed this behaviour again today. Haven't had a chance to install a fresh jenkins install to try to find a test case yet. 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-37219) Option to suppress automatic SCM trigger from Jenkinsfile
Title: Message Title Nick Sonneveld commented on JENKINS-37219 Re: Option to suppress automatic SCM trigger from Jenkinsfile Andrew Bayer Possibly some issues related to this in JENKINS-39092 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-39232) unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave
Title: Message Title Nick Sonneveld commented on JENKINS-39232 Re: unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave I can confirm that changing our slave startup script from javaws http://jenkins.internal:8080/computer/win-app01.bld/slave-agent.jnlp to java -jar slave.jar -jnlpUrl http://jenkins.internal:8080/computer/win-app01.bld/slave-agent.jnlp seems to allow our slaves to connect now. 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-39232) unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave
Title: Message Title Nick Sonneveld commented on JENKINS-39232 Re: unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave I've tested this with Jenkins 2.28 but I still see the same error: JNLP agent connected from /192.168.12.3 <===[JENKINS REMOTING CAPACITY]===>Slave.jar version: 3.0 This is a Windows agent java.net.MalformedURLException: no protocol: jnlpJars/slave.jar I am running the master with -Djenkins.slaves.DefaultJnlpSlaveReceiver.disableStrictVerification=true Commenting here because JENKINS-39246 was marked as a duplicate. 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-38721) Viewing canceled Pipeline jobs can get NPE from UserInterruption/summary.groovy
Title: Message Title Nick Sonneveld commented on JENKINS-38721 Re: Viewing canceled Pipeline jobs can get NPE from UserInterruption/summary.groovy I haven't tried from scratch. We do run Jenkins internally with zero security enabled. Everyone is an anonymous user which might explain why User.get is null. 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-38721) Viewing canceled Pipeline jobs can get NPE from UserInterruption/summary.groovy
Title: Message Title Nick Sonneveld edited a comment on JENKINS-38721 Re: Viewing canceled Pipeline jobs can get NPE from UserInterruption/summary.groovy [~jglick] I haven't tried from scratch. We do run Jenkins internally with zero security enabled. Everyone is an anonymous user which might explain why User.get is null. 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-39092) Pipeline branches SCM polling properties for multibranch has broken behaviour.
Title: Message Title
Nick Sonneveld updated an issue
Jenkins / JENKINS-39092
Pipeline branches SCM polling properties for multibranch has broken behaviour.
Change By:
Nick Sonneveld
We're attempting to configure a pipeline multibranch folder such that 'default' is always built but feature branches are only built daily. We did this by suppressing automatic SCM triggering for all branches except 'default', then configuring a separate pollSCM in the jenkinsfile for each branch. However we're seeing issues where feature branches that have changes are not built for days while sometimes a branch will be triggered many times for the same changeset.Multiple jobs for the same changeset are triggered. The first by "Branch indexing" and the later ones by "Started by an SCM change". The logs show "Dependent changes detected"No other polling is configured. Removing the pipelineTriggers/pollSCM property seems to stop repeat builds (but won't give you daily builds) Our Jenkinsfile starts with this:{noformat}def alwaysBuild = (env.BRANCH_NAME == "default" || env.BRANCH_NAME ==~ /CompanyName-.*/);properties([overrideIndexTriggers(alwaysBuild), pipelineTriggers([pollSCM('@daily')])]);{noformat}Multibranch folder is configured with properties overrides:- "named branches get different properties" exceptions: "default": no properties "us*,d*,ts*": Suppess automatic SCM triggering.And every commit will notify jenkins via {noformat}curl -v http://jenkins:8080/mercurial/notifyCommit?url="">{noformat}
Add Comment
This message was
[JIRA] (JENKINS-38443) Pollscm trigger runs the job twice for the same commit
Title: Message Title Nick Sonneveld commented on JENKINS-38443 Re: Pollscm trigger runs the job twice for the same commit Linking to related JENKINS-39092 . The difference is that no polling interval is set, only change notifications 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-39092) Pipeline branches SCM polling properties for multibranch has broken behaviour.
Title: Message Title
Nick Sonneveld created an issue
Jenkins / JENKINS-39092
Pipeline branches SCM polling properties for multibranch has broken behaviour.
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
build 125 Screen Shot 2016-10-19 at 4.11.14 PM.png, build 126 Screen Shot 2016-10-19 at 4.11.28 PM.png, job config - Screen Shot 2016-10-19 at 4.09.04 PM.png, multibranch config Screen Shot 2016-10-19 at 4.10.24 PM.png, multiple builds - Screen Shot 2016-10-19 at 4.10.53 PM.png
Components:
mercurial-plugin, pipeline, workflow-multibranch-plugin
Created:
2016/Oct/19 5:28 AM
Environment:
Jenkins 2.26
Priority:
Critical
Reporter:
Nick Sonneveld
We're attempting to configure a pipeline multibranch folder such that 'default' is always built but feature branches are only built daily. However we're seeing issues where feature branches that have changes are not built for days while sometimes a branch will be triggered many times for the same changeset. Multiple jobs for the same changeset are triggered. The first by "Branch indexing" and the later ones by "Started by an SCM change". The logs show "Dependent changes detected" No other polling is configured. Our Jenkinsfile starts with this:
def alwaysBuild = (env.BRANCH_NAME == "default" || env.BRANCH_NAME ==~ /CompanyName-.*/);
properties([overrideIndexTriggers(alwaysBuild), pipelineTriggers([pollSCM('@daily')])]);
[JIRA] (JENKINS-39081) Cannot get property 'fullName' on null object
Title: Message Title Nick Sonneveld commented on JENKINS-39081 Re: Cannot get property 'fullName' on null object Duplicates JENKINS-38721 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-38720) 500 Server Error when notifying master of new mercurial commit: "Response header too large"
Title: Message Title Nick Sonneveld commented on JENKINS-38720 Re: 500 Server Error when notifying master of new mercurial commit: "Response header too large" Jesse Glick Hrm, I wonder if you can generate the "Response header too large" exception while adding properties to the header. It looks like the size isn't checked until the header is flushed just before the body starts being written. I'm certainly not checking the results in the header but others might. Should it just be a cap with no warning? Or should there be a further header with number of projects triggered? (with a possible "truncated" property as well?) 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-38720) 500 Server Error when notifying master of new mercurial commit: "Response header too large"
Title: Message Title Nick Sonneveld commented on JENKINS-38720 Re: 500 Server Error when notifying master of new mercurial commit: "Response header too large" Jesse Glick hah, I know. It was my attempt to de-identify the logs. They are all unique job names however. 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-38765) Stage view renders incorrectly with stages appearing multiple times.
Title: Message Title Nick Sonneveld updated an issue Jenkins / JENKINS-38765 Stage view renders incorrectly with stages appearing multiple times. Change By: Nick Sonneveld Summary: Stage view renders incorrectly and time doesn't update in real time with stages appearing multiple times . 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-38765) Stage view renders incorrectly with stages appearing multiple times.
Title: Message Title
Nick Sonneveld updated an issue
Jenkins / JENKINS-38765
Stage view renders incorrectly with stages appearing multiple times.
Change By:
Nick Sonneveld
Attached is a screenshot of the stage view rendering weird. The time for the current stage doesn't seem to update either. Sometimes refreshing the page helps (but not always!).Our jenkinsfile essentially looks like this:{noformat}#!groovynode('linux') {stage("Checkout") {commitTag = checkout...}stage("Build") {parallel (// )}}stage("Docker") {node('docker') {// }}stage("Tests") {parallel (// )}{noformat}_javascript_ console shows this log:{noformat}stageview.js:4557 No "data-stageId" on stage.stageview.js:4557 No "data-stageId" on stage.{noformat} but this doesn't seem to be related to the issue.
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
[JIRA] (JENKINS-38765) Stage view renders incorrectly and time doesn't update in real time.
Title: Message Title Nick Sonneveld commented on JENKINS-38765 Re: Stage view renders incorrectly and time doesn't update in real time. Sam Van Oort Yes I think that's what I mean. Most of our stages involve a parallel step so I didn't think to blame that for the lack of updates. I'll update ticket to only include rendering issues. 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-38765) Stage view renders incorrectly and time doesn't update in real time.
Title: Message Title
Nick Sonneveld updated an issue
Jenkins / JENKINS-38765
Stage view renders incorrectly and time doesn't update in real time.
Change By:
Nick Sonneveld
Attached is a screenshot of the stage view rendering weird. The time for the current stage doesn't seem to update either. Sometimes refreshing the page helps (but not always!) .Our jenkinsfile essentially looks like this:{noformat}#!groovynode('linux') {stage("Checkout") {commitTag = checkout...}stage("Build") {parallel (// )}}stage("Docker") {node('docker') {// }}stage("Tests") {parallel (// )}{noformat}_javascript_ console shows this log:{noformat}stageview.js:4557 No "data-stageId" on stage.stageview.js:4557 No "data-stageId" on stage.{noformat}
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
[JIRA] (JENKINS-38765) Stage view renders incorrectly and time doesn't update in real time.
Title: Message Title
Nick Sonneveld updated an issue
Jenkins / JENKINS-38765
Stage view renders incorrectly and time doesn't update in real time.
Change By:
Nick Sonneveld
Attached is a screenshot of the stage view rendering weird. The time for the current stage doesn't seem to update either. Sometimes refreshing the page helps. Our jenkinsfile essentially looks like this:{noformat}#!groovynode('linux') {stage("Checkout") {commitTag = swcheckout(false) checkout... }stage("Build") {parallel (// )}}stage("Docker") {node('docker') {// }}stage("Tests") {parallel (// )}{noformat} _javascript_ console shows this log:{noformat}stageview.js:4557 No "data-stageId" on stage.stageview.js:4557 No "data-stageId" on stage.{noformat}
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
[JIRA] (JENKINS-38765) Stage view renders incorrectly and time doesn't update in real time.
Title: Message Title Nick Sonneveld updated an issue Jenkins / JENKINS-38765 Stage view renders incorrectly and time doesn't update in real time. Change By: Nick Sonneveld Attachment: jenkins_weird_stage_rendering_2.png 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-38765) Stage view renders incorrectly and time doesn't update in real time.
Title: Message Title
Nick Sonneveld created an issue
Jenkins / JENKINS-38765
Stage view renders incorrectly and time doesn't update in real time.
Issue Type:
Bug
Assignee:
Sam Van Oort
Attachments:
jenkins_weird_stage_rendering.png
Components:
pipeline, pipeline-stage-view-plugin
Created:
2016/Oct/06 1:06 AM
Environment:
Jenkins 2.24 stageview plugin 2.1
Labels:
pipeline pipeline-stage-view
Priority:
Major
Reporter:
Nick Sonneveld
Attached is a screenshot of the stage view rendering weird. The time for the current stage doesn't seem to update either. Our jenkinsfile essentially looks like this:
#!groovy
node('linux') {
stage("Checkout") {
commitTag = swcheckout(false)
}
stage("Build") {
parallel (
//
)
}
}
stage("Docker") {
node('docker') {
//
}
}
stage("Tests") {
parallel (
//
)
}
[JIRA] (JENKINS-38720) 500 Server Error when notifying master of new mercurial commit: "Response header too large"
Title: Message Title Nick Sonneveld updated an issue Jenkins / JENKINS-38720 500 Server Error when notifying master of new mercurial commit: "Response header too large" Change By: Nick Sonneveld Summary: 500 Server Error when notifying master of new mercurial commit : "Response header too large" 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-38721) Viewing canceled pipeline jobs can raise org.apache.commons.jelly.JellyTagException.
Title: Message Title Nick Sonneveld updated an issue Jenkins / JENKINS-38721 Viewing canceled pipeline jobs can raise org.apache.commons.jelly.JellyTagException. Change By: Nick Sonneveld Summary: Viewing canceled pipeline jobs can raise exception org . apache.commons.jelly.JellyTagException. 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-38721) Viewing canceled pipeline jobs can raise exception.
Title: Message Title Nick Sonneveld created an issue Jenkins / JENKINS-38721 Viewing canceled pipeline jobs can raise exception. Issue Type: Bug Assignee: Unassigned Attachments: jenkins_view_job_error.log Components: core, pipeline, workflow-job-plugin Created: 2016/Oct/05 5:43 AM Environment: Jenkins 2.24, workflow-job 2.7, Linux vmkvmx02 3.10.0-327.el7.x86_64 #1 SMP Thu Oct 29 17:29:29 EDT 2015 x86_64 x86_64 x86_64 GNU/Linux Labels: exception pipeline Priority: Critical Reporter: Nick Sonneveld Sometimes when viewing cancelled pipeline jobs, an exception is shown. I'm not sure if it's all cancelled jobs or just particular ones. Can still view console logs by entering url in manually. javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/home/jenkins/plugins/workflow-job/WEB-INF/lib/workflow-job.jar!/org/jenkinsci/plugins/workflow/job/WorkflowRun/index.jelly:63:93: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.24.jar!/lib/hudson/summary.jelly:105:31: Cannot get property 'fullName' on null object
[JIRA] (JENKINS-38720) 500 Server Error when notifying master of new mercurial commit
Title: Message Title Nick Sonneveld updated an issue Jenkins / JENKINS-38720 500 Server Error when notifying master of new mercurial commit Change By: Nick Sonneveld Labels: exception mercurial scm 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-38720) 500 Server Error when notifying master of new mercurial commit
Title: Message Title Nick Sonneveld updated an issue Jenkins / JENKINS-38720 500 Server Error when notifying master of new mercurial commit Change By: Nick Sonneveld Summary: 500 Server Error when notifying Jenkins master of new mercurial commit 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-38720) 500 Server Error when notifying Jenkins of new mercurial commit
Title: Message Title Nick Sonneveld created an issue Jenkins / JENKINS-38720 500 Server Error when notifying Jenkins of new mercurial commit Issue Type: Bug Assignee: Unassigned Attachments: jenkins_notify.log Components: core, mercurial-plugin Created: 2016/Oct/05 5:33 AM Environment: Jenkins 2.24, Linux vmkvmx01 2.6.32-431.29.2.el6.x86_64 #1 SMP Sun Jul 27 15:55:46 EDT 2014 x86_64 x86_64 x86_64 GNU/Linux Priority: Major Reporter: Nick Sonneveld Notifying Jenkins of a new mercurial commit via /mercurial/notifyCommit responds with a '500 Server Error'. It looks like the notification is accepted in the Jenkins logs but an exception is also raised. The logs also show all the job polling that is triggered, perhaps related to the issue? curl -v http://jenkins.bld.cbr.internal.example.com:8080/mercurial/notifyCommit?url="" * Trying 192.168.12.1... * Connected to jenkins.bld.cbr.internal.example.com (192.168.12.1) port 8080 (#0) > GET /mercurial/notifyCommit?url="" HTTP/1.1 > Host: jenkins.bld.cbr.internal.example.com:8080 > User-Agent: curl/7.43.0 > Accept: */* > < HTTP/1.1 500 Server Error < Connection: close < Server: Jetty(9.2.z-SNAPSHOT) < * Closing connection 0 Log snippet:
[JIRA] (JENKINS-38443) Pollscm trigger runs the job twice for the same commit
Title: Message Title Nick Sonneveld edited a comment on JENKINS-38443 Re: Pollscm trigger runs the job twice for the same commit As far as I know, we're only polling "daily" per branch , configured via pollSCM . We do have a mercurial trigger hook that GETs "/mercurial/notifyCommit" for each commit but I feel that shouldn't affect things as that is just notifying jenkins that "something" changed . The parent multibranch job does not have any polling configured. 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-38443) Pollscm trigger runs the job twice for the same commit
Title: Message Title Nick Sonneveld reopened an issue Jenkins / JENKINS-38443 Pollscm trigger runs the job twice for the same commit Change By: Nick Sonneveld Resolution: Not A Defect Status: Resolved Reopened 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-38443) Pollscm trigger runs the job twice for the same commit
Title: Message Title Nick Sonneveld edited a comment on JENKINS-38443 Re: Pollscm trigger runs the job twice for the same commit As far as I know, we're only polling "daily" per branch. We do have a mercurial trigger for each commit but I feel that shouldn't affect things. The parent multibranch job does not have any polling configured. 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-38443) Pollscm trigger runs the job twice for the same commit
Title: Message Title Nick Sonneveld commented on JENKINS-38443 Re: Pollscm trigger runs the job twice for the same commit As far as I know, we're only polling "daily" per branch. We do have a mercurial trigger for each commit but I feel that shouldn't affect things. 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-38443) Pollscm trigger runs the job twice for the same commit
Title: Message Title Nick Sonneveld updated an issue Jenkins / JENKINS-38443 Pollscm trigger runs the job twice for the same commit Change By: Nick Sonneveld Component/s: pipeline 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-38443) Pollscm trigger runs the job twice for the same commit
Title: Message Title Nick Sonneveld edited a comment on JENKINS-38443 Re: Pollscm trigger runs the job twice for the same commit When I had a pipeline job's PollSCM property configured with "@daily", I witnessed 7 builds triggered for the same changeset. All were "Started by an SCM change". Is it possible that PollSCM isn't checking for a running build with that changeset? Although why would it attempt to build more than once a day? 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-38443) Pollscm trigger runs the job twice for the same commit
Title: Message Title Nick Sonneveld commented on JENKINS-38443 Re: Pollscm trigger runs the job twice for the same commit When I had a job's PollSCM property configured with "@daily", I witnessed 7 builds triggered for the same changeset. All were "Started by an SCM change". Is it possible that PollSCM isn't checking for a running build with that changeset? Although why would it attempt to build more than once a day? 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-37219) Option to suppress automatic SCM trigger from Jenkinsfile
Title: Message Title
Nick Sonneveld commented on JENKINS-37219
Re: Option to suppress automatic SCM trigger from Jenkinsfile
So if I wanted new branches to be built but all further changes to be built daily, would I use this property in the Jenkinsfile?:
properties([overrideIndexTriggers(false), pipelineTriggers([pollSCM('@daily')])])
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-36813) Re-run particular steps or stage
Title: Message Title Nick Sonneveld commented on JENKINS-36813 Re: Re-run particular steps or stage This is something they won't do in the open source solution. See https://issues.jenkins-ci.org/browse/JENKINS-33846 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-22971) Show full project name when project is in a folder
Title: Message Title Nick Sonneveld updated an issue Jenkins / JENKINS-22971 Show full project name when project is in a folder Change By: Nick Sonneveld *strong text* Currently, Jenkins shows the full, real name of a project when a display name is set on its index page.The same should be done for projects (display name set of not) that are not immediate children of Jenkins, e.g. in a folder, because the full, real name may be needed for build triggers, copy artifact build steps, etc. 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-22971) Show full project name when project is in a folder
Title: Message Title Nick Sonneveld updated an issue Jenkins / JENKINS-22971 Show full project name when project is in a folder Change By: Nick Sonneveld *strong text* Currently, Jenkins shows the full, real name of a project when a display name is set on its index page.The same should be done for projects (display name set of not) that are not immediate children of Jenkins, e.g. in a folder, because the full, real name may be needed for build triggers, copy artifact build steps, etc. 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-29037) Add Max interval to waitUntil
Title: Message Title Nick Sonneveld edited a comment on JENKINS-29037 Re: Add Max interval to waitUntil There's a pull request against this issue https://issues.jenkins-ci.org/browse/JENKINS-34554 . It simply adds a limit. 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-29037) Add Max interval to waitUntil
Title: Message Title Nick Sonneveld commented on JENKINS-29037 Re: Add Max interval to waitUntil There's a pull request against this issue https://issues.jenkins-ci.org/browse/JENKINS-34554 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] [workflow-plugin] (JENKINS-34554) workflow-basic-steps-plugin "waitUtil" should have a MAX_RECURRENCE_PERIOD
Title: Message Title Nick Sonneveld updated an issue Jenkins / JENKINS-34554 workflow-basic-steps-plugin "waitUtil" should have a MAX_RECURRENCE_PERIOD Change By: Nick Sonneveld Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-34554) workflow-basic-steps-plugin "waitUtil" should have a MAX_RECURRENCE_PERIOD
Title: Message Title Nick Sonneveld commented on JENKINS-34554 Re: workflow-basic-steps-plugin "waitUtil" should have a MAX_RECURRENCE_PERIOD Implementation pull request https://github.com/jenkinsci/workflow-basic-steps-plugin/pull/7 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [parallel-test-executor-plugin] (JENKINS-34901) Continue parallel stage even if previous stage failed
Title: Message Title Nick Sonneveld assigned an issue to Nick Sonneveld Jenkins / JENKINS-34901 Continue parallel stage even if previous stage failed Change By: Nick Sonneveld Assignee: Sam Van Oort Nick Sonneveld Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [parallel-test-executor-plugin] (JENKINS-34901) Continue parallel stage even if previous stage failed
Title: Message Title Nick Sonneveld assigned an issue to Sam Van Oort Jenkins / JENKINS-34901 Continue parallel stage even if previous stage failed Change By: Nick Sonneveld Assignee: Nick Sonneveld Sam Van Oort Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [durable-task-plugin] (JENKINS-34150) Pipeline Batch hangs
Title: Message Title Nick Sonneveld commented on JENKINS-34150 Re: Pipeline Batch hangs There is a pull request being worked on by Martin Karing you might want to look at and comment on. Link is attached to this issue https://github.com/jenkinsci/durable-task-plugin/pull/21 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [durable-task-plugin] (JENKINS-34150) Pipeline Batch hangs
Title: Message Title Nick Sonneveld commented on JENKINS-34150 Re: Pipeline Batch hangs Another workaround that doesn't involved deleting jobs (but isn't a long term solution) is to realise that batch steps create two batch files in the @tmp directory (which is relative to where batch is run, so it might be in the workspace if you've changed the directory, or just outside it): a jenkins-main.bat and a jenkins-wrap.bat. The main bat file contains your commands. The wrap bat file will run the main bat, pipe output to a log file and finally writes a result file. The bug concerns the wrap bat file not completing so the result file is never written. You can search for the file and run the final line manually (looks like echo %errorlevel% > ...\jenkins-result.txt), or run the wrap batch file again if you don't mind it performing the same operation again. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [durable-task-plugin] (JENKINS-34150) Pipeline Batch hangs
Title: Message Title Nick Sonneveld edited a comment on JENKINS-34150 Re: Pipeline Batch hangs Another workaround that doesn't involved involve deleting jobs (but also isn't a long term solution) is to realise that batch steps create two batch files in the @tmp directory (which is relative to where batch is run, so it might be in the workspace if you've changed the directory, or just outside it): a jenkins-main.bat and a jenkins-wrap.bat. The main bat file contains your commands. The wrap bat file will run the main bat, pipe output to a log file and finally writes a result file.The bug concerns the wrap bat file not completing so the result file is never written. You can search for the file and run the final line manually (looks like echo %errorlevel% > ...\jenkins-result.txt), or run the wrap batch file again if you don't mind it performing the same operation again. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [durable-task-plugin] (JENKINS-34150) Pipeline Batch hangs
Title: Message Title
Nick Sonneveld edited a comment on JENKINS-34150
Re: Pipeline Batch hangs
I have mentioned in other related tickets but I just want to point out that I have seen this behaviour with a linux master and multiple windows agents (with 5-10 executors on each). You could try this example code. I haven't tested it but it's similar to our Jenkinsfile where we have branches doing chunks of a test. Cancelling the job in the middle of execution sometimes puts the agents in a weird state too.{code:java}def branches = [:]for (int i = 0; i < 64; i++) { def id = "branch-${i}" branches[id] = {node ('windows') { for (int j = 0; j < 8; j++) { bat 'ping 127.0.0.1 -n 10' } }} } parallel branches{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [durable-task-plugin] (JENKINS-34150) Pipeline Batch hangs
Title: Message Title
Nick Sonneveld commented on JENKINS-34150
Re: Pipeline Batch hangs
I have mentioned in other related tickets but I just want to point out that I have seen this behaviour with a linux master and multiple windows agents (with 5-10 executors on each). You could try this example code. I haven't tested it but it's similar to our Jenkinsfile where we have branches doing chunks of a test. Cancelling the job in the middle of execution sometimes puts the agents in a weird state too.
def branches = [:]
for (int i = 0; i < 64; i++) {
def id = "branch-${i}"
branches[id]
node ('windows') {
for (int j = 0; j < 8; j++) {
bat 'ping 127.0.0.1 -n 10'
}
}
}
parallel branches
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [workflow-plugin] (JENKINS-34554) workflow-basic-steps-plugin "waitUtil" should have a MAX_RECURRENCE_PERIOD
Title: Message Title Nick Sonneveld updated an issue Jenkins / JENKINS-34554 workflow-basic-steps-plugin "waitUtil" should have a MAX_RECURRENCE_PERIOD Change By: Nick Sonneveld It would be helpful if waitUntil had a fixed MAX_RECURRENCE_PERIOD (of say a minute) or a parameter to specify the max period. I've seen the period get up to - 8 - 30 minutes while waiting for a longer job parallel branch to finish. I noticed that restarting jenkins master reset the delay. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-34554) workflow-basic-steps-plugin "waitUtil" should have a MAX_RECURRENCE_PERIOD
Title: Message Title Nick Sonneveld created an issue Jenkins / JENKINS-34554 workflow-basic-steps-plugin "waitUtil" should have a MAX_RECURRENCE_PERIOD Issue Type: Improvement Assignee: Jesse Glick Components: workflow-plugin Created: 2016/May/03 7:01 AM Environment: Jenkins 2.1 Labels: workflow pipeline Priority: Minor Reporter: Nick Sonneveld It would be helpful if waitUntil had a fixed MAX_RECURRENCE_PERIOD (of say a minute) or a parameter to specify the max period. I've seen the period get up to 8 minutes while waiting for a longer job to finish.
[JIRA] [workflow-plugin] (JENKINS-34501) Steps that accept closure overwrite parallel branch context logs
Title: Message Title Nick Sonneveld created an issue Jenkins / JENKINS-34501 Steps that accept closure overwrite parallel branch context logs Issue Type: Bug Assignee: Jesse Glick Attachments: jenkins-step-closure-loses-parallel-log.groovy, jenkins-step-closure-loses-parallel-log.log Components: workflow-plugin Created: 2016/Apr/29 2:09 AM Environment: Jenkins 2.0, Pipeline plugins 2.0, Linux master, Windows slaves Labels: workflow pipeline Priority: Major Reporter: Nick Sonneveld When within a parallel branch and using steps that accept a closure (such as 'withEnv', 'dir' or 'timeout') the parallel context prepended in log is lost after the step has completed. This doesn't happen if a closure is called directly.
[JIRA] [workflow-plugin] (JENKINS-34489) Pipeline 'bat' does not terminate immediately
Title: Message Title Nick Sonneveld created an issue Jenkins / JENKINS-34489 Pipeline 'bat' does not terminate immediately Issue Type: Bug Assignee: Jesse Glick Attachments: jenkins-capture-error-error.log, jenkins-capture-error-failed-to-terminate-at-all.log, jenkins-capture-error-succes.log, jenkins-capture-error.groovy Components: workflow-plugin Created: 2016/Apr/28 7:49 AM Environment: Jenkins 2.0, Windows 2012 R2 Labels: workflow pipeline Priority: Major Reporter: Nick Sonneveld When a pipeline job is terminated while executing a batch script, it will sometimes continue running the batch file after terminating the batch file's child process. This means you cannot reliably check if the process was terminated by Jenkins or if
[JIRA] [workflow-plugin] (JENKINS-34376) Cannot easily/safely catch exceptions without disrupting job abortion
Title: Message Title Nick Sonneveld updated an issue Jenkins / JENKINS-34376 Cannot easily/safely catch exceptions without disrupting job abortion Change By: Nick Sonneveld Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-34488) Failing 'assert' hangs the pipeline
Title: Message Title Nick Sonneveld created an issue Jenkins / JENKINS-34488 Failing 'assert' hangs the pipeline Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 2016/Apr/28 5:23 AM Environment: Jenkins 2.0, pipeline 2.0 plugins Labels: workflow pipeline Priority: Major Reporter: Nick Sonneveld Having a failing assert hangs the pipeline for me. Requires a hard kill in order to stop it. Test pipeline script: assert false
[JIRA] [durable-task-plugin] (JENKINS-33164) Pipeline bat stuck on Windows Server 2012
Title: Message Title Nick Sonneveld edited a comment on JENKINS-33164 Re: Pipeline bat stuck on Windows Server 2012 Sorry that might be a red herring. I have been testing exclusively with a Linux master and a combination of linux and windows nodes. I still see this behaviour. edit1: However, I usually see it after running many batch scripts (around 400) on 30 executors across 4 nodes. edit2: It might also involve terminating jobs in the middle of running scripts Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [durable-task-plugin] (JENKINS-33164) Pipeline bat stuck on Windows Server 2012
Title: Message Title Nick Sonneveld edited a comment on JENKINS-33164 Re: Pipeline bat stuck on Windows Server 2012 Sorry that might be a red herring. I have been testing exclusively with a Linux master and a combination of linux and windows nodes. I still see this behaviour. However, I usually see it after running many batch scripts (around 400) on 30 executors across 4 nodes. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [durable-task-plugin] (JENKINS-33164) Pipeline bat stuck on Windows Server 2012
Title: Message Title Nick Sonneveld commented on JENKINS-33164 Re: Pipeline bat stuck on Windows Server 2012 Sorry that might be a red herring. I have been testing exclusively with a Linux master and a combination of linux and windows nodes. I still see this behaviour. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-34414) Code that raises groovy.lang.MissingMethodException will prevent parallel from finishing
Title: Message Title Nick Sonneveld created an issue Jenkins / JENKINS-34414 Code that raises groovy.lang.MissingMethodException will prevent parallel from finishing Issue Type: Bug Assignee: Jesse Glick Attachments: jenkins-parallel-freeze.groovy, jenkins-parallel-freeze.log Components: workflow-plugin Created: 2016/Apr/24 4:17 AM Environment: Jenkins 2.0, pipeline 2.0, rhel 6.5(hosted on), safari Priority: Minor Reporter: Nick Sonneveld I have provided example code that seems to freeze a parallel pipeline job. I am unable to kill it unless I restart Jenkins first. Attached is example code. It raises a MissingMethodException (through a bad calling of timeout). I would expect the parallel step to end.
[JIRA] [workflow-plugin] (JENKINS-34376) Cannot easily/safely catch exceptions without disrupting job abortion
Title: Message Title
Nick Sonneveld updated an issue
Jenkins / JENKINS-34376
Cannot easily/safely catch exceptions without disrupting job abortion
Change By:
Nick Sonneveld
There doesn't seem to be a safe method of catching errors that might occur while running a shell command without disrupting the normal job stopping process. I would like to be able to catch the error (as it might just be a failing test), log it, and continue running the pipeline script. My main concern is being able to still allow stopping or aborting the pipeline. This would suggest to me that I need to allow exceptions to bubble up if it is due to an abort.Manually aborting (by pressing red stop button in the gui) will either raise an AbortException or a FlowInterruptedException depending on whether the pipeline is running a shell command or not. This makes it difficult to determine if the shell command failed or a job abort was requested. If a shell command is aborted, the AbortException will at least have a message about an exit code 143. (I _think_)To further confuse things, I am wrapping some shell scripts with a timeout step. Timeout also raises FlowInterruptedException but at least the exception will have ExceededTimeout as the cause.I thought maybe I could look at currentBuild.result but it seems to be always null. I looked at 'catchError' but that doesn't set the result to 'ABORTED' when stopping during a shell command. (It also seems to ignore when a user is trying to abort the job)Basically, to be able to recover from errors but also allow stopping pipelines, I think I have to use this monstrosity:{code: groovy java }onErrorMarkUnstable("sleep step") {// stopping here raises FlowInterruptedExceptionsleep 10}onErrorMarkUnstable("sleep shell") {node {// error here raises AbortException, stopping here raises AbortException// a script that fails.. we want to be able to log that it failed and continue testing.sh "sleep 10 && false"}}onErrorMarkUnstable("sleep shell with timeout") {// we want to log that it timed out and continue.timeout (time: 5, unit: 'SECONDS') {node {// error here raises AbortException, stopping here raises AbortException, timeout raises FlowInterruptedExceptionsh "sleep 10 && false"}}}echo "last line, done!"def onErrorMarkUnstable(desc, Closure body) {echo "${desc}"try {body.call()} catch (org.jenkinsci.plugins.workflow.steps.FlowInterruptedException e) {def allowInterruption = true;for (int i = 0; i < e.causes.size(); i++) {// white list ExceededTimeoutif (e.causes[0] instanceof org.jenkinsci.plugins.workflow.steps.TimeoutStepExecution.ExceededTimeout) {echo "${desc}: An error occured (${e.causes[0]}) marking build as failed."currentBuild.result = "UNSTABLE"allowInterruption = false;}}if (allowInterruption) { throw e; }} catch (hudson.AbortException e) {def m = e.message =~ /(?i)script returned exit code (\d+)/if (m) {def exitcode = m.group(1).toInteger()if (exitcode >= 128) {throw e;// killed because of abort, letting through}}
[JIRA] [workflow-plugin] (JENKINS-34376) Cannot easily/safely catch exceptions without disrupting job abortion
Title: Message Title Nick Sonneveld created an issue Jenkins / JENKINS-34376 Cannot easily/safely catch exceptions without disrupting job abortion Issue Type: Improvement Assignee: Jesse Glick Components: workflow-plugin Created: 2016/Apr/21 1:58 PM Environment: Jenkins ver. 1.656, pipeline 2.0 Priority: Minor Reporter: Nick Sonneveld There doesn't seem to be a safe method of catching errors that might occur while running a shell command without disrupting the normal job stopping process. I would like to be able to catch the error (as it might just be a failing test), log it, and continue running the pipeline script. My main concern is being able to still allow stopping or aborting the pipeline. This would suggest to me that I need to allow exceptions to bubble up if it is due to an abort. Manually aborting (by pressing red stop button in the gui) will either raise an AbortException or a FlowInterruptedException depending on whether the pipeline is running a shell command or not. This makes it difficult to determine if the shell command failed or a job abort was requested. If a shell command is aborted, the AbortException will at least have a message about an exit code 143. (I think) To further confuse things, I am wrapping some shell scripts with a timeout step. Timeout also raises
[JIRA] [cucumber-reports-plugin] (JENKINS-34220) Sorting report by duration column is sorting by string, not time.
Title: Message Title Nick Sonneveld created an issue Jenkins / JENKINS-34220 Sorting report by duration column is sorting by string, not time. Issue Type: Bug Assignee: Damian Szczepanik Attachments: weird-duration-sort.png Components: cucumber-reports-plugin Created: 2016/Apr/14 4:59 AM Environment: Jenkins v1.656, cucumber reports 2.1.0 Priority: Minor Reporter: Nick Sonneveld When sorting test results by duration, it looks like it is a simple string sort instead of sorting by time. See attached screenshot.
