date:20200312

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jared Biel edited a comment on  JENKINS-52761  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: withDockerRegistry fails to login with complex password   
 

  
 
 
 
 

 
 In case anyone runs across this, I've opened a  [ PR |[  ( https://github.com/jenkinsci/docker-commons-plugin/pull/86 ]] )  to solve this issue.  [ The artifact |  from that PR build can be manually installed in Jenkins until it's merged or fixed in some other way ( https://ci.jenkins.io/job/Plugins/job/docker-commons-plugin/job/PR-86/1/artifact/org/jenkins-ci/plugins/docker-commons/1.17-rc347.f3e1aa3e5799/docker-commons-1.17-rc347.f3e1aa3e5799.hpi ] from that PR build can be manually installed in Jenkins until it's merged or fixed in some other way ) .  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-53770) docker.withRegistry failed to login

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jared Biel commented on  JENKINS-53770  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: docker.withRegistry failed to login   
 

  
 
 
 
 

 
 In case anyone runs across this, I've opened a PR (https://github.com/jenkinsci/docker-commons-plugin/pull/86) to solve this issue. The artifact from that PR build can be manually installed in Jenkins until it's merged or fixed in some other way (https://ci.jenkins.io/job/Plugins/job/docker-commons-plugin/job/PR-86/1/artifact/org/jenkins-ci/plugins/docker-commons/1.17-rc347.f3e1aa3e5799/docker-commons-1.17-rc347.f3e1aa3e5799.hpi).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-52761) withDockerRegistry fails to login with complex password

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jared Biel commented on  JENKINS-52761  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: withDockerRegistry fails to login with complex password   
 

  
 
 
 
 

 
 In case anyone runs across this, I've opened a [PR|https://github.com/jenkinsci/docker-commons-plugin/pull/86] to solve this issue. The artifact from that PR build can be manually installed in Jenkins until it's merged or fixed in some other way.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-52761) withDockerRegistry fails to login with complex password

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jared Biel edited a comment on  JENKINS-52761  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: withDockerRegistry fails to login with complex password   
 

  
 
 
 
 

 
 In case anyone runs across this, I've opened a [PR|[https://github.com/jenkinsci/docker-commons-plugin/pull/86]] to solve this issue. [The artifact|https://ci.jenkins.io/job/Plugins/job/docker-commons-plugin/job/PR-86/1/artifact/org/jenkins-ci/plugins/docker-commons/1.17-rc347.f3e1aa3e5799/docker-commons-1.17-rc347.f3e1aa3e5799.hpi] from that PR build can be manually installed in Jenkins until it's merged or fixed in some other way.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)

2020-03-12 Thread charles.l.sm...@uscis.dhs.gov (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Charles Smith commented on  JENKINS-61356  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to connect to slave via Launch Agent mode(SSH)   
 

  
 
 
 
 

 
 Matt Sicker Ok. Just to confirm, you would like me to try downgrading the ssh-credential plugin to a previous version from the Plugin Manager section of my Jenkins' master?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)

2020-03-12 Thread msic...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Sicker commented on  JENKINS-61356  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to connect to slave via Launch Agent mode(SSH)   
 

  
 
 
 
 

 
 That's how I've used it, too. Could you try using an older version of the plugin to see if this is a regression? Previous releases are available here: https://updates.jenkins-ci.org/download/plugins/ssh-credentials/  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)

2020-03-12 Thread charles.l.sm...@uscis.dhs.gov (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Charles Smith edited a comment on  JENKINS-61356  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to connect to slave via Launch Agent mode(SSH)   
 

  
 
 
 
 

 
 [~jvz]My private key being used is a 4096 bit RSA key. The command that was used to create the keypair was:{code:java}ssh-keygen -t rsa –b 4096{code}I'm pretty sure RSA should be a supported format, do you know if there's a limit on the bit size? I'm able to SSH between systems from the shell with this same keypair. {code:java}$ file .ssh/id_rsa.ssh/id_rsa: ASCII text{code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)

2020-03-12 Thread charles.l.sm...@uscis.dhs.gov (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Charles Smith commented on  JENKINS-61356  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to connect to slave via Launch Agent mode(SSH)   
 

  
 
 
 
 

 
 Matt Sicker My private key being used is a 4096 bit RSA key. The command that was used to create the keypair was: 

 

ssh-keygen -t rsa –b 4096
 

 I'm pretty sure RSA should be a supported format, do you know if there's a limit on the bit size? I'm able to SSH between systems from the shell with this same keypair.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)

2020-03-12 Thread msic...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Sicker commented on  JENKINS-61356  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to connect to slave via Launch Agent mode(SSH)   
 

  
 
 
 
 

 
 So it looks like whatever key file format you're using isn't supported potentially? What encoding format are you using? I'm not very familiar with what's supported upstream at the moment besides what I've been using.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-45916) Path is not getting set correctly in pipeline when there is a variable present

2020-03-12 Thread ilaty...@yahoo.ca (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilguiz Latypov commented on  JENKINS-45916  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Path is not getting set correctly in pipeline when there is a variable present   
 

  
 
 
 
 

 
 Never mind, I see the magic recipe.  I still don't know the exact difference between "declarative" and "scripting", but I am mortal as well 

the PATH+EXTRA system works for Scripted Pipeline. If it does not work for Declarative, please file a separate RFE in pipeline-model-definition-plugin. Workaround would I guess be something like (untested) 

 

environment {
  STUFF = "${MTI_HOME}/linux:${MTI_HOME}/bin:${QUARTUS_HOME}/bin:${DCP_LOC}/bin"
}
// …
steps {
  withEnv(["PATH+EXTRA=$STUFF"]) {
sh 'whatever'
  }
}
 


 https://issues.jenkins-ci.org/browse/JENKINS-41339?focusedCommentId=357645&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-357645    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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 t

[JIRA] (JENKINS-45916) Path is not getting set correctly in pipeline when there is a variable present

2020-03-12 Thread ilaty...@yahoo.ca (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilguiz Latypov commented on  JENKINS-45916  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Path is not getting set correctly in pipeline when there is a variable present   
 

  
 
 
 
 

 
 What does that mean for the mere mortals?  Is "steps" or "sh" the thing to avoid?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)

2020-03-12 Thread charles.l.sm...@uscis.dhs.gov (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Charles Smith edited a comment on  JENKINS-61356  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to connect to slave via Launch Agent mode(SSH)   
 

  
 
 
 
 

 
 [~jvz]The test is failing after adding my private key to the _TrileadSSHPublicKeyAuthenticatorTest.java_ file. I'm not sure if anything else needs tp be added in order for the build to become successful or if there's a limitation on how big the private key must be? The private key that is found in this file is only 20 line long whereas my private key is 50 lines long.  When  I  run the test with the private key that ' s already found in the file the test build is successful. I' ve also attached the  test txt  log of the test  of my private key  to this ticket. Below is the output from the maven test:{code:java}$ mvn -e test -Dtest=TrileadSSHPublicKeyAuthenticatorTest [INFO] Error stacktraces are turned on.[INFO] Scanning for projects...[WARNING] The POM for org.jenkins-ci.tools:maven-hpi-plugin:jar:3.11 is missing, no dependency information available[WARNING] Failed to build parent project for org.jenkins-ci.plugins:ssh-credentials:hpi:1.18.2-SNAPSHOT[INFO][INFO] ---< org.jenkins-ci.plugins:ssh-credentials >---[INFO] Building SSH Credentials Plugin 1.18.2-SNAPSHOT[INFO] [ hpi ]-[INFO][INFO] --- maven-hpi-plugin:3.11:validate (default-validate) @ ssh-credentials ---[INFO][INFO] --- maven-enforcer-plugin:3.0.0-M3:display-info (display-info) @ ssh-credentials ---[INFO] Maven Version: 3.6.3[INFO] JDK Version: 1.8.0_242 normalized as: 1.8.0-242[INFO] OS Info: Arch: amd64 Family: unix Name: linux Version: 3.10.0-1062.12.1.el7.x86_64[INFO][INFO] --- maven-enforcer-plugin:3.0.0-M3:enforce (display-info) @ ssh-credentials ---[INFO] Adding ignore: module-info[INFO] Ignoring requireUpperBoundDeps in com.google.guava:guava[INFO][INFO] --- maven-localizer-plugin:1.26:generate (default) @ ssh-credentials ---[INFO][INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ ssh-credentials ---[INFO] Using 'UTF-8' encoding to copy filtered resources.[INFO] Copying 10 resources[INFO][INFO] --- flatten-maven-plugin:1.1.0:flatten (flatten) @ ssh-credentials ---[INFO] Generating flattened POM of project org.jenkins-ci.plugins:ssh-credentials:hpi:1.18.2-SNAPSHOT...[INFO][INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ ssh-credentials ---[INFO] Nothing to compile - all classes are up to date[INFO][INFO] --- access-modifier-checker:1.16:enforce (default-enforce) @ ssh-credentials ---[INFO][INFO] --- maven-hpi-plugin:3.11:insert-test (default-insert-test) @ ssh-credentials ---[INFO][INFO] --- gmaven-plugin:1.5-jenkins-3:generateTestStubs (test-in-groovy) @ ssh-credentials ---[INFO] No sources found for Java stub generation[INFO][INFO] --- maven-antrun-plugin:1.8:run (createTempDir) @ ssh-credentials ---[INFO] Executing tasksmain:[INFO] Executed tasks[INFO][INFO] --- maven-resources-plugin:3.1.0:testResources (default-testResources) @ ssh-credentials ---[INFO] Using 'UTF-8' encoding to copy filtered resources.[INFO] Copying 4 resources[INFO][INFO] --- maven-compiler-plugin:3.8.1:testCompile (default-testCompile) @ ssh-credentials ---[INFO] Nothing to compile - all classes are up to date[INFO][INFO] --- maven-hpi-plugin:3.11:test-hpl (default-test-hpl) @ ssh-credentials ---[INFO] Generating /home/clsmith4/test/ssh-credentials-plugin-master/target/test-classes/the.hpl[INFO][INFO] --- maven-hpi-plugin:3.11:resolve-test-dependencies (default-resolve-test-dependencies) @ ssh-credentials ---[INFO][INFO] --- gmaven-plugin:1.5-jenkins-3:testCompile (test-in-groovy) @ ssh-credentials ---[INFO] No s

[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)

2020-03-12 Thread charles.l.sm...@uscis.dhs.gov (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Charles Smith updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61356  
 
 
  Unable to connect to slave via Launch Agent mode(SSH)   
 

  
 
 
 
 

 
Change By: 
 Charles Smith  
 
 
Attachment: 
 com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSHPublicKeyAuthenticatorTest.txt.txt  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)

2020-03-12 Thread charles.l.sm...@uscis.dhs.gov (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Charles Smith edited a comment on  JENKINS-61356  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to connect to slave via Launch Agent mode(SSH)   
 

  
 
 
 
 

 
 [~jvz]The test is failing after adding my private key to the  TrileadSSHPublicKeyAuthenticatorTest _TrileadSSHPublicKeyAuthenticatorTest . java java_  file. I'm not sure if anything else needs tp be added in order for the build to become successful or if there's a limitation on how big the private key must be? The private key that is found in this file is only 20 line long whereas my private key is 50 lines long. I've also attached the log of the test to this ticket. Below is the output from the maven test:{code:java}$ mvn -e test -Dtest=TrileadSSHPublicKeyAuthenticatorTest [INFO] Error stacktraces are turned on.[INFO] Scanning for projects...[WARNING] The POM for org.jenkins-ci.tools:maven-hpi-plugin:jar:3.11 is missing, no dependency information available[WARNING] Failed to build parent project for org.jenkins-ci.plugins:ssh-credentials:hpi:1.18.2-SNAPSHOT[INFO][INFO] ---< org.jenkins-ci.plugins:ssh-credentials >---[INFO] Building SSH Credentials Plugin 1.18.2-SNAPSHOT[INFO] [ hpi ]-[INFO][INFO] --- maven-hpi-plugin:3.11:validate (default-validate) @ ssh-credentials ---[INFO][INFO] --- maven-enforcer-plugin:3.0.0-M3:display-info (display-info) @ ssh-credentials ---[INFO] Maven Version: 3.6.3[INFO] JDK Version: 1.8.0_242 normalized as: 1.8.0-242[INFO] OS Info: Arch: amd64 Family: unix Name: linux Version: 3.10.0-1062.12.1.el7.x86_64[INFO][INFO] --- maven-enforcer-plugin:3.0.0-M3:enforce (display-info) @ ssh-credentials ---[INFO] Adding ignore: module-info[INFO] Ignoring requireUpperBoundDeps in com.google.guava:guava[INFO][INFO] --- maven-localizer-plugin:1.26:generate (default) @ ssh-credentials ---[INFO][INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ ssh-credentials ---[INFO] Using 'UTF-8' encoding to copy filtered resources.[INFO] Copying 10 resources[INFO][INFO] --- flatten-maven-plugin:1.1.0:flatten (flatten) @ ssh-credentials ---[INFO] Generating flattened POM of project org.jenkins-ci.plugins:ssh-credentials:hpi:1.18.2-SNAPSHOT...[INFO][INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ ssh-credentials ---[INFO] Nothing to compile - all classes are up to date[INFO][INFO] --- access-modifier-checker:1.16:enforce (default-enforce) @ ssh-credentials ---[INFO][INFO] --- maven-hpi-plugin:3.11:insert-test (default-insert-test) @ ssh-credentials ---[INFO][INFO] --- gmaven-plugin:1.5-jenkins-3:generateTestStubs (test-in-groovy) @ ssh-credentials ---[INFO] No sources found for Java stub generation[INFO][INFO] --- maven-antrun-plugin:1.8:run (createTempDir) @ ssh-credentials ---[INFO] Executing tasksmain:[INFO] Executed tasks[INFO][INFO] --- maven-resources-plugin:3.1.0:testResources (default-testResources) @ ssh-credentials ---[INFO] Using 'UTF-8' encoding to copy filtered resources.[INFO] Copying 4 resources[INFO][INFO] --- maven-compiler-plugin:3.8.1:testCompile (default-testCompile) @ ssh-credentials ---[INFO] Nothing to compile - all classes are up to date[INFO][INFO] --- maven-hpi-plugin:3.11:test-hpl (default-test-hpl) @ ssh-credentials ---[INFO] Generating /home/clsmith4/test/ssh-credentials-plugin-master/target/test-classes/the.hpl[INFO][INFO] --- maven-hpi-plugin:3.11:resolve-test-dependencies (default-resolve-test-dependencies) @ ssh-credentials ---[INFO][INFO] --- gmaven-plugin:1.5-jenkins-3:testCompile (test-in-groovy) @ ssh-credentials ---[INFO] No sources found to compile[INFO][INFO] --- maven-surefire-plugin:3.0.0-M4:test (default-test) @ ss

[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)

2020-03-12 Thread charles.l.sm...@uscis.dhs.gov (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Charles Smith commented on  JENKINS-61356  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to connect to slave via Launch Agent mode(SSH)   
 

  
 
 
 
 

 
 Matt Sicker The test is failing after adding my private key to the TrileadSSHPublicKeyAuthenticatorTest.java file. I'm not sure if anything else needs tp be added in order for the build to become successful or if there's a limitation on how big the private key must be? The private key that is found in this file is only 20 line long whereas my private key is 50 lines long. I've also attached the log of the test to this ticket. Below is the output from the maven test: 

 

$ mvn -e test -Dtest=TrileadSSHPublicKeyAuthenticatorTest   [INFO] Error stacktraces are turned on.
[INFO] Scanning for projects...
[WARNING] The POM for org.jenkins-ci.tools:maven-hpi-plugin:jar:3.11 is missing, no dependency information available
[WARNING] Failed to build parent project for org.jenkins-ci.plugins:ssh-credentials:hpi:1.18.2-SNAPSHOT
[INFO]
[INFO] ---< org.jenkins-ci.plugins:ssh-credentials >---
[INFO] Building SSH Credentials Plugin 1.18.2-SNAPSHOT
[INFO] [ hpi ]-
[INFO]
[INFO] --- maven-hpi-plugin:3.11:validate (default-validate) @ ssh-credentials ---
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0-M3:display-info (display-info) @ ssh-credentials ---
[INFO] Maven Version: 3.6.3
[INFO] JDK Version: 1.8.0_242 normalized as: 1.8.0-242
[INFO] OS Info: Arch: amd64 Family: unix Name: linux Version: 3.10.0-1062.12.1.el7.x86_64
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0-M3:enforce (display-info) @ ssh-credentials ---
[INFO] Adding ignore: module-info
[INFO] Ignoring requireUpperBoundDeps in com.google.guava:guava
[INFO]
[INFO] --- maven-localizer-plugin:1.26:generate (default) @ ssh-credentials ---
[INFO]
[INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ ssh-credentials ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 10 resources
[INFO]
[INFO] --- flatten-maven-plugin:1.1.0:flatten (flatten) @ ssh-credentials ---
[INFO] Generating flattened POM of project org.jenkins-ci.plugins:ssh-credentials:hpi:1.18.2-SNAPSHOT...
[INFO]
[INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ ssh-credentials ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- access-modifier-checker:1.16:enforce (default-enforce) @ ssh-credentials ---
[INFO]
[INFO] --- maven-hpi-plugin:3.11:insert-test (default-insert-test) @ ssh-credentials ---
[INFO]
[INFO] --- gmaven-plugin:1.5-jenkins-3:generateTestStubs (test-in-groovy) @ ssh-credentials ---
[INFO] No sources found for Java stub generation
[INFO]
[INFO] --- maven-antrun-plugin:1.8:run (createTempDir) @ ssh-credentials ---
[INFO] Executing tasksmain:
[INFO] Executed tasks
[INFO]
[INFO] --- maven-resources-plugin:3.1.0:testResources (default-testResources) @ ssh-credentials ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 4 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.8.1:testCompile (default-testCompile) @ ssh-credentials ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-hpi-plugin:3.11:test-hpl (default-test-hpl) @ ssh-credentials ---
[INFO] Generating /home/clsmith4/test/ssh-credentials-plugin-master/target/test-classes/the.hpl
[INFO]
[INFO] --- maven-hpi-plugin:3.11:resolve-test-dependencies (default-resolve-test-dependencies) @ ssh

[JIRA] (JENKINS-61463) PipelineJob trigger deprecation, migration error

2020-03-12 Thread alan.l.spa...@microfocus.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alan Sparks created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61463  
 
 
  PipelineJob trigger deprecation, migration error   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Daniel Spilker  
 
 
Components: 
 job-dsl-plugin  
 
 
Created: 
 2020-03-12 19:20  
 
 
Environment: 
 Jenkins LTS 2.204.5, job-dsl-plugin 1.77, pipeline job 2.37  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Alan Sparks  
 

  
 
 
 
 

 
 Migration page for 1.77 deprecates pipeline trigger, so trying to migrate to new syntax.  Change my jobs from: triggers  {   cron('@daily') } To: properties { pipelineTriggers { triggers  { cron('@daily') }  } } DSL processing now fails with: 13:02:42 ERROR: (fullbyacct.groovy, line 8) No signature of method: javaposse.jobdsl.plugin.structs.DescribableListContext.cron() is applicable for argument types: (java.lang.String) values: [@daily] 13:02:42 Possible solutions: grep(), print(java.io.PrintWriter), print(java.lang.Object), grep(java.lang.Object), wait(), find() Am I missing something?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-61380) RequestorRecipientProvider returns wrong user when rebuild plugin is used

2020-03-12 Thread slide.o....@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl updated  JENKINS-61380  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61380  
 
 
  RequestorRecipientProvider returns wrong user when rebuild plugin is used   
 

  
 
 
 
 

 
Change By: 
 Alex Earl  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-61380) RequestorRecipientProvider returns wrong user when rebuild plugin is used

2020-03-12 Thread slide.o....@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl commented on  JENKINS-61380  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: RequestorRecipientProvider returns wrong user when rebuild plugin is used   
 

  
 
 
 
 

 
 This fix has been merged, but not released yet.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-61456) Allow Jenkins.MANAGE user to access "System Information"

Title: Message Title


 
 
 
 

 
 
 

 
   
 Esther Álvarez Feijoo assigned an issue to Esther Álvarez Feijoo  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61456  
 
 
  Allow Jenkins.MANAGE user to access "System Information"   
 

  
 
 
 
 

 
Change By: 
 Esther Álvarez Feijoo  
 
 
Assignee: 
 Esther Álvarez Feijoo  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-61456) Allow Jenkins.MANAGE user to access "System Information"

Title: Message Title


 
 
 
 

 
 
 

 
   
 Esther Álvarez Feijoo started work on  JENKINS-61456  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Esther Álvarez Feijoo  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-61456) Allow Jenkins.MANAGE user to access "System Information"

Title: Message Title


 
 
 
 

 
 
 

 
   
 Esther Álvarez Feijoo updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61456  
 
 
  Allow Jenkins.MANAGE user to access "System Information"   
 

  
 
 
 
 

 
Change By: 
 Esther Álvarez Feijoo  
 

  
 
 
 
 

 
 Jenkins.MANAGE permission allows accessing "System Information"Thread dumps and environment variables should still only be shown to a user with Jenkins.ADMINISTER  because they can contain sensitive data. One common example is running Jenkins in a container, where the common way of providing secrets is by using environment variables.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-61429) Unable to move/reorder steps within a job

2020-03-12 Thread fqueir...@cloudbees.com (JIRA)

Title: Message Title

Félix Queiruga Balado commented on JENKINS-61429

Re: Unable to move/reorder steps within a job

I have a better idea of what caused this regression. I’ll try to explain it. The war/src/main/js/config-scrollspy.js JS entry point contains some fixes for drag & drop behaviour for the job and folders form forms. Fixes are applied on a proxied Behaviour.specify call on the tabbar.js file it imports. These fixes are initialized by a function wrapped within a $() jquery block .(https://github.com/jenkinsci/jenkins/blob/23ab517cb4de3edd80e07b77d332d47eb9049276/war/src/main/js/config-scrollspy.js#L29). Before 2.217, the code would run in the following order:

config-scrollspy.js loads and it’s executed.
The initialization code runs immediatly and the Behaviour.specify call registers the fixes (https://github.com/jenkinsci/jenkins/blob/1ca9f6e8d649be88adb364da5dc2533706a8bfa5/war/src/main/js/widgets/config/tabbar.js#L13)
The window.onload event handler is triggered, and runs all pieces of code set up via Behaviour.specify
On 2.217+:

config-scrollspy.js loads and it’s script-level code is executed, but the initialization code does not run.
The window.onload event handler is triggered, and runs all pieces of code set up via Behaviour.specify. Because the intialization code was not yet run on the config-scrollspy.js file, drag & drop widgets existing on the page are not initialized.
The initialization code for the drag & drop fixes is run. Because it came after the _window.onload _event, it will only apply to draggable widgets added after this point (i.e. recently added and unsaved steps).
Basically, jQuery will wait until window.onload event to run the subscription code on 2.217+. The fix consists on moving the Behaviour.specify call on the tabbar.js file to be run when the script loads, so that it happens before the window.onload event. I don’t think it will negatively impact any other part of the app / plugin.

Add Comment

[JIRA] (JENKINS-60779) Pipeline Build Step: Remove Message converting string Parameter to Extensible Choice Parameter

2020-03-12 Thread dnusb...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum commented on  JENKINS-60779  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline Build Step: Remove Message converting string Parameter to Extensible Choice Parameter   
 

  
 
 
 
 

 
 I added the the parameter definitions for Active Choices Plugin to the whitelist. Paul Thevenot Max Matissek If either of you is able test the proposed fix, here is a prerelease build of the plugin that includes the fix that you could install on your Jenkins instance.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-60779) Pipeline Build Step: Remove Message converting string Parameter to Extensible Choice Parameter

2020-03-12 Thread dnusb...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum updated  JENKINS-60779  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60779  
 
 
  Pipeline Build Step: Remove Message converting string Parameter to Extensible Choice Parameter   
 

  
 
 
 
 

 
Change By: 
 Devin Nusbaum  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-60779) Pipeline Build Step: Remove Message converting string Parameter to Extensible Choice Parameter

2020-03-12 Thread dnusb...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum started work on  JENKINS-60779  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Devin Nusbaum  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-61462) Jenkinsfile parameter default values not evaluted on first-run when read from scm

2020-03-12 Thread jerrywil...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 jerry wiltse created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61462  
 
 
  Jenkinsfile parameter default values not evaluted on first-run when read from scm   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 pipeline  
 
 
Created: 
 2020-03-12 16:50  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 jerry wiltse  
 

  
 
 
 
 

 
 As of... CloudBees Jenkins Distribution 2.176.2.3-rolling To reproduce 
 
Create a jenkinsfile on SCM 
Give it a parameter of any type (for example, a string named "greeting") 
Give it some default value of "Hello World" 
Add a step to echo the value of "greeting" 
Add a new jenkins job: type=pipeline 
Choose "pipeline script from scm" 
Point to the Jenkinsfile you added in step 1 
Click "build" button 
 
Of note, "Build with parameters isn't an option because Jenkins doesn't know that the job has a parameter when it's added this way". I believe this is the root of the issue. 
  
 So, the first run of the job should print "null" rather than "Hello World" because using the "build" button seems to set all the parameters to "null" instead of using their default values.  After the first run, the job will have a "Build with parameters" button, so the issue will never occur again. I'm not sure what a sensible approach is to resol

[JIRA] (JENKINS-61462) Jenkinsfile parameter default values not evaluted on first-run when read from scm

2020-03-12 Thread jerrywil...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 jerry wiltse created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61462  
 
 
  Jenkinsfile parameter default values not evaluted on first-run when read from scm   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 pipeline  
 
 
Created: 
 2020-03-12 16:50  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 jerry wiltse  
 

  
 
 
 
 

 
 As of... CloudBees Jenkins Distribution 2.176.2.3-rolling To reproduce 
 
Create a jenkinsfile on SCM 
Give it a parameter of any type (for example, a string named "greeting") 
Give it some default value of "Hello World" 
Add a step to echo the value of "greeting" 
Add a new jenkins job: type=pipeline 
Choose "pipeline script from scm" 
Point to the Jenkinsfile you added in step 1 
Click "build" button 
 
Of note, "Build with parameters isn't an option because Jenkins doesn't know that the job has a parameter when it's added this way". I believe this is the root of the issue. 
  
 So, the first run of the job should print "null" rather than "Hello World" because using the "build" button seems to set all the parameters to "null" instead of using their default values.  After the first run, the job will have a "Build with parameters" button, so the issue will never occur again. I'm not sure what a sensible approach is to resol

[JIRA] (JENKINS-61461) Logger suggestions don't show all results as you type

2020-03-12 Thread timbla...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tim Black created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61461  
 
 
  Logger suggestions don't show all results as you type   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Praqma Support  
 
 
Components: 
 logging-plugin  
 
 
Created: 
 2020-03-12 16:13  
 
 
Environment: 
 Deban 9/Stretch   Jenkins ver. 2.190.3   openjdk version "1.8.0_232"  OpenJDK Runtime Environment (build 1.8.0_232-8u232-b09-1~deb9u1-b09)  OpenJDK 64-Bit Server VM (build 25.232-b09, mixed mode)   Plugin Versions:  OWASP Markup Formatter Plugin (antisamy-markup-formatter): 1.6  Pipeline: Nodes and Processes (workflow-durable-task-step): 2.35  ruby-runtime (ruby-runtime): 0.12  Email Extension Plugin (email-ext): 2.68  CVS Plug-in (cvs): 2.14  Maven Integration plugin (maven-plugin): 3.4  Git Pipeline for Blue Ocean (blueocean-git-pipeline): 1.21.0  Run Condition Plugin (run-condition): 1.2  Pipeline: Stage Step (pipeline-stage-step): 2.3  Ant Plugin (ant): 1.10  LDAP Plugin (ldap): 1.21  Mercurial plugin (mercurial): 2.8  Pipeline: Groovy (workflow-cps): 2.80  REST API for Blue Ocean (blueocean-rest): 1.21.0  Git client plugin (git-client): 3.2.1  i18n for Blue Ocean (blueocean-i18n): 1.21.0  PAM Authentication plugin (pam-auth): 1.6  Pipeline: Multibranch (workflow-multibranch): 2.21  Handy Uri Templates 2.x API Plugin (handy-uri-templates-2-api): 2.1.8-1.0  Bitbucket Pipeline for Blue Ocean (blueocean-bitbucket-pipeline): 1.21.0  Extended Choice Parameter Plug-In (extended-choice-parameter): 0.78  GitHub plugin (github): 1.29.5  Server Sent Events (SSE) Gateway Plugin (sse-gateway): 1.20  Office 365 Connector (Office-365-Connector): 4.12.3  Favorite (favorite): 2.3.2  Pipeline: Shared Groovy Libraries (workflow-cps-global-lib): 2.15  Pipeline SCM API for Blue Ocean (blueocean-pipeline-scm-api): 1.21.0  Blue Ocean Pipeline Editor (blueocean-pipeline-editor): 1.21.0  Matrix Authorization Strategy Plugin (matrix-auth): 2.5  Branch API Plugin (branch-api): 2.5.5  Docker Pipeline (docker-workflow): 1.22  categorized-view (categorized-view): 1.10  bouncycastle API Plugin (bouncycastle-api): 2.17  Pipeline Utility Steps (pipeline-utility-steps): 2.5.0  Command Agent Launcher Plugin (command-launcher): 1.4  Icon Shim Plugin (icon-shim): 2.0.3  JUnit Plugin (junit): 1.28  Config File Provider Plugin (config-file-provider): 3.6.2  Matrix Project Plugin (matrix-project): 1.14  Pub-Sub "light" Bus (pubsub-light): 1.13  Plugin Usage - Plugin (plugin-usage-plugin): 1.0  Pipeline implementation for Blue Ocean (blueocean-pipeline-api-impl): 1.21.0  Dashboard for Blue Ocean (blueocean-dashboard): 1.21.0  SSH Credentials Plugin (ssh-credentials): 1.18  Pipeline: Declarative (pipeline-model

[JIRA] (JENKINS-61455) Allow Jenkins.MANAGE user to access "About Jenkins"

Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonio Muñiz updated  JENKINS-61455  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61455  
 
 
  Allow Jenkins.MANAGE user to access "About Jenkins"   
 

  
 
 
 
 

 
Change By: 
 Antonio Muñiz  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-61455) Allow Jenkins.MANAGE user to access "About Jenkins"

Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonio Muñiz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61455  
 
 
  Allow Jenkins.MANAGE user to access "About Jenkins"   
 

  
 
 
 
 

 
Change By: 
 Antonio Muñiz  
 

  
 
 
 
 

 
 Users with Jenkins.MANAGE permission  allows  should be able  to access "About Jenkins"  management link.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-61452) Illegal base64 character in FileLogStorage$1.writeHtmlTo(FileLogStorage.java:203)

2020-03-12 Thread xiao...@outlook.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ted Xiao commented on  JENKINS-61452  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Illegal base64 character in FileLogStorage$1.writeHtmlTo(FileLogStorage.java:203)   
 

  
 
 
 
 

 
 The console page will go back to normal if the job completes, either normally or aborted. probably a caching bug in the FileLogStorage  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-61460) Subversion UpdateUpdater fails to update with corrupted WC database

2020-03-12 Thread kuisathave...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61460  
 
 
  Subversion UpdateUpdater fails to update with corrupted WC database   
 

  
 
 
 
 

 
Change By: 
 Ivan Fernandez Calvo  
 
 
Assignee: 
 Ivan Fernandez Calvo  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-61460) Subversion UpdateUpdater fails to update with corrupted WC database

2020-03-12 Thread advor...@vasco.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexander Dvorsky created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61460  
 
 
  Subversion UpdateUpdater fails to update with corrupted WC database   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Ivan Fernandez Calvo  
 
 
Components: 
 subversion-plugin  
 
 
Created: 
 2020-03-12 15:23  
 
 
Environment: 
 java.version 1.8.0_231  Windows 10  Subversion Plug-in 2.13.1  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Alexander Dvorsky  
 

  
 
 
 
 

 
 According to what I have read in the code UpdateUpdater should fallback to CheckoutUpdater in case of issues, which it does. But in the first analysis it seems the code checking the state of the working copy locks the WC database in case of the new working copy format (.svn/wc.db) A workaround is to use the CheckoutUpdater (verified) The issue looks as follows (for full stack see attachment): 

 

Also:   java.nio.file.FileSystemException: C:\Users\mwa\.jenkins\workspace\subversion\.svn\wc.db: The process cannot access the file because it is being used by another process.

at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)
at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)
at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source)
at java.nio.file.Files.deleteIfExists(Unknown Source)
at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:237) 

 This can be replicated with this short Jenkinsfile script

[JIRA] (JENKINS-54592) Sorting arrows show in wrong direction in dashboard

2020-03-12 Thread b.mich...@gmx.de (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Björn Michael commented on  JENKINS-54592  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Sorting arrows show in wrong direction in dashboard   
 

  
 
 
 
 

 
 Is there any chance that this issue will be addressed?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-61459) In progress builds report failure when orphaned

2020-03-12 Thread ni...@carallon.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Bulleid created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61459  
 
 
  In progress builds report failure when orphaned   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 branch-api-plugin  
 
 
Created: 
 2020-03-12 14:33  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Nick Bulleid  
 

  
 
 
 
 

 
 If a ref disappears, it's job will become disabled, however any running builds of this job will not be aborted. This can result in the build trying to checkout code from a deleted ref which, most likely, will result in a failure. This becomes an issue when the failure of a build gets reported back to a code review system eg Gerrit. It seems logical that an orphaned job should also have any builds aborted as they cannot succeed and will result in an incorrect failure case.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-22236) LinkageError when using Maven 3.1.1 and 3.2.1 with Jenkins 1.555

2020-03-12 Thread mark.earl.wa...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite closed an issue as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Too old a report and too old a version for investigation. Won't fix.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-22236  
 
 
  LinkageError when using Maven 3.1.1 and 3.2.1 with Jenkins 1.555   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Won't Fix  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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 d

[JIRA] (JENKINS-44741) Build User Vars should not require node

2020-03-12 Thread su...@sunilkchopra.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sunil Chopra commented on  JENKINS-44741  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Build User Vars should not require node   
 

  
 
 
 
 

 
 Agree.  This not being a feature is very puzzling and makes the plugin hard to use.  The fact that the plugin is necessary at all is weird.  The fact that the plugin then goes further in requiring a node makes the situation super frustrating. For what it's worth, I was able to put together a one-ish line of Groovy that effectively "liberates" the needed information.  But this is highly confusing and increases technical debt in our pipelines.  

 

node {
  wrap([$class: 'BuildUser']) { env.BUILD_USER_ID = env.BUILD_USER_ID  } 
}

echo env.BUILD_USER_ID 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-61439) Independent git operations share singular JVM lock

2020-03-12 Thread mark.earl.wa...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61439  
 
 
  Independent git operations share singular JVM lock   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Assignee: 
 Mark Waite  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-61457) Allow Jenkins.MANAGE user to configure "Enable Anonymous Usage Statistics"

Title: Message Title


 
 
 
 

 
 
 

 
   
 Esther Álvarez Feijoo started work on  JENKINS-61457  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Esther Álvarez Feijoo  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-61457) Allow Jenkins.MANAGE user to configure "Enable Anonymous Usage Statistics"

Title: Message Title


 
 
 
 

 
 
 

 
   
 Esther Álvarez Feijoo assigned an issue to Esther Álvarez Feijoo  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61457  
 
 
  Allow Jenkins.MANAGE user to configure "Enable Anonymous Usage Statistics"   
 

  
 
 
 
 

 
Change By: 
 Esther Álvarez Feijoo  
 
 
Assignee: 
 Esther Álvarez Feijoo  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-56759) Unexpected executor death prevents builds

2020-03-12 Thread ronny.borch...@muehlbauer.de (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert edited a comment on  JENKINS-56759  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unexpected executor death prevents builds   
 

  
 
 
 
 

 
 I We  got this too  today. We are using several axis. We are using no slave. We are on Windows 2012 R2 and jenkins version is 2.225 ,  all plugins are up  but we was copying a project  to  date  wrong location .  How could I support?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-61455) Allow Jenkins.MANAGE user to access "About Jenkins"

Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonio Muñiz assigned an issue to Antonio Muñiz  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61455  
 
 
  Allow Jenkins.MANAGE user to access "About Jenkins"   
 

  
 
 
 
 

 
Change By: 
 Antonio Muñiz  
 
 
Assignee: 
 Antonio Muñiz  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-61455) Allow Jenkins.MANAGE user to access "About Jenkins"

Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonio Muñiz started work on  JENKINS-61455  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Antonio Muñiz  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-46988) String.eachLine only reads first line

2020-03-12 Thread piotr.b.kozuchow...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Piotr Kożuchowski commented on  JENKINS-46988  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: String.eachLine only reads first line   
 

  
 
 
 
 

 
 I've just stumbled over this as well.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-61458) Allow Jenkins.MANAGE user to access "Reload Configuration From Disk"

Title: Message Title


 
 
 
 

 
 
 

 
   
 Esther Álvarez Feijoo created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61458  
 
 
  Allow Jenkins.MANAGE user to access "Reload Configuration From Disk"   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2020-03-12 12:36  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Esther Álvarez Feijoo  
 

  
 
 
 
 

 
 Jenkins.MANAGE permission allows accessing and running "Reload Configuration From Disk"  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)

[JIRA] (JENKINS-61457) Allow Jenkins.MANAGE user to configure "Enable Anonymous Usage Statistics"

Title: Message Title


 
 
 
 

 
 
 

 
   
 Esther Álvarez Feijoo created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61457  
 
 
  Allow Jenkins.MANAGE user to configure "Enable Anonymous Usage Statistics"   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2020-03-12 12:35  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Esther Álvarez Feijoo  
 

  
 
 
 
 

 
 Jenkins.MANAGE permission allows configuring "Enable Anonymous Usage Statistics"  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)

[JIRA] (JENKINS-56759) Unexpected executor death prevents builds

2020-03-12 Thread ronny.borch...@muehlbauer.de (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert edited a comment on  JENKINS-56759  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unexpected executor death prevents builds   
 

  
 
 
 
 

 
 I got this too today. We are using several axis. We are using no slave. We are on Windows 2012 R2  and jenkins version is 2 . 225, all plugins are up to date.  How could I support?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-61456) Allow Jenkins.MANAGE user to access "System Information"

Title: Message Title


 
 
 
 

 
 
 

 
   
 Esther Álvarez Feijoo created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61456  
 
 
  Allow Jenkins.MANAGE user to access "System Information"   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2020-03-12 12:25  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Esther Álvarez Feijoo  
 

  
 
 
 
 

 
 Jenkins.MANAGE permission allows accessing "System Information" Thread dumps and environment variables should still only be shown to a user with Jenkins.ADMINISTER  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13

[JIRA] (JENKINS-56759) Unexpected executor death prevents builds

2020-03-12 Thread ronny.borch...@muehlbauer.de (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert commented on  JENKINS-56759  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unexpected executor death prevents builds   
 

  
 
 
 
 

 
 I got this too today. We are using several axis. We are using no slave. We are on Windows 2012 R2. How could I support?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-61455) Allow Jenkins.MANAGE user to access "About Jenkins"

Title: Message Title


 
 
 
 

 
 
 

 
   
 Esther Álvarez Feijoo created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61455  
 
 
  Allow Jenkins.MANAGE user to access "About Jenkins"   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2020-03-12 12:20  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Esther Álvarez Feijoo  
 

  
 
 
 
 

 
 Jenkins.MANAGE permission allows to access "About Jenkins"  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)

[JIRA] (JENKINS-61454) (Jenkins.MANAGE) Be able to configure Jenkins without ADMINISTER

Title: Message Title


 
 
 
 

 
 
 

 
   
 Esther Álvarez Feijoo started work on  JENKINS-61454  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Esther Álvarez Feijoo  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-61454) (Jenkins.MANAGE) Be able to configure Jenkins without ADMINISTER

Title: Message Title


 
 
 
 

 
 
 

 
   
 Esther Álvarez Feijoo updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61454  
 
 
  (Jenkins.MANAGE) Be able to configure Jenkins without ADMINISTER   
 

  
 
 
 
 

 
Change By: 
 Esther Álvarez Feijoo  
 
 
Summary: 
 Add a (  Jenkins.MANAGE  permission to be ) Be  able to configure Jenkins without ADMINISTER  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-61454) (Jenkins.MANAGE) Be able to configure Jenkins without ADMINISTER

Title: Message Title


 
 
 
 

 
 
 

 
   
 Esther Álvarez Feijoo updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61454  
 
 
  (Jenkins.MANAGE) Be able to configure Jenkins without ADMINISTER   
 

  
 
 
 
 

 
Change By: 
 Esther Álvarez Feijoo  
 
 
Summary: 
 Add a (  Jenkins.MANAGE  permission to be ) Be  able to configure Jenkins without ADMINISTER  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-61454) Add a Jenkins.MANAGE permission to be able to configure Jenkins without ADMINISTER