[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Roy Arnon commented on JENKINS-59083 Re: Builds stuck on "is already in progress" forever Actually, taking a look at it, it seems it has to do with one of our own plugins - I will look into that. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.1072.1566935520377%40Atlassian.JIRA.
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Roy Arnon commented on JENKINS-59083 Re: Builds stuck on "is already in progress" forever Yes, I do see a stack trace like that in the log: Aug 27, 2019 7:37:09 PM org.jenkinsci.plugins.workflow.job.WorkflowRun getListener WARNING: null java.lang.IllegalStateException: trying to open a build log on Lint.Hooks #1923 after it has completed at org.jenkinsci.plugins.workflow.job.WorkflowRun.getListener(WorkflowRun.java:219) at org.jenkinsci.plugins.workflow.job.WorkflowRun.access$300(WorkflowRun.java:133) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.getListener(WorkflowRun.java:955) at org.jenkinsci.plugins.workflow.cps.EnvActionImpl.getListener(EnvActionImpl.java:77) at org.jenkinsci.plugins.workflow.cps.EnvActionImpl.getEnvironment(EnvActionImpl.java:69) at org.jenkinsci.plugin.taboola.ElasticSearchManager.getConsoleEnvs(ElasticSearchManager.java:277) at org.jenkinsci.plugin.taboola.ElasticSearchManager.addCommonDataAndSend(ElasticSearchManager.java:110) at org.jenkinsci.plugin.taboola.ElasticSearchManager.sendStageData(ElasticSearchManager.java:179) at org.jenkinsci.plugin.taboola.events.TaboolaStagesListener.onNewHead(TaboolaStagesListener.java:145) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.notifyListeners(CpsFlowExecution.java:1463) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$3.run(CpsThreadGroup.java:458) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$1.run(CpsVmExecutorService.java:37) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:131) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Add Comment
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Roy Arnon commented on JENKINS-59083 Re: Builds stuck on "is already in progress" forever Hi, I can confirm that the build you've uploaded fixes the issue for us. Thanks! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.948.1566930300374%40Atlassian.JIRA.
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Roy Arnon updated an issue Jenkins / JENKINS-59083 Builds stuck on "is already in progress" forever Change By: Roy Arnon Attachment: stuck-build-2.tar.gz Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.288.1566856206445%40Atlassian.JIRA.
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Roy Arnon commented on JENKINS-59083 Re: Builds stuck on "is already in progress" forever I went ahead and reproduced it again. This time I simulated a failure in the pipeline job - you can see build #1916 waiting for the failed build #1915. I have attached the builds folder again - stuck-build-2.tar.gz Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.289.1566856207285%40Atlassian.JIRA.
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Roy Arnon updated an issue Jenkins / JENKINS-59083 Builds stuck on "is already in progress" forever Change By: Roy Arnon Attachment: stuck-build.tar.gz Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.283.1566856020304%40Atlassian.JIRA.
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Roy Arnon updated an issue Jenkins / JENKINS-59083 Builds stuck on "is already in progress" forever Change By: Roy Arnon Attachment: failed.PNG Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.278.1566855900249%40Atlassian.JIRA.
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Roy Arnon commented on JENKINS-59083 Re: Builds stuck on "is already in progress" forever I do not get what you mean nothing problematic in the screenshot. This jenkins instance is still stuck forever on this build. I have tried restarting it and it reproduces again after completing one build. Is that not enough of a reproduction? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.261.1566855300411%40Atlassian.JIRA.
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Roy Arnon updated an issue Jenkins / JENKINS-59083 Builds stuck on "is already in progress" forever Change By: Roy Arnon Attachment: Capture2.PNG Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.257.1566855180298%40Atlassian.JIRA.
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Roy Arnon edited a comment on JENKINS-59083 Re: Builds stuck on "is already in progress" forever Hi,I've uploaded a build that is stuck and an image of the state in jenkins. The build I uploaded is build #1913 - I aborted it (the process it was testing was just taking too much time, some misconfiguration probably), but jenkins still does not allow next builds to start - [^stuck-build.tar.gz]I'v also attached a thread dump - [^tdump]After a restart, these "stuck" builds immediately start. The jenkins logs do not seem to contain anything relevant. Regarding durability settings - this job is using the default (PERFORMANCE) but I've seen this issue on jobs that are set to DURABILITY as well. Let me know if you need anything else.!Capture.PNG|thumbnail! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.245.1566850980379%40Atlassian.JIRA.
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Roy Arnon edited a comment on JENKINS-59083 Re: Builds stuck on "is already in progress" forever Hi,I've uploaded a build that is stuck and an image of the state in jenkins. The build I uploaded is build #1913 - I aborted it (the process it was testing was just taking too much time, some misconfiguration probably), but jenkins still does not allow next builds to start - [^stuck-build.tar.gz]I'v also attached a thread dump - [^tdump]After a restart, these "stuck" builds immediately start. The jenkins logs do not seem to contain anything relevant.Let me know if you need anything else. [^stuck-build !Capture . tar.gz] PNG|thumbnail! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.238.1566850680807%40Atlassian.JIRA.
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Roy Arnon commented on JENKINS-59083 Re: Builds stuck on "is already in progress" forever Hi, I've uploaded a build that is stuck and an image of the state in jenkins. The build I uploaded is build #1913 - I aborted it (the process it was testing was just taking too much time, some misconfiguration probably), but jenkins still does not allow next builds to start - stuck-build.tar.gz I'v also attached a thread dump - tdump After a restart, these "stuck" builds immediately start. The jenkins logs do not seem to contain anything relevant. Let me know if you need anything else. stuck-build.tar.gz Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.234.1566850680746%40Atlassian.JIRA.
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Roy Arnon updated an issue Jenkins / JENKINS-59083 Builds stuck on "is already in progress" forever Change By: Roy Arnon Attachment: tdump Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.233.1566850680731%40Atlassian.JIRA.
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Roy Arnon updated an issue Jenkins / JENKINS-59083 Builds stuck on "is already in progress" forever Change By: Roy Arnon Attachment: Capture.PNG Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.229.1566850440596%40Atlassian.JIRA.
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Roy Arnon updated an issue Jenkins / JENKINS-59083 Builds stuck on "is already in progress" forever Change By: Roy Arnon Attachment: stuck-build.tar.gz Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.225.1566850380805%40Atlassian.JIRA.
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Roy Arnon commented on JENKINS-59083 Re: Builds stuck on "is already in progress" forever Hi, I can reproduce the error, I am not near a computer right now so I will have that for you by tomorrow. Yes, in this specific project - and probably all stuck builds - we have disabled concurrent builds. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.10062.1566835380166%40Atlassian.JIRA.
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Roy Arnon updated an issue Jenkins / JENKINS-59083 Builds stuck on "is already in progress" forever Change By: Roy Arnon Attachment: image.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.10024.1566830880237%40Atlassian.JIRA.
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title
Roy Arnon updated an issue
Jenkins / JENKINS-59083
Builds stuck on "is already in progress" forever
Change By:
Roy Arnon
After upgrading our jenkins master and plugins, some of our build jobs - specifically it seemed like most pipeline jobs - were stuck waiting for previous build to complete, even though it already completed.!https://files.slack.com/files-pri/T0255EC3D-FMP3HKY56/image.png! This seems to have been caused by JENKINS-46076.After donwngrading the plugin to version 2.32, all build builds were working correctly. From some testing, it seems that calling{code:java}Jenkins.instance.getItemByFullName(...).getBuildByNumber(..).isLogUpdated(){code}On the previous build (in the sample case build #185) returns true, although the build is completed and the log seems to have been completed.This issue happened immediately after restarting the jenkins instance with any of our pipeline jobs
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.9848.1566824580071%40Atlassian.JIRA.
[JIRA] (JENKINS-46076) Test flake in CpsThreadTest.stop
Title: Message Title Roy Arnon commented on JENKINS-46076 Re: Test flake in CpsThreadTest.stop Jesse Glick done - JENKINS-59083 I have also reproduced this issue on our test instance, if you need any more information please let me know. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184309.1502230337000.9844.1566824520164%40Atlassian.JIRA.
[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever
Title: Message Title Roy Arnon created an issue Jenkins / JENKINS-59083 Builds stuck on "is already in progress" forever Issue Type: Bug Assignee: Unassigned Attachments: plugins.txt Components: workflow-job-plugin Created: 2019-08-26 12:58 Environment: Centos 7.2.1511 (master and slaves) Jenkins 2.176.2 Jenkins master - open-jdk 1.8.0_212 Jenkins slaves - Oracle jdk 1.8.0_60 Jenkins running as docker container (standalone) Attached plugin versions as file Labels: regression Priority: Major Reporter: Roy Arnon After upgrading our jenkins master and plugins, some of our build jobs - specifically it seemed like most pipeline jobs - were stuck waiting for previous build to complete, even though it already completed. This seems to have been caused by JENKINS-46076. After donwngrading the plugin to version 2.32, all build were working correctly. From some testing, it seems that calling Jenkins.instance.getItemByFullName(...).getBuildByNumber(..).isLogUpdated() On the previous build (in the sample case build #185) returns true, although the build is
[JIRA] (JENKINS-46076) Test flake in CpsThreadTest.stop
Title: Message Title Roy Arnon commented on JENKINS-46076 Re: Test flake in CpsThreadTest.stop Hi Jesse Glick, I believe this ticked caused an issue with our jenkins instance. The issue I was seeing was causing builds to be stuck forever in queue - I ran Jenkins.instance.getItemByFullName(...).getBuildByNumber(..).isLogUpdated() On the previous build, and the result was true. I believe this was causing the blockage. A downgrade to workflow-job 2.32 fixed the issue for us. I can gather more information if you like and try to reproduce the issue on our test instance. We are using jenkins 2.176.2. I have attached a list of our plugins as well - plugins.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184309.1502230337000.9104.1566652620164%40Atlassian.JIRA.
[JIRA] (JENKINS-46076) Test flake in CpsThreadTest.stop
Title: Message Title Roy Arnon updated an issue Jenkins / JENKINS-46076 Test flake in CpsThreadTest.stop Change By: Roy Arnon Attachment: plugins.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184309.1502230337000.9099.1566652560258%40Atlassian.JIRA.
[JIRA] (JENKINS-56402) Declarative Pipeline shows SUCCESS even though job FAILED
Title: Message Title Roy Arnon commented on JENKINS-56402 Re: Declarative Pipeline shows SUCCESS even though job FAILED Just wanted to remark that the currentBuild.resultIsBetterOrEqualTo / resultIsWorseOrEqualTo also does not work because of the same issue - assuming they use the same currentBuild.currentResult internally. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55254) Customize mappings from Jenkins Results to Bitbucket State
Title: Message Title Roy Arnon created an issue Jenkins / JENKINS-55254 Customize mappings from Jenkins Results to Bitbucket State Issue Type: Bug Assignee: Roy Arnon Components: bitbucket-branch-source-plugin Created: 2018-12-19 09:16 Environment: Jenkins 2.150.1 LTS bitbucket-branch-source-plugin 2.2.16 Priority: Minor Reporter: Roy Arnon A recent change done in JENKINS-49640 is causing an issue with our workflow. In our builds, we use the NOT_BUILT option to mark builds that we chose not to build, not due to them not being needed, but due to the user not requesting them, erroneous triggers, etc. The change performed in JENKINS-49640 broke this workflow. We suggest adding custom mappings from Jenkins Results to BB build states, configurable in UI. Add Comment
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Roy Arnon edited a comment on JENKINS-50199 Re: Failed pipeline jobs stuck running after incorrect resume [~svanoort] we have also recently encountered this issue, or something similar as in our case the resuming jobs completed with SUCCESS.I commented [ here |https://issues.jenkins-ci.org/browse/JENKINS-33761?focusedCommentId=347675=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-347675] But it seems this issue is more relevant to this ticket.In our case the resuming build was marked as SUCCESS which marked at as success in Bitbucket (with bitbucket-branch-source plugin). The build itself never completed and in fact had a failing test. This allowed one of our developers to merge a failing build into release unfortunately, If there is anything you need from our jenkins instance I am happy to provide it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Roy Arnon edited a comment on JENKINS-50199 Re: Failed pipeline jobs stuck running after incorrect resume [~svanoort] we have also recently encountered this issue , or something similar as in our case the resuming jobs completed with SUCCESS .I commented hereBut it seems this issue is more relevant to this ticket.In our case the resuming build was marked as SUCCESS which marked at as success in Bitbucket (with bitbucket-branch-source plugin). The build itself never completed and in fact had a failing test. This allowed one of our developers to merge a failing build into release unfortunately, If there is anything you need from our jenkins instance I am happy to provide it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Roy Arnon edited a comment on JENKINS-50199 Re: Failed pipeline jobs stuck running after incorrect resume [~svanoort] we have also recently encountered this issue.I commented [ here |https://issues.jenkins-ci.org/browse/JENKINS-33761?focusedCommentId=347675=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-347675] But it seems this issue is more relevant to this ticket.In our case the resuming build was marked as SUCCESS which marked at as success in Bitbucket (with bitbucket-branch-source plugin). The build itself never completed and in fact had a failing test. This allowed one of our developers to merge a failing build into release unfortunately, If there is anything you need from our jenkins instance I am happy to provide it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Roy Arnon commented on JENKINS-50199 Re: Failed pipeline jobs stuck running after incorrect resume Sam Van Oort we have also recently encountered this issue. I commented here But it seems this issue is more relevant to this ticket. In our case the resuming build was marked as SUCCESS which marked at as success in Bitbucket (with bitbucket-branch-source plugin). This allowed one of our developers to merge a failing build into release unfortunately, If there is anything you need from our jenkins instance I am happy to provide it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-33761) Ability to disable Pipeline durability and "resume" build.
Title: Message Title Roy Arnon commented on JENKINS-33761 Re: Ability to disable Pipeline durability and "resume" build. Hello, I am not sure this is related to this issue, but in our pipeline build job we recently added the disableResume step and it does not seem to work correctly: Jenkins 2.89.3 Pipeline 2.5 Pipeline API 2.27 Pipeline Nodes and Processes 2.20 Pipeline Step API 2.16 Scripts Security 1.44 durabilityHint=PERFORMANCE_OPTIMIZED org.jenkinsci.plugins.workflow.job.properties.DisableResumeJobProperty Groovy Sandbox = disabled Creating placeholder flownodes because failed loading originals. Resuming build at Thu Aug 30 12:42:45 UTC 2018 after Jenkins restart [Bitbucket] Notifying pull request build result [Bitbucket] Build result notified [lockable-resources] released lock on [UNIT_TEST_RESOURCE_3] java.io.IOException: Tried to load head FlowNodes for execution Owner[Products.Pipeline/PR-5615/7:Products.Pipeline/PR-5615 #7] but FlowNode was not found in storage for head id:FlowNodeId 1:586 at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.initializeStorage(CpsFlowExecution.java:678) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.onLoad(CpsFlowExecution.java:715) at org.jenkinsci.plugins.workflow.job.WorkflowRun.getExecution(WorkflowRun.java:875) at org.jenkinsci.plugins.workflow.job.WorkflowRun.onLoad(WorkflowRun.java:745) at hudson.model.RunMap.retrieve(RunMap.java:225) at hudson.model.RunMap.retrieve(RunMap.java:57) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:500) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:482) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:380) at hudson.model.RunMap.getById(RunMap.java:205) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.run(WorkflowRun.java:1098) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.get(WorkflowRun.java:1109) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:65) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:57) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$ItemListenerImpl.onLoaded(FlowExecutionList.java:178) at jenkins.model.Jenkins.(Jenkins.java:974) at hudson.model.Hudson.(Hudson.java:86) at hudson.model.Hudson.(Hudson.java:82) at hudson.WebAppMain$3.run(WebAppMain.java:233) Finished: SUCCESS This is an issue for us as the build was marked as SUCCESS in bitbucket, which allowed a user to merge a failing test into our release branch. The job was definitely running with resume disabled, as this was printed at start of job: Resume disabled by user, switching to high-performance, low-durability mode. Any ideas?
[JIRA] (JENKINS-50713) Timestamper URL paths are incorrect in README examples
Title: Message Title Roy Arnon created an issue Jenkins / JENKINS-50713 Timestamper URL paths are incorrect in README examples Issue Type: Bug Assignee: Steven G Brown Components: timestamper-plugin Created: 2018-04-10 10:33 Environment: Timestamper 1.8.9 Priority: Minor Reporter: Roy Arnon In the wiki, you describe the timestamp paths as the following: Examples: /timestamps By default, display the elapsed time in seconds with three places after the decimal point. /timestamps?time=HH:mm:ss Display the system clock time and append the line from the log. /timestamps?elapsed=HH:mm:ss.S Display the elapsed time and append the line from the log. /timestamps?time=HH:mm:ss=HH:mm:ss.S Display both the system clock time and the elapsed time. /timestamps?currentTime=HH:mm:ss Display the current time on the Jenkins master. These paths are incorrect. When sending a request to /timestamps?time=HH:mm:ss for example: < HTTP/1.1 302 Found < Server: nginx/1.10.2 < Date: Tue, 10 Apr 2018 10:31:27 GMT < Transfer-Encoding: chunked < Connection: keep-alive < X-Content-Type-Options: nosniff < Access-Control-Allow-Origin: * < Access-Control-Allow-Methods: GET, POST, PUT, DELETE < Access-Control-Allow-Headers: Authorization < Set-Cookie:
[JIRA] [ssh-slaves-plugin] (JENKINS-22320) High CPU consumption because of SSH communication
Title: Message Title Roy Arnon commented on JENKINS-22320 Re: High CPU consumption because of SSH communication Sorry, attached the image incorrectly: 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] [ssh-slaves-plugin] (JENKINS-22320) High CPU consumption because of SSH communication
Title: Message Title Roy Arnon commented on JENKINS-22320 Re: High CPU consumption because of SSH communication Hi, Using jenkins 1.625.3 and ssh-slave plugin 1.10, it seems this issue occurs intermenitally for us. Lately, it happens at least once a day. Most of the threads are wasting CPU time exactly the same as in the example above. I've attached call tree from yourkit. I can provide more data if required. 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] (JENKINS-18241) Can't run Parallel Test Execution jobs
Roy Arnon created JENKINS-18241 Cant run Parallel Test Execution jobs Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: parallel-test-executor Created: 06/Jun/13 5:24 PM Description: I just created a new job that only contains a Parallel Test Execution. Tried the job with both a matrix job, and a regular maven job. Both fail with this exception: Copying file to FATAL: Failed to copy /var/lib/jenkins/jobs/backstage.ParallelTestExecution/builds/2013-06-06_20-20-25/parameter-files/test-splits/split.1.txt to /home/builder/workspace/backstage.Test.chrome hudson.util.IOException2: Failed to copy /var/lib/jenkins/jobs/backstage.ParallelTestExecution/builds/2013-06-06_20-20-25/parameter-files/test-splits/split.1.txt to /home/builder/workspace/backstage.Test.chrome at hudson.FilePath.copyTo(FilePath.java:1726) at hudson.model.FileParameterValue$FileItemImpl.write(FileParameterValue.java:267) at hudson.FilePath.copyFrom(FilePath.java:830) at hudson.model.FileParameterValue$2.setUp(FileParameterValue.java:136) at hudson.model.Build$BuildExecution.doRun(Build.java:154) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:586) at hudson.model.Run.execute(Run.java:1576) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:241) Caused by: java.io.FileNotFoundException: /home/builder/workspace/backstage.Test.chrome (Is a directory) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.init(FileOutputStream.java:179) at java.io.FileOutputStream.init(FileOutputStream.java:131) at hudson.FilePath.write(FilePath.java:1622) at hudson.FilePath.copyTo(FilePath.java:1719) ... 9 more Project: Jenkins Labels: bug Priority: Major Reporter: Roy Arnon This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
