[JIRA] (JENKINS-60913) Remove network discovery services

2020-02-10 Thread allan.le...@youview.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan Lewis updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60913  
 
 
  Remove network discovery services   
 

  
 
 
 
 

 
Change By: 
 Allan Lewis  
 

  
 
 
 
 

 
 Dating back many years, Jenkins has supported two network discovery services (UDP multicast/broadcast and DNS multicast). When this was first implemented this may have been a reasonable way to provide useful lookup services. With modern Jenkins capabilities, networks, and security considerations, this is no longer a good mechanism. There are now other ways to accomplish the real needs and concerns with doing it this way.With [Jenkins Security Advisory 2020-01-29| [ https://jenkins.io/security/advisory/2020-01-29/] |https://jenkins.io/security/advisory/2020-01-29/]  these services were disabled by default because of SECURITY-1641 / CVE-2020-2100.These should just be removed.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this

[JIRA] (JENKINS-60836) "No such property: JENKINS_URL" on cron-triggered job, resolved by manual trigger

2020-01-22 Thread allan.le...@youview.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan Lewis created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60836  
 
 
  "No such property: JENKINS_URL" on cron-triggered job, resolved by manual trigger   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 consoleText, plugins.txt  
 
 
Components: 
 core, pipeline  
 
 
Created: 
 2020-01-22 11:34  
 
 
Environment: 
 Jenkins 2.176.2  See attached plugins.txt  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Allan Lewis  
 

  
 
 
 
 

 
 I have a multi-branch pipeline with the following as the first line, outside of pipeline: 

 

JENKINS_HOST = JENKINS_URL.toURL().host.tokenize('.')[0]
 

 This value is used inside the pipeline. The pipeline generally works but, apparently at random, builds will fail with the following exception: 

 
groovy.lang.MissingPropertyException: No such property: JENKINS_URL for class: groovy.lang.Binding
 

 See consoleText for a redacted console log including the stack trace. This has only been observed on cron-triggered builds: manually building the job, or rebuilding a failed job, works fine. The pipeline defines

[JIRA] (JENKINS-24698) ShowParametersBuildAction doesn't have @ExportedBean so cannot write hudson.model.Actionabl

2019-12-12 Thread allan.le...@youview.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan Lewis updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-24698  
 
 
  ShowParametersBuildAction doesn't have @ExportedBean so cannot write hudson.model.Actionabl   
 

  
 
 
 
 

 
Change By: 
 Allan Lewis  
 

  
 
 
 
 

 
 These exceptions are being written to the log file at regular intervalls.According to JENKINS-24458 it might have to do with some REST API call done by the plugin. {noformat} WARNING: nullorg.kohsuke.stapler.export.NotExportableException: class jenkins.plugins.show_build_parameters.ShowParametersBuildAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actionsat org.kohsuke.stapler.export.Model.(Model.java:73)at org.kohsuke.stapler.export.ModelBuilder.get(ModelBuilder.java:51)at org.kohsuke.stapler.export.Property.writeValue(Property.java:231)at org.kohsuke.stapler.export.Property.writeValue(Property.java:187)at org.kohsuke.stapler.export.Property.writeValue(Property.java:139)at org.kohsuke.stapler.export.Property.writeTo(Property.java:116)at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:190)at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:185)at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:185)at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:185)at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:185)at org.kohsuke.stapler.export.Property.writeValue(Property.java:241)at org.kohsuke.stapler.export.Property.writeValue(Property.java:187)at org.kohsuke.stapler.export.Property.writeValue(Property.java:139)at org.kohsuke.stapler.export.Property.writeTo(Property.java:116)at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:190)at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:185)at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:185)at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:185)at org.kohsuke.stapler.export.Property.writeValue(Property.java:241)at org.kohsuke.stapler.export.Property.writeValue(Property.java:187)at org.kohsuke.stapler.export.Property.writeValue(Property.java:139)at org.kohsuke.stapler.export.Property.writeTo(Property.java:116)at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:190)at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:185)at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:185)at org.kohsuke.stapler.export.Model.writeTo(Model.java:157)at org.kohsuke.stapler.ResponseImpl.serveExposedBean(ResponseImpl.java:267)at hudson.model.Api.doJson(Api.java:205)at sun.reflect.GeneratedMethodAccessor353.invoke(Unknown Source)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method.java:606)at

[JIRA] (JENKINS-60459) Pipeline parameters not properly updated in multibranch job config

2019-12-12 Thread allan.le...@youview.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan Lewis commented on  JENKINS-60459  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline parameters not properly updated in multibranch job config   
 

  
 
 
 
 

 
 I just noticed that there are many hudson.model.ParametersDefinitionProperty elements in config.xml! So perhaps they're being appended instead of replaced? The excerpt in the description is from the first one, which I guess gets read in favour of the later ones.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.203537.1576150173000.6294.1576150800231%40Atlassian.JIRA.

[JIRA] (JENKINS-60459) Pipeline parameters not properly updated in multibranch job config

2019-12-12 Thread allan.le...@youview.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan Lewis commented on  JENKINS-60459  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline parameters not properly updated in multibranch job config   
 

  
 
 
 
 

 
 I'm not sure which plugin is responsible for this logic - apologies if I picked the wrong one!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.203537.1576150173000.6292.1576150380611%40Atlassian.JIRA.

[JIRA] (JENKINS-60459) Pipeline parameters not properly updated in multibranch job config

2019-12-12 Thread allan.le...@youview.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan Lewis created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60459  
 
 
  Pipeline parameters not properly updated in multibranch job config   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Andrew Bayer  
 
 
Attachments: 
 plugins.txt  
 
 
Components: 
 pipeline-model-definition-plugin  
 
 
Created: 
 2019-12-12 11:29  
 
 
Environment: 
 Jenkins 2.176.2  Plugins: see attached plugins.txt  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Allan Lewis  
 

  
 
 
 
 

 
 I have a multi-branch pipeline where I've replaced a boolean parameter with a choice parameter but the "build with parameters" page shows the old boolean parameter; this is after I've done a dummy run to pick up the change. The log reports that it read the pipeline from the latest commit on that branch (master) which has the parameter change. In branches/master/config.xml, I see that the new parameter is listed in the parameters element, but the definition in parameterDefinitions is the old one! Here's an excerpt of that file - the old parameter is named REBOOT_FIRST and the new one is REBOOT_WHEN: 


branches/master/config.xml

 

"workflow-job@2.33">
  
...
"pipeline-model-definition@1.3.9">
...
  
REBOOT_WHEN
...
  
...
  
...
  

  

  REBOOT_FIRST
  ...
  true

[JIRA] (JENKINS-41929) Offer "Build with Parameters" on first build when declarative Jenkinsfile found

2019-12-10 Thread allan.le...@youview.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan Lewis commented on  JENKINS-41929  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Offer "Build with Parameters" on first build when declarative Jenkinsfile found   
 

  
 
 
 
 

 
 Thanks, Michael Brunner - I've considered doing something similar, except maybe making it SCM-triggered since my pipeline is designed to only be manually triggered.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.178785.1486740246000.4234.1575999842285%40Atlassian.JIRA.

[JIRA] (JENKINS-45962) GIT_BRANCH variable is not populated in jenkins pipeline

2019-12-05 Thread allan.le...@youview.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan Lewis updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-45962  
 
 
  GIT_BRANCH variable is not populated in jenkins pipeline   
 

  
 
 
 
 

 
Change By: 
 Allan Lewis  
 

  
 
 
 
 

 
 With Jenkins file below, it shows error that {{GIT_BRANCH}} is not recognized{noformat}stages  \ {   stage('checkout')  \ {       steps  \ {            git credentialsId: 'jenkins',                 url: 'g...@git.xxx.com:jianjing/jenkinspipeline.git',                branch: "test"         }    }    stage('test')  \ {        steps  \ {            sh "echo $\{GIT_BRANCH}"        }    }{noformat}{noformat} groovy.lang.MissingPropertyException: No such property: GIT_BRANCH for class: groovy.lang.Binding at groovy.lang.Binding.getVariable(Binding.java:63) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:232) at org.kohsuke.groovy.sandbox.impl.Checker$5.call(Checker.java:255) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:259) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:235) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:235) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:235) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:235) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.getProperty(SandboxInvoker.java:28) at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:20) at WorkflowScript.run(WorkflowScript:19) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.delegateAndExecute(jar:file:/data/program/jenkins/plugins/pipeline-model-definition/WEB-INF/lib/pipeline-model-definition.jar!/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy:172) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.executeSingleStage(jar:file:/data/program/jenkins/plugins/pipeline-model-definition/WEB-INF/lib/pipeline-model-definition.jar!/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy:438) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.catchRequiredContextForNode(jar:file:/data/program/jenkins/plugins/pipeline-model-definition/WEB-INF/lib/pipeline-model-definition.jar!/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy:188) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.catchRequiredContextForNode(jar:file:/data/program/jenkins/plugins/pipeline-model-definition/WEB-INF/lib/pipeline-model-definition.jar!/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy:186) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.executeSingleStage(jar:file:/data/program/jenkins/plugins/pipeline-model-definition/WEB-INF/lib/pipeline-model-definition.jar!/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy:437) at

[JIRA] (JENKINS-45962) GIT_BRANCH variable is not populated in jenkins pipeline

2019-12-05 Thread allan.le...@youview.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan Lewis updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-45962  
 
 
  GIT_BRANCH variable is not populated in jenkins pipeline   
 

  
 
 
 
 

 
Change By: 
 Allan Lewis  
 

  
 
 
 
 

 
 With Jenkins file below, it shows error that  {{  GIT_BRANCH }}  is not recognized {noformat} stages \{   stage('checkout') \{       steps \{            git credentialsId: 'jenkins',                 url: 'g...@git.xxx.com:jianjing/jenkinspipeline.git',                branch: "test"         }    }    stage('test') \{        steps \{            sh "echo $\{GIT_BRANCH}"        }    } {noformat}  {noformat}  groovy.lang.MissingPropertyException: No such property: GIT_BRANCH for class: groovy.lang.Binding at groovy.lang.Binding.getVariable(Binding.java:63) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:232) at org.kohsuke.groovy.sandbox.impl.Checker$5.call(Checker.java:255) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:259) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:235) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:235) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:235) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:235) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.getProperty(SandboxInvoker.java:28) at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:20) at WorkflowScript.run(WorkflowScript:19) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.delegateAndExecute(jar:file:/data/program/jenkins/plugins/pipeline-model-definition/WEB-INF/lib/pipeline-model-definition.jar!/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy:172) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.executeSingleStage(jar:file:/data/program/jenkins/plugins/pipeline-model-definition/WEB-INF/lib/pipeline-model-definition.jar!/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy:438) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.catchRequiredContextForNode(jar:file:/data/program/jenkins/plugins/pipeline-model-definition/WEB-INF/lib/pipeline-model-definition.jar!/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy:188) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.catchRequiredContextForNode(jar:file:/data/program/jenkins/plugins/pipeline-model-definition/WEB-INF/lib/pipeline-model-definition.jar!/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy:186) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.executeSingleStage(jar:file:/data/program/jenkins/plugins/pipeline-model-definition/WEB-INF/lib/pipeline-model-definition.jar!/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy:437) at

[JIRA] (JENKINS-60315) "Indication" drop-down raises exception in Javascript console

2019-11-28 Thread allan.le...@youview.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan Lewis created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60315  
 
 
  "Indication" drop-down raises exception in _javascript_ console   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Tomas Westling  
 
 
Components: 
 build-failure-analyzer-plugin  
 
 
Created: 
 2019-11-28 10:46  
 
 
Environment: 
 Jenkins v2.176.2  Build Failure Analyzer Plugin 1.24.1  Fedora 30  Firefox 70.0.1 / Google Chrome 78.0.3904.108  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Allan Lewis  
 

  
 
 
 
 

 
 On a build status page where a failure has been identified, each "indication" has a drop-down arrow next to it; this appears when hovering over the text. Clicking this should presumably present some options, but instead it throws a _javascript_ exception that can be seen in the console: 


Firefox 70

 
SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data prototype.js:747:17
 

 


Chrome 78

 
hudson-behavior.js:2995 Uncaught SyntaxError: Unexpected token < in JSON at position 0
at JSON.parse ()
at

[JIRA] (JENKINS-26567) Tests result analyzer plugin not working

2019-11-20 Thread allan.le...@youview.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan Lewis updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-26567  
 
 
  Tests result analyzer plugin not working   
 

  
 
 
 
 

 
Change By: 
 Allan Lewis  
 

  
 
 
 
 

 
 When clicking on "Test results analyzer" for the build, the exception below is produced by jenkins, and only the different buttons for generating graphs and report is shown, with the header of the table as well.See attachement on how the jenkins configuration is done when publishing the junit reports ←[0m←[33mjan {noformat}jan  23, 2015 11:12:34 AM hudson.ExpressionFactory2$JexlExpression evaluateWARNING: Caught exception evaluating: it.jsonLoadData in /view/ny-nettbutikk/job/selenium-aapnesider/test_results_analyzer/. Reason: java.lang.reflect.InvocationTargetExceptionjava.lang.reflect.InvocationTargetExceptionat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method.java:606)at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125)at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314)at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185)at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75)at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74)at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)at

[JIRA] (JENKINS-59125) test

2019-11-20 Thread allan.le...@youview.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan Lewis updated  JENKINS-59125  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59125  
 
 
  test   
 

  
 
 
 
 

 
Change By: 
 Allan Lewis  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Assignee: 
 Varun Menon Sai Test  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.201557.1567006519000.4506.1574265120860%40Atlassian.JIRA.

[JIRA] (JENKINS-59125) test

2019-11-20 Thread allan.le...@youview.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan Lewis updated  JENKINS-59125  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59125  
 
 
  test   
 

  
 
 
 
 

 
Change By: 
 Allan Lewis  
 
 
Status: 
 Fixed but Unreleased Closed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.201557.1567006519000.4508.1574265120885%40Atlassian.JIRA.

[JIRA] (JENKINS-59436) Include body with GET requests

2019-09-18 Thread allan.le...@youview.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan Lewis created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59436  
 
 
  Include body with GET requests   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Janario Oliveira  
 
 
Components: 
 http-request-plugin  
 
 
Created: 
 2019-09-18 17:03  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Allan Lewis  
 

  
 
 
 
 

 
 If a request body is set for a GET request, it appears to be ignored. This situation isn't common, but it's used by Elasticsearch for queries so the plugin should support it.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira

[JIRA] (JENKINS-53372) Update Groovy to v2.5.x

2019-05-02 Thread allan.le...@youview.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan Lewis assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53372  
 
 
  Update Groovy to v2.5.x   
 

  
 
 
 
 

 
Change By: 
 Allan Lewis  
 
 
Assignee: 
 Allan Lewis  
 

  
 
 
 
 

 
 
 

 
 
 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-57315) Github folder should allow one reference repo per child repository

2019-05-02 Thread allan.le...@youview.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan Lewis created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57315  
 
 
  Github folder should allow one reference repo per child repository   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 github-branch-source-plugin  
 
 
Created: 
 2019-05-02 16:36  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Allan Lewis  
 

  
 
 
 
 

 
 A Github folder can be configured to use a reference repo. However, this doesn't make sense for a Github org containing multiple repos: surely there should be one reference repo per Github repo? I understand it's possible to have one reference repo for multiple "real" repos, but is that a good idea?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
 

[JIRA] (JENKINS-56247) notifyBitbucket ignores projectKey

2019-02-22 Thread allan.le...@youview.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan Lewis created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56247  
 
 
  notifyBitbucket ignores projectKey   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 stashnotifier-plugin  
 
 
Created: 
 2019-02-22 13:13  
 
 
Environment: 
 Jenkins 2.138.1  Stash Notifier 1.14  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Allan Lewis  
 

  
 
 
 
 

 
 If I set projectKey to some string, it seems to be ignored. I've tried notifyBitbucket(projectKey: 'foobar') and setting all the options including that one, but it always uses the default generated key.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
 

[JIRA] (JENKINS-39347) Notify Stash plugin problems after update

2019-02-22 Thread allan.le...@youview.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan Lewis updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39347  
 
 
  Notify Stash plugin problems after update   
 

  
 
 
 
 

 
Change By: 
 Allan Lewis  
 

  
 
 
 
 

 
 After updating Jenkins stash notifier plugin stopped notifying Bitbucket server. In each build I keep getting: {noformat} 12:10:00 Unable to expand commit SHA value with org.jenkinsci.plugins.workflow.job.WorkflowRun12:10:00 Unable to expand build key macro with run of type org.jenkinsci.plugins.workflow.job.WorkflowRun {noformat} pipeline code which is executed when this happens: {code} def notify(sha1,status) {step([$class: 'StashNotifier', buildState: status, commitSha1: sha1, credentialsId: 'SOME_CREDENTIALS', disableInprogressNotification: false, ignoreUnverifiedSSLPeer: false, includeBuildNumberInKey: false, prependParentProjectKey: false, projectKey: 'PROJECT',repositoryKey: 'repo', stashServerBaseUrl: 'https://bitbucket.someCompany.com']) } {code} I tried adding :  {{   -Dhudson.model.ParametersAction.keepUndefinedParameters=true }}  , rebooted the  jenkins  Jenkins  master machine and still everything is the same!Am I missing something? What's going on?  
 

  
 
 
 
 

 
 
 

 
 
 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

[JIRA] (JENKINS-54078) [JEP-210] Exception: Object was recently deallocated when using Git + timeout(activity: true)

2019-02-22 Thread allan.le...@youview.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan Lewis updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54078  
 
 
  [JEP-210] Exception: Object was recently deallocated when using Git + timeout(activity: true)   
 

  
 
 
 
 

 
Change By: 
 Allan Lewis  
 

  
 
 
 
 

 
 When upgrading to Pipeline: Job 2.26 I get errors when combining some wrappers and steps:   {code:java}timeout{timestamps{checkout [$class: 'GitSCM' ...]}}{code}Jenkins version: 2.138.2Pipeline: Groovy 2.58Timestamper 1.8.10Git plugin 3.9.1   {noformat}Released at Mon Oct 15 13:44:45 MSK 2018 at hudson.remoting.ExportTable$Entry.release(ExportTable.java:163) at hudson.remoting.ExportTable$ExportList.release(ExportTable.java:300) at hudson.remoting.UserRequest.releaseExports(UserRequest.java:299) at hudson.remoting.UserRequest.releaseExports(UserRequest.java:295) at hudson.remoting.Channel.call(Channel.java:970) at hudson.FilePath.act(FilePath.java:1071) at hudson.FilePath.act(FilePath.java:1060) at org.jenkinsci.plugins.gitclient.Git.getClient(Git.java:137) at hudson.plugins.git.GitSCM.createClient(GitSCM.java:795) at hudson.plugins.git.GitSCM.createClient(GitSCM.java:786) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1154) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)Caused: java.lang.Exception: Object was recently deallocated#17 (ref.0) : object=null type=org.jenkinsci.plugins.workflow.steps.TimeoutStepExecution$ResetCallbackImpl interfaces=[org.jenkinsci.plugins.workflow.steps.TimeoutStepExecution$ResetCallback]  Created at Mon Oct 15 13:44:45 MSK 2018 at hudson.remoting.ExportTable$Entry.(ExportTable.java:114) at hudson.remoting.ExportTable.export(ExportTable.java:365) at hudson.remoting.Channel.internalExport(Channel.java:776) at hudson.remoting.Channel.export(Channel.java:767) at hudson.remoting.Channel.export(Channel.java:731) at org.jenkinsci.plugins.workflow.steps.TimeoutStepExecution$ConsoleLogFilterImpl.writeReplace(TimeoutStepExecution.java:255) at sun.reflect.GeneratedMethodAccessor393.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:1218) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1136) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548) at

[JIRA] (JENKINS-54078) [JEP-210] Exception: Object was recently deallocated when using Git + timeout(activity: true)

2019-02-22 Thread allan.le...@youview.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan Lewis updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54078  
 
 
  [JEP-210] Exception: Object was recently deallocated when using Git + timeout(activity: true)   
 

  
 
 
 
 

 
Change By: 
 Allan Lewis  
 

  
 
 
 
 

 
 When upgrading to Pipeline: Job 2.26 I get errors when combining some wrappers and steps:   {code:java}timeout{timestamps{checkout [$class: 'GitSCM' ...]}}  {code}  Jenkins version: 2.138.2Pipeline: Groovy 2.58Timestamper 1.8.10Git plugin 3.9.1      {noformat}Released at Mon Oct 15 13:44:45 MSK 2018 at hudson.remoting.ExportTable$Entry.release(ExportTable.java:163) at hudson.remoting.ExportTable$ExportList.release(ExportTable.java:300) at hudson.remoting.UserRequest.releaseExports(UserRequest.java:299) at hudson.remoting.UserRequest.releaseExports(UserRequest.java:295) at hudson.remoting.Channel.call(Channel.java:970) at hudson.FilePath.act(FilePath.java:1071) at hudson.FilePath.act(FilePath.java:1060) at org.jenkinsci.plugins.gitclient.Git.getClient(Git.java:137) at hudson.plugins.git.GitSCM.createClient(GitSCM.java:795) at hudson.plugins.git.GitSCM.createClient(GitSCM.java:786) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1154) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)Caused: java.lang.Exception: Object was recently deallocated#17 (ref.0) : object=null type=org.jenkinsci.plugins.workflow.steps.TimeoutStepExecution$ResetCallbackImpl interfaces=[org.jenkinsci.plugins.workflow.steps.TimeoutStepExecution$ResetCallback]  Created at Mon Oct 15 13:44:45 MSK 2018 at hudson.remoting.ExportTable$Entry.(ExportTable.java:114) at hudson.remoting.ExportTable.export(ExportTable.java:365) at hudson.remoting.Channel.internalExport(Channel.java:776) at hudson.remoting.Channel.export(Channel.java:767) at hudson.remoting.Channel.export(Channel.java:731) at org.jenkinsci.plugins.workflow.steps.TimeoutStepExecution$ConsoleLogFilterImpl.writeReplace(TimeoutStepExecution.java:255) at sun.reflect.GeneratedMethodAccessor393.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:1218) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1136) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548) at

[JIRA] (JENKINS-47799) Blue Ocean shouldn't visualize the parallel keyword of a scripted pipeline directly

2019-02-14 Thread allan.le...@youview.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan Lewis updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-47799  
 
 
  Blue Ocean shouldn't visualize the parallel keyword of a scripted pipeline directly   
 

  
 
 
 
 

 
Change By: 
 Allan Lewis  
 
 
Summary: 
 Blue Ocean  View  shouldn't visualize the parallel keyword of a scripted pipeline directly
 

  
 
 
 
 

 
 
 

 
 
 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-52189) GraphListener does not receive FlowStartNode

2019-02-13 Thread allan.le...@youview.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan Lewis assigned an issue to Sam Van Oort  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Sorry, Thomas Weißschuh, I did that by mistake! I probably pressed 'i' while this ticket was focused.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-52189  
 
 
  GraphListener does not receive FlowStartNode   
 

  
 
 
 
 

 
Change By: 
 Allan Lewis  
 
 
Assignee: 
 Allan Lewis Sam Van Oort  
 

  
 
 
 
 

 
 
 

 
 
 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-52189) GraphListener does not receive FlowStartNode

2019-02-13 Thread allan.le...@youview.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan Lewis assigned an issue to Allan Lewis  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52189  
 
 
  GraphListener does not receive FlowStartNode   
 

  
 
 
 
 

 
Change By: 
 Allan Lewis  
 
 
Assignee: 
 Devin Nusbaum Allan Lewis  
 

  
 
 
 
 

 
 
 

 
 
 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-40723) Built Dockerfile images are never removed

2019-01-30 Thread allan.le...@youview.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan Lewis commented on  JENKINS-40723  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Built Dockerfile images are never removed   
 

  
 
 
 
 

 
 

Hrm. So for a GitHub Organisation PR, the $JOB_NAME will be github-org/project/PR-XX.
 I'm not using a GitHub org, so I'm not sure about that. My case is using a manually-configured Git URL. 

First of all, that's an invalid tag name. But let's assume we can make it sane by removing the {{/}}s.
 I'm not using the job name as a tag, I'm using it as the image name, and image names can contain slashes. 

Granted when (the locally written script for) garbage cleanup removes that PR-XX image because PR-XX is closed, the master branch build will build a new (identical) docker image to replace the just removed one. But that's an extra build that shouldn't be necessary.
 

Doesn't deleting all of the Jenkins produced hashy type tags mean that Jenkins won't be able to find an image to re-use for a future run of a job where the Dockerfile has not changed?
 No, because when master is built, it will build the image again - cached if it's on the same node or if one implements push-pull with a registry - and tag it as /master. If we then prune the tag from the branch, we'll still have the image as it will be tagged for master. I'm not saying my solution will work for everyone, I just posted it in case it was useful for others.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[JIRA] (JENKINS-40723) Built Dockerfile images are never removed

2019-01-30 Thread allan.le...@youview.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan Lewis commented on  JENKINS-40723  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Built Dockerfile images are never removed   
 

  
 
 
 
 

 
 Hi Brian J Murrell - for multi-branch pipelines we're currently using JOB_NAME (plus implied :latest). That has the effect of retaining the image from the tip of every branch since JOB_NAME is / in the multi-branch case. We don't yet have a strategy for deleting images from branches that no longer exist on the remote, but that shouldn't be difficult to script. For some non-multibranch pipelines we have, that can be triggered with an arbitrary Git ref via a parameter, we're using "${JOB_BASE_NAME}/${params.GIT_REF}".toLowerCase(). (Docker image names have to be lower-case.)  
 

  
 
 
 
 

 
 
 

 
 
 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-40723) Built Dockerfile images are never removed

2019-01-29 Thread allan.le...@youview.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan Lewis commented on  JENKINS-40723  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Built Dockerfile images are never removed   
 

  
 
 
 
 

 
 

My call here is that Docker image management is out of scope for Declarative to deal with.
 I agree, but Jenkins shouldn't make it unnecessarily difficult. If Docker images were tagged with some combination of the job name and other metadata instead of just a hash, that would help.  
 

  
 
 
 
 

 
 
 

 
 
 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-40723) Built Dockerfile images are never removed

2019-01-29 Thread allan.le...@youview.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan Lewis commented on  JENKINS-40723  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Built Dockerfile images are never removed   
 

  
 
 
 
 

 
 My current workaround for this is to add -tag some-tag-i-understand to additionalBuildArgs. I then have a cleanup script run by cron on each node that deletes all of Jenkins's random-tagged images. If any of these have another tag due to -tag, this will just drop the random tag; otherwise it will delete the image. I think deleting by date is an antipattern anyway since images built a long time ago aren't necessarily unused and images built recently aren't necessarily worth keeping.  
 

  
 
 
 
 

 
 
 

 
 
 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-40455) Environment variables are not accessible outside of node { }

2018-12-21 Thread allan.le...@youview.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan Lewis updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40455  
 
 
  Environment variables are not accessible outside of node { }   
 

  
 
 
 
 

 
Change By: 
 Allan Lewis  
 
 
Summary: 
 Global  Environment  Variables  variables  are not accessible outside of node { }  
 

  
 
 
 
 

 
 
 

 
 
 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-40455) Global Environment Variables are not accessible outside of node { }

2018-12-21 Thread allan.le...@youview.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan Lewis updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40455  
 
 
  Global Environment Variables are not accessible outside of node { }   
 

  
 
 
 
 

 
Change By: 
 Allan Lewis  
 
 
Summary: 
 Global Environment Variables are  no  not  accessible outside of node { }  
 

  
 
 
 
 

 
 
 

 
 
 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-40455) Global environment variables are not accessible outside of node { }

2018-12-21 Thread allan.le...@youview.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan Lewis updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40455  
 
 
  Global environment variables are not accessible outside of node { }   
 

  
 
 
 
 

 
Change By: 
 Allan Lewis  
 
 
Summary: 
 Environment Global environment  variables are not accessible outside of node { }  
 

  
 
 
 
 

 
 
 

 
 
 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-43911) Environment variables can't be used in agent configuration

2018-10-18 Thread allan.le...@youview.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan Lewis commented on  JENKINS-43911  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Environment variables can't be used in agent configuration   
 

  
 
 
 
 

 
 I finally found a workaround for this: 

 

registry = 'my-registry'
imageRepo = 'my-repo-name'

def getImageName(def doCheckout = false) {
  def treeHash = node {
if (doCheckout) checkout scm
sh(script: 'git rev-parse HEAD:', returnStdout: true).trim()
  }
  "$registry/$imageRepo:$treeHash"
}

pipeline {
  agent {
label 'docker-builder'
  }

  stages {
stage('Build & Push Docker Image') {
  steps {
script {
  docker.build(getImageName()).push()
}
  }
}
stage('Do Stuff') {
  agent {
docker {
  image getImageName(true)
}
  }
  steps {
sh 'echo hello'
  }
}
  }
}
 

  
 

  
 
 
 
 

 
 
 

 
 
 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-43911) Environment variables can't be used in agent configuration

2018-10-11 Thread allan.le...@youview.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan Lewis commented on  JENKINS-43911  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Environment variables can't be used in agent configuration   
 

  
 
 
 
 

 
 I have a very similar use case to Caleb Mayeux. This has been in progress for quite a while, can we please have a status update?  
 

  
 
 
 
 

 
 
 

 
 
 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-47612) Internal tests: hudson.tasks.test.AggregatedTestResultPublisherTest fail on Windows

2018-09-05 Thread allan.le...@youview.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan Lewis resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 I believe this was resolved by https://github.com/jenkinsci/junit-plugin/pull/100  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-47612  
 
 
  Internal tests: hudson.tasks.test.AggregatedTestResultPublisherTest fail on Windows   
 

  
 
 
 
 

 
Change By: 
 Allan Lewis  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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-53372) Update Groovy to v2.5.x

2018-08-31 Thread allan.le...@youview.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan Lewis created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53372  
 
 
  Update Groovy to v2.5.x   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Allan Lewis  
 
 
Components: 
 core  
 
 
Created: 
 2018-08-31 15:15  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Allan Lewis  
 

  
 
 
 
 

 
 Jenkins currently bundles Groovy 2.4.11, which was released in April 2017. Groovy 2.5.0 was released in May 2018 and includes a number of new features; the latest patch release is 2.5.2, released August 2018. This ticket proposes upgrading Groovy to the latest in the 2.5 series as a step to upgrading to v3 - see JENKINS-51823.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment