[JIRA] [workflow-plugin] (JENKINS-33629) `checkout scm` surprisingly fails when multibranch plugin is not installed
Title: Message Title
c089 updated an issue
Jenkins / JENKINS-33629
`checkout scm` surprisingly fails when multibranch plugin is not installed
Change By:
c089
Since JENKINS-31386 we can use `checkout scm` to get SCM sources using the values configured for the "Pipeline script from SCM" job. However, this only works if the multibranch plugin is installed, otherwise it fails (see stack trace below). I only realised that after finding the mentioned issue and looking at the diff of the commit.{ { code} groovy.lang.MissingPropertyException: No such property: scm for class: groovy.lang.Bindingat groovy.lang.Binding.getVariable(Binding.java:62)at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:185)at org.kohsuke.groovy.sandbox.impl.Checker$4.call(Checker.java:241)at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:238)at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:221)at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:221)at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.getProperty(SandboxInvoker.java:23)at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:17)at WorkflowScript.run(WorkflowScript:16)at ___cps.transform___(Native Method)at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.get(PropertyishBlock.java:62)at com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30)at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.fixName(PropertyishBlock.java:54)at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method.java:497)at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21)at com.cloudbees.groovy.cps.Next.step(Next.java:58)at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154)at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:19)at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:33)at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:30)at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:106)at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:30)at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:164)at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:277)at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$000(CpsThreadGroup.java:77)at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:186)at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:184)at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:47)at java.util.concurrent.FutureTask.r
[JIRA] [workflow-plugin] (JENKINS-33629) `checkout scm` surprisingly fails when multibranch plugin is not installed
Title: Message Title
c089 updated an issue
Jenkins / JENKINS-33629
`checkout scm` surprisingly fails when multibranch plugin is not installed
Change By:
c089
Since JENKINS-31386 we can use `checkout scm` to get SCM sources using the values configured for the "Pipeline script from SCM" job. However, this only works if the multibranch plugin is installed, otherwise it fails (see stack trace below). I only realised that after finding the mentioned issue and looking at the diff of the commit.{{ monospace}} groovy.lang.MissingPropertyException: No such property: scm for class: groovy.lang.Bindingat groovy.lang.Binding.getVariable(Binding.java:62)at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:185)at org.kohsuke.groovy.sandbox.impl.Checker$4.call(Checker.java:241)at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:238)at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:221)at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:221)at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.getProperty(SandboxInvoker.java:23)at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:17)at WorkflowScript.run(WorkflowScript:16)at ___cps.transform___(Native Method)at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.get(PropertyishBlock.java:62)at com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30)at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.fixName(PropertyishBlock.java:54)at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method.java:497)at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21)at com.cloudbees.groovy.cps.Next.step(Next.java:58)at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154)at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:19)at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:33)at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:30)at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:106)at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:30)at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:164)at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:277)at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$000(CpsThreadGroup.java:77)at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:186)at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:184)at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:47)at java.util.concurrent.FutureT
[JIRA] [workflow-plugin] (JENKINS-33629) `checkout scm` surprisingly fails when multibranch plugin is not installed
Title: Message Title c089 created an issue Jenkins / JENKINS-33629 `checkout scm` surprisingly fails when multibranch plugin is not installed Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 2016/Mar/17 4:35 PM Labels: workflow Priority: Minor Reporter: c089 Since JENKINS-31386 we can use `checkout scm` to get SCM sources using the values configured for the "Pipeline script from SCM" job. However, this only works if the multibranch plugin is installed, otherwise it fails (see stack trace below). I only realised that after finding the mentioned issue and looking at the diff of the commit. monospace groovy.lang.MissingPropertyException: No such property: scm for class: groovy.lang.Binding at groovy.lang.Binding.getVariable(Binding.java:62) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:185) at org.kohsuke.groovy.sandbox.impl.Checker$4.call(Checker.java:241) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:238) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:221) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:221) at com.cloudbees.groovy
[JIRA] [build-alias-setter] (JENKINS-21706) Terminology of lastUnsuccessfulBuild is unclear
cfx updated JENKINS-21706 Terminology of lastUnsuccessfulBuild is unclear Change By: cfx (07/Feb/14 8:13 AM) Summary: Terminology of lastUnsuccessfulBuilds lastUnsuccessfulBuild is unclear 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.
[JIRA] [build-alias-setter] (JENKINS-21706) Terminology of lastUnsuccessfulBuilds unclear
cfx updated JENKINS-21706 Terminology of lastUnsuccessfulBuilds unclear Change By: cfx (07/Feb/14 8:12 AM) Description: How can the symlinks to successful and unsuccessful builds point to the same build?lrwxrwxrwx 1 jenkins jenkins4 Feb 5 14 10 : 05 47 lastFailedBuild -> 1234 1014 lrwxrwxrwx 1 jenkins jenkins 4 Feb 6 17 2 Oct 7 14 : 32 56 lastStableBuild -> 1244 -1 lrwxrwxrwx 1 jenkins jenkins4 Feb 6 17 18 : 32 42 lastSuccessfulBuild -> 1244 1022 lrwxrwxrwx 1 jenkins jenkins 2 May 7 2013 4 Feb 6 18:42 lastUnstableBuild -> -1 1022 lrwxrwxrwx 1 jenkins jenkins4 Feb 5 14 6 18 : 05 42 lastUnsuccessfulBuild -> 1234 1022 (Edit: ls was on wrong job dir) 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.
[JIRA] [build-alias-setter] (JENKINS-21706) Terminology of lastUnsuccessfulBuilds unclear
cfx created JENKINS-21706 Terminology of lastUnsuccessfulBuilds unclear Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: build-alias-setter Created: 07/Feb/14 8:09 AM Description: How can the symlinks to successful and unsuccessful builds point to the same build? lrwxrwxrwx 1 jenkins jenkins4 Feb 5 14:05 lastFailedBuild -> 1234 lrwxrwxrwx 1 jenkins jenkins4 Feb 6 17:32 lastStableBuild -> 1244 lrwxrwxrwx 1 jenkins jenkins4 Feb 6 17:32 lastSuccessfulBuild -> 1244 lrwxrwxrwx 1 jenkins jenkins2 May 7 2013 lastUnstableBuild -> -1 lrwxrwxrwx 1 jenkins jenkins4 Feb 5 14:05 lastUnsuccessfulBuild -> 1234 Project: Jenkins Priority: Minor Reporter: cfx 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.
[JIRA] (JENKINS-15875) Cannot change "Usage" setting of master jenkins
c089 created JENKINS-15875 Cannot change "Usage" setting of master jenkins Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: master-slave Created: 20/Nov/12 8:08 AM Description: Steps to reproduce: go to "manage nodes" screen click configure icon next to master node set usage setting from "utilize as much as possible" to "leave this machine for tied jobs only" click save go back to the configure page Expected: Usage setting was set to "leave for tied jobs" Actual: Usage setting was set back to "utilize as much as possible" Project: Jenkins Priority: Major Reporter: c089 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
[JIRA] (JENKINS-15864) multi-configuration project ignores slave setting
c089 commented on JENKINS-15864 multi-configuration project ignores slave setting After I used "mark this node as temporarilly offline" on the windows slaves, the job successfully built on the master, but as soon as one was up, it's back on the windows node... 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
[JIRA] (JENKINS-15864) multi-configuration project ignores slave setting
c089 commented on JENKINS-15864 multi-configuration project ignores slave setting It even uses the same slave all the time... 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
[JIRA] (JENKINS-15864) multi-configuration project ignores slave setting
c089 created JENKINS-15864 multi-configuration project ignores slave setting Issue Type: Bug Affects Versions: current Assignee: rsandell Components: master-slave, multi-slave-config Created: 19/Nov/12 1:50 PM Description: After upgrading from 1.488 to 1.491 (could not test the others because of a bug with mercurial) one of our builds started to fail. It is a multi-config build with two axes, one of which is a workaround to get the "restrict where the project can be built" functionality which is not available for multi-config builds. It is a "Slaves" axis with only the Jenkins master node selected. However, the project always seems to be built on a windows node which doesn't even have mercurial installed. Project: Jenkins Priority: Major Reporter: c089 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
[JIRA] (JENKINS-15721) Cannot add browsers due to template include exception
c089 commented on JENKINS-15721 Cannot add browsers due to template include exception Looking at the git log it seems this was fixed about two months ago, but there is no new release available. 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
[JIRA] (JENKINS-15721) Cannot add browsers due to template include exception
c089 created JENKINS-15721 Cannot add browsers due to template include exception Issue Type: Bug Assignee: Richard Lavoie Components: selenium Created: 05/Nov/12 3:00 PM Description: When trying to add a browser in the grid config I get: Caused by: org.apache.commons.jelly.JellyTagException: file:/var/lib/jenkins/plugins/selenium/WEB-INF/classes/hudson/plugins/selenium/configuration/browser/webdriver/ChromeBrowser/config.jelly:2:104: No page found '../../AbstractSeleniumBrowser/config.jelly' for class hudson.plugins.selenium.configuration.global.SeleniumGlobalConfiguration Problem seems to be that is uses SeleniumGlobalConfiguration as the working directory, from which this relative path is indeed wrong. Project: Jenkins Priority: Major Reporter: c089 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
[JIRA] (JENKINS-14103) Grails 2.0.4 not listed in installer doropdown
c089 created JENKINS-14103 Grails 2.0.4 not listed in installer doropdown Issue Type: Bug Assignee: jeffg2one Components: grails Created: 14/Jun/12 12:52 PM Description: Grails 2.0.4 has been released a while ago, but the install from mirrors dropdown still does not list the new version. Project: Jenkins Priority: Major Reporter: c089 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
