[JIRA] (JENKINS-42994) In some situations, the 're-run' button will not trigger a build and not give any feedback of failure.
Title: Message Title Ben Walding commented on JENKINS-42994 Re: In some situations, the 're-run' button will not trigger a build and not give any feedback of failure. My case is for the "Run" button rather than the "Re-run" Also - that Jenkinsfile trace is referring to an internal CloudBees script that it shouldn't have access to (not a security risk, but I think the error is a valid error). I have had issues in the past with Re-run - but that was before parameters were supported - and the lack of parameters in the re-run was the root cause of the problem. 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-42994) In some situations, the 're-run' button will not trigger a build and not give any feedback of failure.
Title: Message Title James Dumay commented on JENKINS-42994 Re: In some situations, the 're-run' button will not trigger a build and not give any feedback of failure. Hurrah! 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-42994) In some situations, the 're-run' button will not trigger a build and not give any feedback of failure.
Title: Message Title Michael Neale reopened an issue I have been able to see this happen. clicking in steady succession on a freestyle job (not the re-run per se, but the run button on activity). Ben Walding has seen similar in specific environments (although in that case the run seems to be triggered, just not reported on the activity list). Jenkins / JENKINS-42994 In some situations, the 're-run' button will not trigger a build and not give any feedback of failure. Change By: Michael Neale Resolution: Cannot Reproduce Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42994) In some situations, the 're-run' button will not trigger a build and not give any feedback of failure.
Title: Message Title James Dumay resolved as Cannot Reproduce Jenkins / JENKINS-42994 In some situations, the 're-run' button will not trigger a build and not give any feedback of failure. Change By: James Dumay Status: Open Resolved Resolution: Cannot Reproduce 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-42994) In some situations, the 're-run' button will not trigger a build and not give any feedback of failure.
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42994 In some situations, the 're-run' button will not trigger a build and not give any feedback of failure. Change By: James Dumay Sprint: Blue Ocean 1. 1 0-rc2 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-42994) In some situations, the 're-run' button will not trigger a build and not give any feedback of failure.
Title: Message Title Michael Neale commented on JENKINS-42994 Re: In some situations, the 're-run' button will not trigger a build and not give any feedback of failure. I think this can stay out of current sprint, needs more time etc. 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-42994) In some situations, the 're-run' button will not trigger a build and not give any feedback of failure.
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-42994 In some situations, the 're-run' button will not trigger a build and not give any feedback of failure. Change By: Michael Neale Sprint: Blue Ocean 1. 0-rc2 1 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-42994) In some situations, the 're-run' button will not trigger a build and not give any feedback of failure.
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42994 In some situations, the 're-run' button will not trigger a build and not give any feedback of failure. Change By: James Dumay Sprint: Blue Ocean 1.0-rc2 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-42994) In some situations, the 're-run' button will not trigger a build and not give any feedback of failure.
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-42994 In some situations, the 're-run' button will not trigger a build and not give any feedback of failure. Change By: Michael Neale Labels: blueocean technical-debt 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-42994) In some situations, the 're-run' button will not trigger a build and not give any feedback of failure.
Title: Message Title James Dumay assigned an issue to James Dumay Jenkins / JENKINS-42994 In some situations, the 're-run' button will not trigger a build and not give any feedback of failure. Change By: James Dumay Assignee: James Dumay 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-42994) In some situations, the 're-run' button will not trigger a build and not give any feedback of failure.
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-42994
In some situations, the 're-run' button will not trigger a build and not give any feedback of failure.
Change By:
James Dumay
In some situations, the 're-run' button will not trigger a build and not give any feedback. One example:*Classic UI* {code} Job re-run and failed: {code} Started by user [admin|http://ec2-52-200-141-179.compute-1.amazonaws.com:8080/user/admin]17:38:37 Connecting to [https://api.github.com|https://api.github.com/] using admin/** (Github Access Token)Obtained Jenkinsfile from 77d10641d025cf0169f61cd6e769fe72c36abf40Could not update commit status, please check if your scan credentials belong to a member of the organization or a collaborator of the repository and repo:status scope is selectedorg.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:WorkflowScript: 1: unable to resolve class com.cloudbees.ops.Builder @ line 1, column 1. import com.cloudbees.ops.Builder; ^1 error at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310) at org.codehaus.groovy.control.CompilationUnit.applyToSourceUnits(CompilationUnit.java:946) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:593) at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:542) at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268) at groovy.lang.GroovyShell.parseClass(GroovyShell.java:688) at groovy.lang.GroovyShell.parse(GroovyShell.java:700) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:67) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:430) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:393) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:238) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404)Finished: FAILURE{code}*In the Blue Ocean UI*No feedback on re-run buttonJob not retriggeringIncluded are two screenshots with the inert buttons highlighted.
Add Comment
[JIRA] (JENKINS-42994) In some situations, the 're-run' button will not trigger a build and not give any feedback of failure.
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-42994
In some situations, the 're-run' button will not trigger a build and not give any feedback of failure.
Change By:
James Dumay
In some situations, the 're-run' button will not trigger a build and not give any feedback. One example:*Classic UI* {code} Job re-run and failed:Started by user [admin|http://ec2-52-200-141-179.compute-1.amazonaws.com:8080/user/admin]17:38:37 Connecting to [https://api.github.com|https://api.github.com/] using admin/** (Github Access Token)Obtained Jenkinsfile from 77d10641d025cf0169f61cd6e769fe72c36abf40Could not update commit status, please check if your scan credentials belong to a member of the organization or a collaborator of the repository and repo:status scope is selected {code} org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:WorkflowScript: 1: unable to resolve class com.cloudbees.ops.Builder @ line 1, column 1. import com.cloudbees.ops.Builder; ^1 error at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310) at org.codehaus.groovy.control.CompilationUnit.applyToSourceUnits(CompilationUnit.java:946) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:593) at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:542) at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268) at groovy.lang.GroovyShell.parseClass(GroovyShell.java:688) at groovy.lang.GroovyShell.parse(GroovyShell.java:700) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:67) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:430) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:393) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:238) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404)Finished: FAILURE{code}*In the Blue Ocean UI*No feedback on re-run buttonJob not retriggeringIncluded are two screenshots with the inert buttons highlighted.
Add Comment
[JIRA] (JENKINS-42994) In some situations, the 're-run' button will not trigger a build and not give any feedback of failure.
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-42994
In some situations, the 're-run' button will not trigger a build and not give any feedback of failure.
Change By:
James Dumay
In some situations, the 're-run' button will not trigger a build and not give any feedback. One example:*Classic UI*Job re-run and failed:Started by user [admin|http://ec2-52-200-141-179.compute-1.amazonaws.com:8080/user/admin]17:38:37 Connecting to [https://api.github.com|https://api.github.com/] using admin/** (Github Access Token)Obtained Jenkinsfile from 77d10641d025cf0169f61cd6e769fe72c36abf40Could not update commit status, please check if your scan credentials belong to a member of the organization or a collaborator of the repository and repo:status scope is selected {code} org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:WorkflowScript: 1: unable to resolve class com.cloudbees.ops.Builder @ line 1, column 1. import com.cloudbees.ops.Builder; ^1 error at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310) at org.codehaus.groovy.control.CompilationUnit.applyToSourceUnits(CompilationUnit.java:946) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:593) at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:542) at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268) at groovy.lang.GroovyShell.parseClass(GroovyShell.java:688) at groovy.lang.GroovyShell.parse(GroovyShell.java:700) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:67) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:430) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:393) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:238) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404)Finished: FAILURE {code} *In the Blue Ocean UI*No feedback on re-run buttonJob not retriggeringIncluded are two screenshots with the inert buttons highlighted.
Add Comment
[JIRA] (JENKINS-42994) In some situations, the 're-run' button will not trigger a build and not give any feedback of failure.
Title: Message Title Michael Neale commented on JENKINS-42994 Re: In some situations, the 're-run' button will not trigger a build and not give any feedback of failure. Not sure how to reproduce this, only see the description of what happened 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-42994) In some situations, the 're-run' button will not trigger a build and not give any feedback of failure.
Title: Message Title John Hill updated an issue Jenkins / JENKINS-42994 In some situations, the 're-run' button will not trigger a build and not give any feedback of failure. Change By: John Hill Summary: Re In some situations, the 're -run pipeline ' button is inert if will not trigger a large number build and not give any feedback of jobs are being retriggered failure. 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.
