date:20190729

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jack Whelpton edited a comment on  JENKINS-58711  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Container does not exist" error using "sh" in a declarative pipeline   
 

  
 
 
 
 

 
 Last update for me today: I can also reproduce this by omitting the container {} block but adding defaultContainer 'golang' to the kubernetes{} block. Added Jenkins and k8s plugin versions to the Environment section.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58711) "Container does not exist" error using "sh" in a declarative pipeline

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jack Whelpton updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58711  
 
 
  "Container does not exist" error using "sh" in a declarative pipeline   
 

  
 
 
 
 

 
Change By: 
 Jack Whelpton  
 
 
Environment: 
 Jenkins 2.150.3Kubernetes Plugin 1.15.2  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58686) Syncing to revision 0 runs an invalid command

2019-07-29 Thread williambr...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 William Brode commented on  JENKINS-58686  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Syncing to revision 0 runs an invalid command   
 

  
 
 
 
 

 
 I've created a pull request with a potential fix: https://github.com/jenkinsci/p4-plugin/pull/103  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58686) Syncing to revision 0 runs an invalid command

2019-07-29 Thread williambr...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 William Brode started work on  JENKINS-58686  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 William Brode  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58711) "Container does not exist" error using "sh" in a declarative pipeline

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jack Whelpton commented on  JENKINS-58711  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Container does not exist" error using "sh" in a declarative pipeline   
 

  
 
 
 
 

 
 Last update for me today: I can also reproduce this by omitting the container {} block but adding defaultContainer 'golang' to the kubernetes{} block.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-52889) new lines in secret is substituted by spaces when reading via Vault plugin

2019-07-29 Thread the.samuel.beaul...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Samuel Beaulieu commented on  JENKINS-52889  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: new lines in secret is substituted by spaces when reading via Vault plugin   
 

  
 
 
 
 

 
 Hee Won Kim you should iclude the actual shell script lines you are running.   I hit the same issue and debugged the plugin. Things are received from Vault with the "\n" preserved as far as I could see, so I looked into issues with the printing of it. The issue arises because of the command substitution in bash http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_06_03 and you can fix that by setting IFS= as per https://unix.stackexchange.com/questions/164508/why-do-newline-characters-get-lost-when-using-command-substitution   BUT its easier to just embed it in double quotes so that: if I do this it is replaced by spaces 

 

 echo $FOO > .foo 

 but if I do this instead it works 

 

 echo "$FOO" > .foo 

 then the newlines are preserved  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-52889) new lines in secret is substituted by spaces when reading via Vault plugin

2019-07-29 Thread the.samuel.beaul...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Samuel Beaulieu edited a comment on  JENKINS-52889  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: new lines in secret is substituted by spaces when reading via Vault plugin   
 

  
 
 
 
 

 
 [~saillinux] you should  iclude  include  the actual shell script lines you are running. I hit the same issue and debugged the plugin. Things are received from Vault with the "\n" preserved as far as I could see, so I looked into issues with the printing of it. The issue arises because of the command substitution in bash [http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_06_03]and you can fix that by setting {{IFS=}} as per [https://unix.stackexchange.com/questions/164508/why-do-newline-characters-get-lost-when-using-command-substitution] BUT its easier to just embed it in double quotes so that:if I do this it is replaced by spaces{code:java} echo $FOO > .foo{code}but if I do this instead it works{code:java} echo "$FOO" > .foo{code}then the newlines are preserved  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58711) "Container does not exist" error using "sh" in a declarative pipeline

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jack Whelpton commented on  JENKINS-58711  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Container does not exist" error using "sh" in a declarative pipeline   
 

  
 
 
 
 

 
 I can also reproduce the same error by running the declarative example from the Kubernetes plugin documentation as-is: https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/test/resources/org/csanchez/jenkins/plugins/kubernetes/pipeline/declarative.groovy 

 
java.io.IOException: container [maven] does not exist in pod [default-jwg9h]
	at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.waitUntilPodContainersAreReady(ContainerExecDecorator.java:476)
	at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.doLaunch(ContainerExecDecorator.java:271)
	at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.launch(ContainerExecDecorator.java:252) 

  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58454) Able to close other people's issues

2019-07-29 Thread e...@mixmax.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eli Skeggs updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58454  
 
 
  Able to close other people's issues   
 

  
 
 
 
 

 
Change By: 
 Eli Skeggs  
 
 
Component/s: 
 core  
 
 
Component/s: 
 _unsorted  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58648) Dependency-check publisher 5.0.2 does not show Results

2019-07-29 Thread mbarza...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Marco Barzanti commented on  JENKINS-58648  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Dependency-check publisher 5.0.2 does not show Results   
 

  
 
 
 
 

 
 I changed cli arguments as follows: --project DCTest --scan "/var/lib/jenkins/workspace/OSSTest-src" --enableExperimental --disableArchive --log SRSCAdep.log --cveValidForHours 24 --enableRetired --junitFailOnCVSS 11 --out "/var/lib/jenkins/workspace/OSSTest" Nothing was changed, no results and I had: [DependencyCheck] Unable to find Dependency-Check reports to parse    
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58715) Gerrit Trigger Plugin is affected by SECURITY-534 fix in Jenkins 2.176.2 and 2.186

Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Jones resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58715  
 
 
  Gerrit Trigger Plugin is affected by SECURITY-534 fix in Jenkins 2.176.2 and 2.186   
 

  
 
 
 
 

 
Change By: 
 Chris Jones  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 2.29.0  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58715) Gerrit Trigger Plugin is affected by SECURITY-534 fix in Jenkins 2.176.2 and 2.186

Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Jones commented on  JENKINS-58715  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Gerrit Trigger Plugin is affected by SECURITY-534 fix in Jenkins 2.176.2 and 2.186   
 

  
 
 
 
 

 
 Using Gerrit Trigger 2.29.0, I can see the server list with without a whitelist. Thanks!  I still see the Stapler block on 2.28.0, so I guess the 2.29.0 did the trick.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58711) "Container does not exist" error using "sh" in a declarative pipeline

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jack Whelpton edited a comment on  JENKINS-58711  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Container does not exist" error using "sh" in a declarative pipeline   
 

  
 
 
 
 

 
 Added First edit: added  a sample implementation of "pull" to reproduce the problem, which I've narrowed down to an "sh" invocation in the shared library function. Second edit: actually, the shared library is not significant: the same error can be reproduced just using an "sh" command insider a "container" block in a declarative pipeline.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58711) "Container does not exist" error using "sh" in a declarative pipeline

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jack Whelpton updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58711  
 
 
  "Container does not exist" error using "sh" in a declarative pipeline   
 

  
 
 
 
 

 
Change By: 
 Jack Whelpton  
 
 
Summary: 
 " Container  does  not  found from shared library  exist" error  using  "sh" in a  declarative pipeline  
 

  
 
 
 
 

 
 Attempting to  call a shared library function  use the sh command  from inside a container block results in an error of the form java.io.IOException: container [name] does not exist in pod [id]. This same setup works OK when using the scripted pipeline.Example:{code:java}pipeline {  agent {kubernetes {  yaml """apiVersion: v1kind: Podspec:  containers:  - name: golangimage: busyboxcommand:- cattty: true"""}  }  options {skipDefaultCheckout true  }  stages {stage('Build') {  steps {container('golang') {   pull env   sh 'ls' }  }}  }}{code} pull is a function in a globally defined shared library, which takes the environment variables as an argument. The problem appears to be caused by an sh block inside that shared function. Here's a minimal implementation that demonstrates the issue:{code:java}Map call(config) {  final Map props = checkout scm  props.GIT_ARCHIVE = 'src.tar.gz'  sh "tar -zcf $props.GIT_ARCHIVE *"  return props}{code} Running this pipeline yields:{noformat}java.io.IOException: container [golang] does not exist in pod [default-vhhcf] at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.waitUntilPodContainersAreReady(ContainerExecDecorator.java:476) at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.doLaunch(ContainerExecDecorator.java:271) at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.launch(ContainerExecDecorator.java:252) at hudson.Launcher$ProcStarter.start(Launcher.java:455) at org.jenkinsci.plugins.durabletask.BourneShellScript.launchWithCookie(BourneShellScript.java:206) at org.jenkinsci.plugins.durabletask.FileMonitoringTask.launch(FileMonitoringTask.java:99) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.start(DurableTaskStep.java:302) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:268) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:176) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at groovy.lang.MetaClassImpl.invokeMethodOnGroovyObject(MetaClassImpl.java:1278) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1172) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:42) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at

[JIRA] (JENKINS-27092) create a step to abort the build with a NOT_BUILT status

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-27092  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: create a step to abort the build with a NOT_BUILT status   
 

  
 
 
 
 

 
 There is also a use case for passing UNSTABLE: if you have some test failures in one parallel branch and are using failFast, you should be able to interrupt the build now. (Of course this could also be handled directly in the junit step.) Making that look pretty would I think also require replacing ParallelStep.FailFastException with FlowInterruptedException so that the other branches are shown as ABORTED rather than FAILED in Blue Ocean.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58715) Gerrit Trigger Plugin is affected by SECURITY-534 fix in Jenkins 2.176.2 and 2.186

Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Jones commented on  JENKINS-58715  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Gerrit Trigger Plugin is affected by SECURITY-534 fix in Jenkins 2.176.2 and 2.186   
 

  
 
 
 
 

 
 Yes, it was left on 2.72.2 after the JEP-200 induced plugin upgrade. I'll try to stand up a clone and test 2.29.0.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58715) Gerrit Trigger Plugin is affected by SECURITY-534 fix in Jenkins 2.176.2 and 2.186

Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Jones edited a comment on  JENKINS-58715  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Gerrit Trigger Plugin is affected by SECURITY-534 fix in Jenkins 2.176.2 and 2.186   
 

  
 
 
 
 

 
 Yes, it was left on 2. 72 27 .2 after the JEP-200 induced plugin upgrade. I'll try to stand up a clone and test 2.29.0.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58717) Modify ATH to be compatible with new GitHub Branch Source UI

Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58717  
 
 
  Modify ATH to be compatible with new GitHub Branch Source UI   
 

  
 
 
 
 

 
Change By: 
 Karl Shultz  
 

  
 
 
 
 

 
 *Summary*Starting with GitHub Branch Source 2.5.5 (see [PR|https://github.com/jenkinsci/github-branch-source-plugin/pull/236]), we now have two ways to set up our remote repo for multibranch projects based on GitHub repositories. This ticket represents the accompanying updates that the acceptance test harness needs in order to make this work.*Details*The new UI offers, and defaults to, the ability to supply a single HTTPS URL, in much the same way you'd copy/paste such a URL into a {{git clone}} command. The ATH needs to be modified to accomodate this.Before the above-mentioned improvement to GitHub Branch Source, users needed to first supply the repository owner. For example, And then, if the repo owner had hundreds or even thousands of repos, it could take a very long time to populate the resulting drop-down menu. My suspicion is that this delay is the reason why  [  the test was set to  [ {{@Ignore}}|https://github.com/jenkinsci/acceptance-test-harness/blob/ master e538cb7ffeeeb11ce5aad4de3b6bc59d03b9a56d /src/test/java/plugins/WorkflowMultibranchTest.java#L37].The page now looks like this when creating a new project: !image-2019-07-29-16-25-51-544.png|thumbnail! It's possible that the ATH will also need to maintain some sort of backward compatibility with the old UI.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-58717) Modify ATH to be compatible with new GitHub Branch Source UI

Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58717  
 
 
  Modify ATH to be compatible with new GitHub Branch Source UI   
 

  
 
 
 
 

 
Change By: 
 Karl Shultz  
 

  
 
 
 
 

 
 *Summary*Starting with GitHub Branch Source 2.5.5 (see [PR|https://github.com/jenkinsci/github-branch-source-plugin/pull/236]), we now have two ways to set up our remote repo for multibranch projects based on GitHub repositories. This ticket represents the accompanying updates that the acceptance test harness needs in order to make this work.*Details*The new UI offers, and defaults to, the ability to supply a single HTTPS URL, in much the same way you'd copy/paste such a URL into a {{git clone}} command. The ATH needs to be modified to accomodate this.Before the above-mentioned improvement to GitHub Branch Source, users needed to first supply the repository owner. For example, And then, if the repo owner had hundreds or even thousands of repos, it could take a very long time to populate the resulting drop-down menu. My suspicion is that this delay is the reason why the test was set to [{{@Ignore}}  d |https://github.com/jenkinsci/acceptance-test-harness/blob/master/src/test/java/plugins/WorkflowMultibranchTest.java#L37].The page now looks like this when creating a new project: !image-2019-07-29-16-25-51-544.png|thumbnail! It's possible that the ATH will also need to maintain some sort of backward compatibility with the old UI.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-58717) Modify ATH to be compatible with new GitHub Branch Source UI

Title: Message Title

Karl Shultz updated an issue

Jenkins / JENKINS-58717

Modify ATH to be compatible with new GitHub Branch Source UI

Change By:
Karl Shultz

*Summary*Starting with Git GitHub Branch Source 2.5.5 (see [PR|https://github.com/jenkinsci/github-branch-source-plugin/pull/236]), we now have two ways to set up our remote repo for multibranch projects based on GitHub repositories. This ticket represents the accompanying updates that the acceptance test harness needs in order to make this work. *Details* The new UI offers, and defaults to, the ability to supply a single HTTPS URL, in much the same way you'd copy/paste such a URL into a {{git clone}} command. The ATH needs to be modified to accomodate this. Before the above-mentioned improvement to GitHub Branch Source, users needed to first supply the repository owner. For example, And then, if the repo owner had hundreds or even thousands of repos, it could take a very long time to populate the resulting drop-down menu. My suspicion is that this delay is the reason why the test was being [{{@Ignore}} d|https://github.com/jenkinsci/acceptance-test-harness/blob/master/src/test/java/plugins/WorkflowMultibranchTest.java#L37]. The page now looks like this when creating a new project: !image-2019-07-29-16-25-51-544.png|thumbnail! It's possible that the ATH will also need to maintain some sort of backward compatibility with the old UI.

Add Comment

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

[JIRA] (JENKINS-58717) Modify ATH to be compatible with new GitHub Branch Source UI

Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58717  
 
 
  Modify ATH to be compatible with new GitHub Branch Source UI   
 

  
 
 
 
 

 
Change By: 
 Karl Shultz  
 

  
 
 
 
 

 
 *Summary*Starting with GitHub Branch Source 2.5.5 (see [PR|https://github.com/jenkinsci/github-branch-source-plugin/pull/236]), we now have two ways to set up our remote repo for multibranch projects based on GitHub repositories. This ticket represents the accompanying updates that the acceptance test harness needs in order to make this work.*Details*The new UI offers, and defaults to, the ability to supply a single HTTPS URL, in much the same way you'd copy/paste such a URL into a {{git clone}} command. The ATH needs to be modified to accomodate this.Before the above-mentioned improvement to GitHub Branch Source, users needed to first supply the repository owner. For example, And then, if the repo owner had hundreds or even thousands of repos, it could take a very long time to populate the resulting drop-down menu. My suspicion is that this delay is the reason why the test was  being  set to  [{{@Ignore}} d|https://github.com/jenkinsci/acceptance-test-harness/blob/master/src/test/java/plugins/WorkflowMultibranchTest.java#L37].The page now looks like this when creating a new project: !image-2019-07-29-16-25-51-544.png|thumbnail! It's possible that the ATH will also need to maintain some sort of backward compatibility with the old UI.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-58717) Modify ATH to be compatible with new GitHub Branch Source UI

Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58717  
 
 
  Modify ATH to be compatible with new GitHub Branch Source UI   
 

  
 
 
 
 

 
Change By: 
 Karl Shultz  
 
 
Issue Type: 
 Bug Improvement  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58717) Modify ATH to be compatible with new GitHub Branch Source UI

Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58717  
 
 
  Modify ATH to be compatible with new GitHub Branch Source UI   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Oliver Gondža  
 
 
Attachments: 
 image-2019-07-29-16-25-51-544.png  
 
 
Components: 
 acceptance-test-harness  
 
 
Created: 
 2019-07-29 20:26  
 
 
Environment: 
 GitHub Branch Source 2.5.5  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Karl Shultz  
 

  
 
 
 
 

 
 Summary Starting with Git The new UI offers, and defaults to, the ability to supply a single HTTPS URL, in much the same way you'd copy/paste such a URL into a git clone command. The ATH needs to be modified to accomodate this. The page now looks like this when creating a new project:   It's possible that the ATH will also need to maintain some sort of backward compatibility with the old UI.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-58716) Failure to check out specified tag for incremental version

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58716  
 
 
  Failure to check out specified tag for incremental version   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 plugin-compat-tester  
 
 
Created: 
 2019-07-29 19:58  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Jesse Glick  
 

  
 
 
 
 

 
 I tried to run the PCT against an incremental release of a plugin, and it failed: 

 

Created plugin checkout dir : .../pct-work/jsch
Checking out from SCM connection URL : scm:git:git://github.com/jenkinsci/jsch-plugin.git (jsch-0.1.55.1-rc41.4943eb07c811)
[INFO] Executing: /bin/sh -c cd '.../pct-work' && 'git' 'clone' 'git://github.com/jenkinsci/jsch-plugin.git' '.../pct-work/jsch'
[INFO] Working directory: .../pct-work
[INFO] Executing: /bin/sh -c cd '.../pct-work/jsch' && 'git' 'fetch' 'git://github.com/jenkinsci/jsch-plugin.git'
[INFO] Working directory: .../pct-work/jsch
[INFO] Executing: /bin/sh -c cd '.../pct-work/jsch' && 'git' 'checkout' 'jsch-0.1.55.1-rc41.4943eb07c811'
[INFO] Working directory: .../pct-work/jsch
Error : The git-checkout command failed. || Cloning into '.../pct-work/jsch'...
>From git://github.com/jenkinsci/jsch-plugin
 * branchHEAD   -> FETCH_HEAD
error: pathspec 'jsch-0.1.55.1-rc41.4943eb07c811' did not match any file(s) known to git
 

 That is because this code improperly assumes that ${project.artifactId}-${project.version} is going to be a valid tag. Maven makes no such guarantee. Rather, this code should be looking for a /project/scm/tag and honoring it if present. In this case it would have found

[JIRA] (JENKINS-58715) Gerrit Trigger Plugin is affected by SECURITY-534 fix in Jenkins 2.176.2 and 2.186

2019-07-29 Thread db...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-58715  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Gerrit Trigger Plugin is affected by SECURITY-534 fix in Jenkins 2.176.2 and 2.186   
 

  
 
 
 
 

 
 Which version of Gerrit Trigger Plugin is this? My guess would be older than 2.29.0.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58548) scriptText URL returns extra newlines

Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Sicker commented on  JENKINS-58548  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: scriptText URL returns extra newlines   
 

  
 
 
 
 

 
 https://github.com/jenkinsci/jenkins/pull/4133 Figured out the problem. Jelly will trim things by default, but a JEXL _expression_ in l:view was introducing untrimmed whitespace for some reason. Refactoring the JEXL _expression_ into vanilla Jelly tags fixed the whitespace issue.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58548) scriptText URL returns extra newlines

Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Sicker updated  JENKINS-58548  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58548  
 
 
  scriptText URL returns extra newlines   
 

  
 
 
 
 

 
Change By: 
 Matt Sicker  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-33217) DescribableHelper does not detect stray parameters

2019-07-29 Thread cch...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Carroll Chiou updated  JENKINS-33217  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 A fix for this issue has been released in version 1.20 of structs  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-33217  
 
 
  DescribableHelper does not detect stray parameters   
 

  
 
 
 
 

 
Change By: 
 Carroll Chiou  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 structs 1.20  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58699) AppCenter Plugin is unable to read parameters set to `Path To App`

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mez Pahlan updated  JENKINS-58699  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58699  
 
 
  AppCenter Plugin is unable to read parameters set to `Path To App`   
 

  
 
 
 
 

 
Change By: 
 Mez Pahlan  
 
 
Status: 
 Closed Fixed but Unreleased  
 
 
Resolution: 
 Fixed Duplicate  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58699) AppCenter Plugin is unable to read parameters set to `Path To App`

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mez Pahlan closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58699  
 
 
  AppCenter Plugin is unable to read parameters set to `Path To App`   
 

  
 
 
 
 

 
Change By: 
 Mez Pahlan  
 
 
Status: 
 Open Closed  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200988.1564386205000.3439.1564424700576%40Atlassian.JIRA.

[JIRA] (JENKINS-58699) AppCenter Plugin is unable to read parameters set to `Path To App`

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mez Pahlan assigned an issue to Alexey Strakh  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58699  
 
 
  AppCenter Plugin is unable to read parameters set to `Path To App`   
 

  
 
 
 
 

 
Change By: 
 Mez Pahlan  
 
 
Assignee: 
 Mez Pahlan Alexey Strakh  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58715) Gerrit Trigger Plugin is affected by SECURITY-534 fix in Jenkins 2.176.2 and 2.186

Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Jones created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58715  
 
 
  Gerrit Trigger Plugin is affected by SECURITY-534 fix in Jenkins 2.176.2 and 2.186   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 rsandell  
 
 
Components: 
 gerrit-trigger-plugin  
 
 
Created: 
 2019-07-29 18:23  
 
 
Environment: 
 Core 2.176.2+ and 2.186+  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Chris Jones  
 

  
 
 
 
 

 
 After upgrading our master to CloudBees 2.138.42.0.1, which picked up a back-ported SECURITY-534 fix, I was unable to view the server list on the Gerrit Trigger status page. The table simply read "Data Error." and the /gerrit-trigger/serverStatuses call returns a 404. The servers themselves seemed functional according to the logs. Also in the logs: 

 

WARNING: New Stapler dispatch rules result in the URL "/gerrit-trigger/serverStatuses" no longer being allowed. If you consider it safe to use, add the following to the whitelist: "com.sonyericsson.hudson.plugins.gerrit.trigger.GerritManagement serverStatuses". Learn more: https://jenkins.io/redirect/stapler-facet-restrictions 

 Adding the above to the whitelist fixed the issue.

[JIRA] (JENKINS-58699) AppCenter Plugin is unable to read parameters set to `Path To App`

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mez Pahlan commented on  JENKINS-58699  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: AppCenter Plugin is unable to read parameters set to `Path To App`   
 

  
 
 
 
 

 
 Hi Alexey Strakh, thanks for reporting. I'm going to tag this as a duplicate of JENKINS-58329 as some work has already started regarding environment variables. Can you confirm that $MY_PACKAGE is an environment variable and not some other type of variable (which I think will be fine too).  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58548) scriptText URL returns extra newlines

Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Sicker assigned an issue to Matt Sicker  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58548  
 
 
  scriptText URL returns extra newlines   
 

  
 
 
 
 

 
Change By: 
 Matt Sicker  
 
 
Assignee: 
 Matt Sicker  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58548) scriptText URL returns extra newlines

Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Sicker started work on  JENKINS-58548  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Matt Sicker  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58714) Cannot save System Settings or update Jobs with latest JIRA Plugin versions

2019-07-29 Thread pet...@epignosishq.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Petros Bountis created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58714  
 
 
  Cannot save System Settings or update Jobs with latest JIRA Plugin versions   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 Jenkins-Jira-Plugin-1.png, Jenkins-Jira-Plugin-2.png, Jenkins-Jira-Plugin-3.png  
 
 
Components: 
 jira-plugin  
 
 
Created: 
 2019-07-29 18:09  
 
 
Environment: 
 Jenkins ver. 2.176.2  JIRA plugin 3.0.8  CentOS 7  OpenJDK 1.8.0_222-b10  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Petros Bountis  
 

  
 
 
 
 

 
 Hello. After updating to the latest versions of JIRA Plugin (3.0.7 || 3.0.8) the following error occurs when trying to save Jenkins global configurations or view Pipeline Job configurations. 

 

java.lang.AssertionError: URL cannot be empty at hudson.plugins.jira.JiraSite.(JiraSite.java:285) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at org.kohsuke.stapler.RequestImpl.invokeConstructor(RequestImpl.java:529) at org.kohsuke.stapler.RequestImpl.instantiate(RequestImpl.java:784) at org.kohsuke.stapler.RequestImpl.access$200(RequestImpl.java:83) at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:678) at

[JIRA] (JENKINS-58713) Redownloading if plugin URL entered

2019-07-29 Thread natasha.st...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Natasha Stopa created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58713  
 
 
  Redownloading if plugin URL entered
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Natasha Stopa  
 
 
Components: 
 plugin-installation-manager-tool  
 
 
Created: 
 2019-07-29 17:54  
 
 
Labels: 
 plugin-manager gsoc-2019  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Natasha Stopa  
 

  
 
 
 
 

 
 Right now if a plugin fails to download, the plugin name will be appended and it will be try to be re-downloaded. The first step of the download process is to determine the download URL. If the the user input a URL for a requested plugin, the download URL will be the URL the user specified. If the plugin fails to download, appending the plugin name will not affect the download url or download process. Should there be some type of different way to retry to download plugins that have a url directly entered?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-38276) Increase size of text area for pipeline script code

2019-07-29 Thread block....@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jon B commented on  JENKINS-38276  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Increase size of text area for pipeline script code   
 

  
 
 
 
 

 
 Marcel Meschenmoser Can you improve it please? I took a look at it and the widget that is being used didn't have a way to resize it at the time. If Marcel is passionate about it maybe he can close this ticket. I couldn't figure it out.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58390) Docker cloud provisioning 1 slave behind

2019-07-29 Thread adam.broussea...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Adam Brousseau commented on  JENKINS-58390  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Docker cloud provisioning 1 slave behind   
 

  
 
 
 
 

 
 As a workaround, we wrote a separate job that runs after the first job has started, and asks for the same container, then times out.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-45579) Step to set stage or parallel status

2019-07-29 Thread dnusb...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-45579  
 
 
  Step to set stage or parallel status   
 

  
 
 
 
 

 
Change By: 
 Devin Nusbaum  
 
 
Status: 
 Reopened Resolved  
 
 
Assignee: 
 Devin Nusbaum  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183763.1500306894000.3222.1564421830129%40Atlassian.JIRA.

[JIRA] (JENKINS-45579) Step to set stage or parallel status

2019-07-29 Thread dnusb...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum commented on  JENKINS-45579  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Step to set stage or parallel status   
 

  
 
 
 
 

 
 The original example in the description of this ticket was fixed as part of JENKINS-39203 with the new warnError and unstable steps and changes to the catchError step, so I am going to close this issue See https://jenkins.io/blog/2019/07/05/jenkins-pipeline-stage-result-visualization-improvements/ and this earlier comment for details. if you have a request for a step that is related to the general title of the ticket but is not covered by the changes I mentioned, please file a new ticket along the lines of JENKINS-27092.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58709) Nested pod templates inherit container of upper level pod

2019-07-29 Thread sergio.merin...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sergio Merino updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58709  
 
 
  Nested pod templates inherit container of upper level pod   
 

  
 
 
 
 

 
Change By: 
 Sergio Merino  
 

  
 
 
 
 

 
 kubernetes plugin version: 1.17.2When I run a podTemplate nested, it inherit the containers of the upper level podTemplate. It is a weird behaviour is better to explain it with an exampleCode:{code:java}podTemplate(showRawYaml: true, label: "alpine1", cloud: "Build farm", containers: [  containerTemplate(name: 'alpine', image: 'alpine', ttyEnabled: true, command: "cat")]) {node ("alpine1") {container('alpine') {sh 'whoami'podTemplate(showRawYaml: true, label: "golang", cloud: "Build farm", containers: [  containerTemplate(name: 'golang', image: 'golang', ttyEnabled: true, command: "cat")]) {  node ("golang") {container('golang') {  sh 'sleep 120'}  }}}}} {code} Expected * alpine pod template containers: \{jnlp} \{alpine} * golang pod template containers: \{jnlp} \{golang}What I have: * alpine pod template containers: \{jnlp} \{alpine} * golang pod template containers: \{jnlp} \{golang} \{alpine}  Log(removed env variables):{code:java} Still waiting to schedule taskWaiting for next available executor on 'alpine1-dgpx2-5jp6k'Agent alpine1-prfs1-ghwvg is provisioned from template Kubernetes Pod Template---apiVersion: "v1"kind: "Pod"metadata:  annotations:buildUrl: "https:// callisto . dev . youview . co.uk/job/CII_test_pod_template_nest/13/ "  labels:jenkins: "slave"jenkins/alpine1: "true"  name: "alpine1-prfs1-ghwvg"spec:  containers:  - command:- "cat"env:- name: "JENKINS_SECRET"  ...image: "alpine"imagePullPolicy: "IfNotPresent"name: "alpine"resources:  limits: {}  requests: {}securityContext:  privileged: falsetty: truevolumeMounts:- mountPath: "/home/jenkins"  name: "workspace-volume"  readOnly: falseworkingDir: "/home/jenkins"  - env:- name: "JENKINS_SECRET"  ...image: "jenkins/jnlp-slave:alpine"name: "jnlp"volumeMounts:- mountPath: "/home/jenkins"  name: "workspace-volume"  readOnly: false  nodeSelector: {}  restartPolicy: "Never"  volumes:  - emptyDir: {}name: "workspace-volume"Running on alpine1-prfs1-ghwvg in /home/jenkins/workspace/CII_test_pod_template_nest[Pipeline] {[Pipeline] container[Pipeline] {[Pipeline] sh+ whoamiroot[Pipeline] podTemplate[Pipeline] {[Pipeline] nodeStill waiting to schedule task'golang-t6g4f-4tzqr' is offlineAgent golang-t6g4f-4tzqr is provisioned from template Kubernetes Pod Template---apiVersion: "v1"kind: "Pod"metadata:  annotations:buildUrl: "https:// callisto . dev . youview . co.uk/job/CII_test_pod_template_nest/13/ "  labels:jenkins: "slave"jenkins/golang: "true"  name: "golang-t6g4f-4tzqr"spec:  containers:  - command:- "cat"env:- name: "JENKINS_SECRET"  ...image: "alpine"imagePullPolicy:

[JIRA] (JENKINS-58686) Syncing to revision 0 runs an invalid command

2019-07-29 Thread williambr...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 William Brode assigned an issue to William Brode  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58686  
 
 
  Syncing to revision 0 runs an invalid command   
 

  
 
 
 
 

 
Change By: 
 William Brode  
 
 
Assignee: 
 William Brode  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-24461) Filter change log based on included/excluded regions

2019-07-29 Thread kerrhome (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Shannon Kerr commented on  JENKINS-24461  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Filter change log based on included/excluded regions   
 

  
 
 
 
 

 
 Would be good to see this 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.157042.1409147564000.3033.1564420080488%40Atlassian.JIRA.

[JIRA] (JENKINS-58712) Docker tool configuration over Jenkins slaves

2019-07-29 Thread dani...@radware.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Juravski created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58712  
 
 
  Docker tool configuration over Jenkins slaves   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Nicolas De Loof  
 
 
Components: 
 docker-commons-plugin, docker-plugin  
 
 
Created: 
 2019-07-29 16:58  
 
 
Labels: 
 jenkins plug-in docker  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Daniel Juravski  
 

  
 
 
 
 

 
 Hi, I'm using docker-commons-plugin v.1.13 and jenkins v.1.121.3 I have several ubuntu (16.04) slaves connected to my jenkins.   My goal is to configure Docker as a global tool, i.e be able to run docker commands without having any docker pkgs on my slaves. I configured  the docker-commons-plugin and add it as it written at the GitHub README, but the only thing I able to do is $docker version Any attempt to make something practical (i.e. docker build/run/push/...) is over with the following error: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?     Once again, I do no want to install the docker pkg over my slaves, but only use the docker tool. What can I do?   Thanks!

[JIRA] (JENKINS-58711) Container not found from shared library using declarative pipeline

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jack Whelpton commented on  JENKINS-58711  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Container not found from shared library using declarative pipeline   
 

  
 
 
 
 

 
 Added a sample implementation of "pull" to reproduce the problem, which I've narrowed down to an "sh" invocation in the shared library function.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58711) Container not found from shared library using declarative pipeline

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jack Whelpton updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58711  
 
 
  Container not found from shared library using declarative pipeline   
 

  
 
 
 
 

 
Change By: 
 Jack Whelpton  
 

  
 
 
 
 

 
 Attempting to call a shared library function from inside a container block results in an error of the form java.io.IOException: container [name] does not exist in pod [id]. This same setup works OK when using the scripted pipeline.Example:{code:java}pipeline {  agent {kubernetes {  yaml """apiVersion: v1kind: Podspec:  containers:  - name: golangimage: busyboxcommand:- cattty: true"""}  }  options {skipDefaultCheckout true  }  stages {stage('Build') {  steps {container('golang') {  pull env}  }}  }}{code}pull is a function in a globally defined shared library, which takes the environment variables as an argument.  I don  The problem appears to be caused by an sh block inside that shared function. Here ' t think its precise definition affects this bug s a minimal implementation that demonstrates the issue:{code:java}Map call(config) {  final Map props = checkout scm  props . GIT_ARCHIVE = 'src.tar.gz'  sh "tar -zcf $props.GIT_ARCHIVE *"  return props}{code}  Running this pipeline yields:{noformat}java.io.IOException: container [golang] does not exist in pod [default-vhhcf] at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.waitUntilPodContainersAreReady(ContainerExecDecorator.java:476) at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.doLaunch(ContainerExecDecorator.java:271) at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.launch(ContainerExecDecorator.java:252) at hudson.Launcher$ProcStarter.start(Launcher.java:455) at org.jenkinsci.plugins.durabletask.BourneShellScript.launchWithCookie(BourneShellScript.java:206) at org.jenkinsci.plugins.durabletask.FileMonitoringTask.launch(FileMonitoringTask.java:99) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.start(DurableTaskStep.java:302) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:268) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:176) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at groovy.lang.MetaClassImpl.invokeMethodOnGroovyObject(MetaClassImpl.java:1278) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1172) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:42) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:20) at getRepoTags.call(/var/jenkins_home/jobs/attr-dict-import/branches/master/builds/36/libs/jenkins/vars/getRepoTags.groovy:6) at ___cps.transform___(Native Method) at

[JIRA] (JENKINS-58710) Classes with Same name and Different Packages are being triggered JCASC

Title: Message Title


 
 
 
 

 
 
 

 
   
 André Ilhicas Santos updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58710  
 
 
  Classes with Same name and Different Packages are being triggered JCASC   
 

  
 
 
 
 

 
Change By: 
 André Ilhicas Santos  
 

  
 
 
 
 

 
 When using Azure Credentials with CASC references to Azure Credentials ( plugin azure-credentials:1.6.1 ) get caught by a different packageExample for CASC confs  - {code:java}azure: clientId: "${azure_clientId}" clientSecret: "${azure_clientSecret}" description: "Azure Credentials" id: "X" scope: GLOBAL subscriptionId: "${azure_subscriptionId}" azureEnvironmentName: "Azure"{code}This results in:```{code:java}jenkins_1 | io.jenkins.plugins.casc.ConfiguratorException: Invalid configuration elements for type class com.microsoftopentechnologies.windowsazurestorage.helper.AzureCredentials : azureEnvironmentName,clientId,clientSecret,subscriptionId,tenant. jenkins_1 | Available attributes : blobEndpointURL, description, id, scope, storageAccountName, storageKey jenkins_1 | at io.jenkins.plugins.casc.BaseConfigurator.handleUnknown(BaseConfigurator.java:378) jenkins_1 | at io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:367) jenkins_1 | at io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:277) jenkins_1 | at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.configure(DataBoundConfigurator.java:83) jenkins_1 | at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.lambda$doConfigure$16668e2$1(HeteroDescribableConfigurator.java:278) jenkins_1 | at io.vavr.CheckedFunction0.lambda$unchecked$52349c75$1(CheckedFunction0.java:201) jenkins_1 | at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.doConfigure(HeteroDescribableConfigurator.java:278) jenkins_1 | at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.lambda$null$2(HeteroDescribableConfigurator.java:86) jenkins_1 | at io.vavr.control.Option.map(Option.java:373) jenkins_1 | at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.lambda$configure$3(HeteroDescribableConfigurator.java:86) jenkins_1 | at io.vavr.Tuple2.apply(Tuple2.java:239) jenkins_1 | at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.configure(HeteroDescribableConfigurator.java:83) jenkins_1 | at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.configure(HeteroDescribableConfigurator.java:55) jenkins_1 | at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.tryConstructor(DataBoundConfigurator.java:153) jenkins_1 | at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.instance(DataBoundConfigurator.java:77) jenkins_1 | at io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:268) jenkins_1 | at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.check(DataBoundConfigurator.java:101) jenkins_1 | at io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:345) jenkins_1 | at

[JIRA] (JENKINS-58710) Classes with Same name and Different Packages are being triggered JCASC

Title: Message Title


 
 
 
 

 
 
 

 
   
 André Ilhicas Santos updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58710  
 
 
  Classes with Same name and Different Packages are being triggered JCASC   
 

  
 
 
 
 

 
Change By: 
 André Ilhicas Santos  
 

  
 
 
 
 

 
 When using Azure Credentials with CASC references to Azure Credentials ( plugin azure-credentials:1.6.1 ) get caught by a different packageExample for CASC confs  - {code:java}azure: clientId: "${azure_clientId}" clientSecret: "${azure_clientSecret}" description: "Azure Credentials" id: "X" scope: GLOBAL subscriptionId: "${azure_subscriptionId}" azureEnvironmentName: "Azure"{code}This results in:```{code:java}jenkins_1 | io.jenkins.plugins.casc.ConfiguratorException: Invalid configuration elements for type class com.microsoftopentechnologies.windowsazurestorage.helper.AzureCredentials : azureEnvironmentName,clientId,clientSecret,subscriptionId,tenant. jenkins_1 | Available attributes : blobEndpointURL, description, id, scope, storageAccountName, storageKey jenkins_1 | at io.jenkins.plugins.casc.BaseConfigurator.handleUnknown(BaseConfigurator.java:378) jenkins_1 | at io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:367) jenkins_1 | at io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:277) jenkins_1 | at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.configure(DataBoundConfigurator.java:83) jenkins_1 | at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.lambda$doConfigure$16668e2$1(HeteroDescribableConfigurator.java:278) jenkins_1 | at io.vavr.CheckedFunction0.lambda$unchecked$52349c75$1(CheckedFunction0.java:201) jenkins_1 | at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.doConfigure(HeteroDescribableConfigurator.java:278) jenkins_1 | at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.lambda$null$2(HeteroDescribableConfigurator.java:86) jenkins_1 | at io.vavr.control.Option.map(Option.java:373) jenkins_1 | at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.lambda$configure$3(HeteroDescribableConfigurator.java:86) jenkins_1 | at io.vavr.Tuple2.apply(Tuple2.java:239) jenkins_1 | at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.configure(HeteroDescribableConfigurator.java:83) jenkins_1 | at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.configure(HeteroDescribableConfigurator.java:55) jenkins_1 | at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.tryConstructor(DataBoundConfigurator.java:153) jenkins_1 | at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.instance(DataBoundConfigurator.java:77) jenkins_1 | at io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:268) jenkins_1 | at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.check(DataBoundConfigurator.java:101) jenkins_1 | at io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:345) jenkins_1 | at

[JIRA] (JENKINS-58711) Container not found from shared library using declarative pipeline

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jack Whelpton created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58711  
 
 
  Container not found from shared library using declarative pipeline   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Carlos Sanchez  
 
 
Components: 
 kubernetes-plugin, pipeline-model-definition-plugin  
 
 
Created: 
 2019-07-29 16:21  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Jack Whelpton  
 

  
 
 
 
 

 
 Attempting to call a shared library function from inside a container block results in an error of the form java.io.IOException: container [name] does not exist in pod [id]. This same setup works OK when using the scripted pipeline. Example: 

 

pipeline {
  agent {
kubernetes {
  yaml """
apiVersion: v1
kind: Pod
spec:
  containers:
  - name: golang
image: busybox
command:
- cat
tty: true
"""
}
  }
  options {
skipDefaultCheckout true
  }
  stages {
stage('Build') {
  steps {
container('golang') {
  pull env
}
  }
}
  }
}

 

 pull is a function in a globally defined shared library, which takes the environment variables as an argument. I don't think its precise definition affects this bug. Running this pipeline yields: 

 
java.io.IOException: container [golang] does not exist in pod [default-vhhcf]
	at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.waitUntilPodContainersAreReady(ContainerExecDecorator.java:476)
	at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.doLaunch(ContainerExecDecorator.java:271)
	at

[JIRA] (JENKINS-58710) Classes with Same name and Different Packages are being triggered JCASC

Title: Message Title


 
 
 
 

 
 
 

 
   
 André Ilhicas Santos updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58710  
 
 
  Classes with Same name and Different Packages are being triggered JCASC   
 

  
 
 
 
 

 
Change By: 
 André Ilhicas Santos  
 

  
 
 
 
 

 
 When using Azure Credentials with CASC references to Azure Credentials ( plugin azure-credentials:1.6.1 ) get caught by a different packageExample for CASC confs ```    -  {code:java}  azure: clientId: "${azure_clientId}" clientSecret: "${azure_clientSecret}" description: "Azure Credentials" id: "X" scope: GLOBAL subscriptionId: "${azure_subscriptionId}" azureEnvironmentName: "Azure" {code}  ```   This results in:``` {code:java} jenkins_1 | io.jenkins.plugins.casc.ConfiguratorException: Invalid configuration elements for type class com.microsoftopentechnologies.windowsazurestorage.helper.AzureCredentials : azureEnvironmentName,clientId,clientSecret,subscriptionId,tenant.jenkins_1 | Available attributes : blobEndpointURL, description, id, scope, storageAccountName, storageKeyjenkins_1 | at io.jenkins.plugins.casc.BaseConfigurator.handleUnknown(BaseConfigurator.java:378)jenkins_1 | at io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:367)jenkins_1 | at io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:277)jenkins_1 | at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.configure(DataBoundConfigurator.java:83)jenkins_1 | at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.lambda$doConfigure$16668e2$1(HeteroDescribableConfigurator.java:278)jenkins_1 | at io.vavr.CheckedFunction0.lambda$unchecked$52349c75$1(CheckedFunction0.java:201)jenkins_1 | at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.doConfigure(HeteroDescribableConfigurator.java:278)jenkins_1 | at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.lambda$null$2(HeteroDescribableConfigurator.java:86)jenkins_1 | at io.vavr.control.Option.map(Option.java:373)jenkins_1 | at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.lambda$configure$3(HeteroDescribableConfigurator.java:86)jenkins_1 | at io.vavr.Tuple2.apply(Tuple2.java:239)jenkins_1 | at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.configure(HeteroDescribableConfigurator.java:83)jenkins_1 | at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.configure(HeteroDescribableConfigurator.java:55)jenkins_1 | at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.tryConstructor(DataBoundConfigurator.java:153)jenkins_1 | at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.instance(DataBoundConfigurator.java:77)jenkins_1 | at io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:268)jenkins_1 | at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.check(DataBoundConfigurator.java:101)jenkins_1 | at io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:345)jenkins_1 | at

[JIRA] (JENKINS-58710) Classes with Same name and Different Packages are being triggered JCASC

Title: Message Title


 
 
 
 

 
 
 

 
   
 André Ilhicas Santos created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58710  
 
 
  Classes with Same name and Different Packages are being triggered JCASC   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Jie Shen  
 
 
Components: 
 azure-credentials-plugin, configuration-as-code-plugin, windows-azure-storage-plugin  
 
 
Created: 
 2019-07-29 16:10  
 
 
Environment: 
 Jenkins version 2.187 (Docker - Alpine based)   windows-azure-storage:1.1.0  azure-credentials:1.6.1  configuration-as-code:1.24  configuration-as-code-support:1.18  
 
 
Priority: 
  Major  
 
 
Reporter: 
 André Ilhicas Santos  
 

  
 
 
 
 

 
 When using Azure Credentials with CASC references to Azure Credentials ( plugin azure-credentials:1.6.1 ) get caught by a different package Example for CASC confs ``` 
 
azure: clientId: "${azure_clientId}" clientSecret: "${azure_clientSecret}" description: "Azure Credentials" id: "X" scope: GLOBAL subscriptionId: "${azure_subscriptionId}" azureEnvironmentName: "Azure" ``` 
 This results in: ``` jenkins_1 | io.jenkins.plugins.casc.ConfiguratorException: Invalid configuration elements for type class com.microsoftopentechnologies.windowsazurestorage.helper.AzureCredentials : azureEnvironmentName,clientId,clientSecret,subscriptionId,tenant. jenkins_1 | Available attributes : blobEndpointURL, description, id, scope, storageAccountName, storageKey jenkins_1 | at io.jenkins.plugins.casc.BaseConfigurator.handleUnknown(BaseConfigurator.java:378) jenkins_1 | at io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:367) jenkins_1 | at io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:277) jenkins_1 | at

[JIRA] (JENKINS-58667) NumberFormatException when parsing deploy url

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-58667  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: NumberFormatException when parsing deploy url   
 

  
 
 
 
 

 
 I probably do not know what you are really asking here. Best to ask on the dev list with a concrete example.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-55945) Got IllegalStateException while restart Jenkins

2019-07-29 Thread jthomp...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeff Thompson commented on  JENKINS-55945  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Got IllegalStateException while restart Jenkins
 

  
 
 
 
 

 
 Simon Tunnat, as I mentioned above, you can read about the LTS releases, including backports, at https://jenkins.io/download/lts/  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-50999) Repository Branch DropDown timesout

2019-07-29 Thread bitwise...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Newman updated  JENKINS-50999  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50999  
 
 
  Repository Branch DropDown timesout   
 

  
 
 
 
 

 
Change By: 
 Liam Newman  
 
 
Status: 
 Fixed but Unreleased Resolved  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58667) NumberFormatException when parsing deploy url

2019-07-29 Thread robin.jans...@zf.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Robin Jansohn commented on  JENKINS-58667  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: NumberFormatException when parsing deploy url   
 

  
 
 
 
 

 
 Not sure I can follow. The introduced variable is a string and should be automatically serializable? Do you have an example where a new configuration option was introduced and did not require a manual refresh?  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58667) NumberFormatException when parsing deploy url

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-58667  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: NumberFormatException when parsing deploy url   
 

  
 
 
 
 

 
 

Is there any best practice to introduce new plugin configuration variables (with a default value) without needing to manually refresh freestyle job configurations?
 Yes. https://jenkins.io/doc/developer/persistence/  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58705) Change default working dir to /home/jenkins/agent

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vincent Latombe updated  JENKINS-58705  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58705  
 
 
  Change default working dir to /home/jenkins/agent   
 

  
 
 
 
 

 
Change By: 
 Vincent Latombe  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-50883) Blue ocean:GitHub Webhook is not created after new pipeline creation

2019-07-29 Thread vivek.pan...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated  JENKINS-50883  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fix released with Blueocean 1.18.0  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-50883  
 
 
  Blue ocean:GitHub Webhook is not created after new pipeline creation   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Status: 
 In Review 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190008.1524095011000.2953.1564410721027%40Atlassian.JIRA.

[JIRA] (JENKINS-56834) Build permission on agents is not working

2019-07-29 Thread svcj...@keitalbame.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nuno Costa edited a comment on  JENKINS-56834  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Build permission on agents is not working   
 

  
 
 
 
 

 
 I also saw this happening. If I change the [Project Default Build Authorization|https://wiki.jenkins-ci.org/display/JENKINS/Authorize+Project+plugin] from RUN AS USER WHO TRIGGERED BUILD to *RUN AS* *SYSTEM*, it runs without any issue. UPDATE: After doing some tweaking on Global and project roles permissions, I got it working with RUN AS USER WHO TRIGGERED BUILD, running the builds on Jenkins master.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58708) ECS Cluster field empty

2019-07-29 Thread stefan.and...@ddo.ai (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Stefan Anders updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58708  
 
 
  ECS Cluster field empty   
 

  
 
 
 
 

 
Change By: 
 Stefan Anders  
 
 
Environment: 
 Amazon Linux 2Jenkins 2.187  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58709) Nested pod templates inherit container of upper level pod

2019-07-29 Thread sergio.merin...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sergio Merino created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58709  
 
 
  Nested pod templates inherit container of upper level pod   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Carlos Sanchez  
 
 
Components: 
 kubernetes-plugin  
 
 
Created: 
 2019-07-29 14:11  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Sergio Merino  
 

  
 
 
 
 

 
 kubernetes plugin version: 1.17.2 When I run a podTemplate nested, it inherit the containers of the upper level podTemplate. It is a weird behaviour is better to explain it with an example Code: 

 

podTemplate(showRawYaml: true, label: "alpine1", cloud: "Build farm", containers: [
  containerTemplate(name: 'alpine', image: 'alpine', ttyEnabled: true, command: "cat")]) {
node ("alpine1") {
container('alpine') {
sh 'whoami'
podTemplate(showRawYaml: true, label: "golang", cloud: "Build farm", containers: [
  containerTemplate(name: 'golang', image: 'golang', ttyEnabled: true, command: "cat")]) {
  node ("golang") {
container('golang') {
  sh 'sleep 120'
}
  }
}
}
}
}  

   Expected 
 
alpine pod template containers: {jnlp} {alpine} 
golang pod template containers: {jnlp} {golang} 
 What I have: 
 
alpine pod template containers: {jnlp} {alpine} 
golang pod template

[JIRA] (JENKINS-58708) ECS Cluster field empty

2019-07-29 Thread stefan.and...@ddo.ai (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Stefan Anders created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58708  
 
 
  ECS Cluster field empty   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Jan Roehrich  
 
 
Components: 
 amazon-ecs-plugin  
 
 
Created: 
 2019-07-29 13:59  
 
 
Labels: 
 ECS CLUSTER plug-in configuration  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Stefan Anders  
 

  
 
 
 
 

 
 In Jenkins configuration I'm trying to add a new Cloud config for plugin amazon-ecs-plugin. I've entered Name, Amazon ECS Credentials, and region. The field ECS Cluster is empty. I can't see any of my 2 ECS clusters that I have configured in AWS.   Background information about AWS account The users are setup in the AWS main account, the ECS cluster can be setup in a different account using profiles with roles. aws ecs list-clusters doesn'ts how any clusters but aws ecs list-clusters --profile my_profile does.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-58705) Change default working dir to /home/jenkins/agent

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vincent Latombe started work on  JENKINS-58705  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Vincent Latombe  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58707) Rancher 2 Jenkins AWS CLI

2019-07-29 Thread elmajdoulizaka...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 zak maj updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58707  
 
 
  Rancher 2 Jenkins AWS CLI   
 

  
 
 
 
 

 
Change By: 
 zak maj  
 
 
Component/s: 
 cli  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-57561) Ant plugin exports empty home and then crashes with NPE

2019-07-29 Thread fjfernan...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Francisco Fernández assigned an issue to Armando Fernandez  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57561  
 
 
  Ant plugin exports empty home and then crashes with NPE   
 

  
 
 
 
 

 
Change By: 
 Francisco Fernández  
 
 
Assignee: 
 Francisco Fernández Armando Fernandez  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-57561) Ant plugin exports empty home and then crashes with NPE

2019-07-29 Thread fjfernan...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Francisco Fernández assigned an issue to Francisco Fernández  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57561  
 
 
  Ant plugin exports empty home and then crashes with NPE   
 

  
 
 
 
 

 
Change By: 
 Francisco Fernández  
 
 
Assignee: 
 Armando Fernandez Francisco Fernández  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58707) Rancher 2 Jenkins AWS CLI

2019-07-29 Thread elmajdoulizaka...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 zak maj created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58707  
 
 
  Rancher 2 Jenkins AWS CLI   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2019-07-29 13:20  
 
 
Environment: 
 Operating system : Centos 7, 64 bit (cluster of 3 nodes in the Rancher 2 environment).  Jenkins Version: 2.176.1.  Jenkins Installation: as a docker image in the Rancher 2 environment.  Reverse proxy: Apache version 2.4.6 (forward the request to the rancher cluster nodes).   
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 zak maj  
 

  
 
 
 
 

 
 Hi Everyone,   I'm not familiar with Jenkins (New user). My colleague got this error message:   Console Output:   Building in workspace /var/jenkins_home/workspace/ [] $ /bin/sh -xe /tmp/jenkins7583347576379589116.sh 
 
PROFILE=""> 
AWSCLI=/usr/bin/aws 
SLEEP=/usr/bin/sleep 
[ start = stop ] 
[ start = start ] 
/usr/bin/aws rds --profile -restart start-db-instance --db-instance-identifier -postgresql-awsuse2-live /tmp/jenkins7583347576369589116.sh: 18: /tmp/jenkins7583347577369589116.sh: /usr/bin/aws: not found Build step 'Execute shell' marked build as failure Finished: FAILURE 
   As i understood, the AWS CLI is not installed. Is there a plugin that i need to install or something ?   Please someone can help ?

[JIRA] (JENKINS-53810) Launch Agents fails with ERROR: null java.util.concurrent.CancellationException

2019-07-29 Thread kuisathave...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo commented on  JENKINS-53810  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Launch Agents fails with ERROR: null java.util.concurrent.CancellationException   
 

  
 
 
 
 

 
 yep, it is really helpful, I'm fixing the retry method on https://issues.jenkins-ci.org/browse/JENKINS-58589, and I've found the connection was not closed in some cases, so now it forces to close the connection before to retry again, also the timeout is passed to the connection and the weird global timeout disappear, now it'd be a timeout per connection.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58540) Console output of pipeline extra stars

2019-07-29 Thread karolgil...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Karol Gil commented on  JENKINS-58540  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Console output of pipeline extra stars   
 

  
 
 
 
 

 
 Jesse Glick we have a set of secrets assigned to pods depending on the environment which they are testing. If given service does not exist on certain environment secret for it is empty.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58540) Console output of pipeline extra stars

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-58540  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Console output of pipeline extra stars   
 

  
 
 
 
 

 
 As a matter of curiosity, how did you wind up with an empty secret to begin with?  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58706) Define API for secret masking in console output

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58706  
 
 
  Define API for secret masking in console output   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Carlos Sanchez  
 
 
Components: 
 credentials-binding-plugin, kubernetes-plugin  
 
 
Created: 
 2019-07-29 13:00  
 
 
Labels: 
 api  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Jesse Glick  
 

  
 
 
 
 

 
 credentials-binding should define an API for creating a console filter which masks a given set of secrets, usable by other plugins such as kubernetes.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-58540) Console output of pipeline extra stars

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-58540  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Console output of pipeline extra stars   
 

  
 
 
 
 

 
 Best done upstream in JENKINS-58706.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58706) Define API for secret masking in console output

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick assigned an issue to Jesse Glick  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58706  
 
 
  Define API for secret masking in console output   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Assignee: 
 Carlos Sanchez Jesse Glick  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58540) Console output of pipeline extra stars

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick started work on  JENKINS-58540  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58540) Console output of pipeline extra stars

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick assigned an issue to Karol Gil  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58540  
 
 
  Console output of pipeline extra stars   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Assignee: 
 Karol Gil  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58540) Console output of pipeline extra stars

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-58540  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58540  
 
 
  Console output of pipeline extra stars   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58705) Change default working dir to /home/jenkins/agent

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vincent Latombe assigned an issue to Vincent Latombe  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58705  
 
 
  Change default working dir to /home/jenkins/agent   
 

  
 
 
 
 

 
Change By: 
 Vincent Latombe  
 
 
Assignee: 
 Carlos Sanchez Vincent Latombe  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-58705) Change default working dir to /home/jenkins/agent

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vincent Latombe created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58705  
 
 
  Change default working dir to /home/jenkins/agent   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Carlos Sanchez  
 
 
Components: 
 kubernetes-plugin  
 
 
Created: 
 2019-07-29 12:24  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Vincent Latombe  
 

  
 
 
 
 

 
 The current default /home/jenkins causes some issues in some scenarios: When building a docker image with kaniko that is actually a jnlp agent image, since the specified workingDir is mounted as a volume in all containers in the pod, and it is also the home directory for the jenkins user, it prevents adding any file to /home/jenkins in the docker image. Changing the default working directory to /home/jenkins/agent should not have any downside except for users hardcoding stuff to it, while allowing this kind of scenarios in an easier way.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-58682) Global YAML Merge Strategy is not respected