[JIRA] (JENKINS-55553) Active flag in jenkins build engine gets de-activated

2019-01-11 Thread makambindu.2...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 hima bindu created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-3  
 
 
  Active flag in jenkins build engine gets de-activated   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 teamconcert-plugin  
 
 
Created: 
 2019-01-12 06:57  
 
 
Priority: 
  Major  
 
 
Reporter: 
 hima bindu  
 

  
 
 
 
 

 
 Hi, we recently upgrade jenkins to 2.156. We have a jenkins build engine which is connecting to RTC through a proxy server. TheActive flag gets de-activated intermittently. Please do let us know what the issue is. It used to be fine before upgrade. Are there any changes needed to have it enabled all the time.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 
  

[JIRA] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted

2019-01-11 Thread sbc8...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dan Wang edited a comment on  JENKINS-29616  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted   
 

  
 
 
 
 

 
 I also faced this issue after I update the jenkins to newest version but now is resolved. I follow [~junior1024] 's last update solution, and works now. # Remove slave workspace directory # Download the launcher (slave-agent.jnlp) on your jenkins slave page.  # Use task-scheduler to process slave-agent.   # Enjoy it!     
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted

2019-01-11 Thread sbc8...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dan Wang commented on  JENKINS-29616  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted   
 

  
 
 
 
 

 
 I also faced this issue after I update the jenkins to newest version but now is resolved.   I follow Peter Sosnowski 's last update solution, and works now. 
 
Remove slave workspace directory 
Download the launcher (slave-agent.jnlp) on your jenkins slave page. 
      
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55552) NullPointerException when using Credentials Binding Plugin

2019-01-11 Thread cowlina...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 p cowlinator updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-2  
 
 
  NullPointerException when using Credentials Binding Plugin   
 

  
 
 
 
 

 
Change By: 
 p cowlinator  
 

  
 
 
 
 

 
 A NullPointerException with no stacktrace is experienced when trying to run the following pipeline:{code:java}pipeline {agent anystages {stage('stage usernameColonPassword') {steps {sh 'echo usernameColonPassword 1'withCredentials([usernameColonPassword(credentialsId: 'mysecret', variable: 'SECRET')]) {sh 'echo usernameColonPassword 2' }}}stage('stage usernamePassword') {steps {sh 'echo usernamePassword 3'withCredentials([usernamePassword(credentialsId: 'mysecret', passwordVariable: 'SECRET2')]) {sh 'echo usernamePassword 4' }}}}}{code}where "mysecret" is a credential with it's "kind" being "username and password".This exception causes the job to fail. Specifically, `usernameColonPassword` succeeds, while `usernamePassword` fails; `usernamePassword 4` is never printed to the log. This was the first time I have tried to run this script, so I have never observed this succeeding; for all I know, it has always failed. My workaround options are bad:  either parse the password out of the `user:pass` format, or abandon the plugin.  UPDATE: as mentioned in the comments, there is a better workaround.  This ticket is now for removing or documenting the requirement for all arguments to be used, and creating a useful error message.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 
   

[JIRA] (JENKINS-55552) NullPointerException when using Credentials Binding Plugin

2019-01-11 Thread cowlina...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 p cowlinator updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-2  
 
 
  NullPointerException when using Credentials Binding Plugin   
 

  
 
 
 
 

 
Change By: 
 p cowlinator  
 
 
Priority: 
 Major Minor  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-42950) credentials-binding-plugin not masking secret text when it includes a single quote

2019-01-11 Thread cowlina...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 p cowlinator edited a comment on  JENKINS-42950  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: credentials-binding-plugin not masking secret text when it includes a single quote
 

  
 
 
 
 

 
 I get this problem with the following environment:Jenkins server: runs on `jenkins/jenkins:lts` docker image (image id: 5907903170ad), with Jenkins version 2.150.1.  Credentials-binding-plugin version: 1.17.  Agent: runs on a Alpine Linux 3.8 docker imageWhen running the following pipeline:{code:java}pipeline {agent { docker { image 'alpine:3.8' } }stages {stage('run_for_ranapas') {steps {withCredentials([usernamePassword(credentialsId: 'quote_pw', usernameVariable: 'USER', passwordVariable: 'PASS')]) {sh ''' echo $USER $PASS'''}}}}}{code}Where `quote_pw` is a global scope, global domain credential who's  "  ` kind " `  is  "  ` username and password " ` , and who's values are: username: `username7`, password: `password'7`.The result is {code:java}[Pipeline] withCredentials[Pipeline] {[Pipeline] sh+ echo  'password'"'"'7' {code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-42950) credentials-binding-plugin not masking secret text when it includes a single quote

2019-01-11 Thread cowlina...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 p cowlinator edited a comment on  JENKINS-42950  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: credentials-binding-plugin not masking secret text when it includes a single quote
 

  
 
 
 
 

 
 I get this problem with the following environment:Jenkins server: runs on  `  jenkins/jenkins:lts `  docker image (image id: 5907903170ad), with Jenkins version 2.150.1.  Credentials-binding-plugin version: 1.17.  Agent: runs on a Alpine Linux 3.8 docker imageWhen running the following pipeline:{code:java}pipeline {agent { docker { image 'alpine:3.8' } }stages {stage('run_for_ranapas') {steps {withCredentials([usernamePassword(credentialsId: 'quote_pw', usernameVariable: 'USER', passwordVariable: 'PASS')]) {sh ''' echo $USER $PASS'''}}}}}{code}Where  "  ` quote_pw " `  is a global scope, global domain credential who's "kind" is "username and password", and who's values are: username: `username7`, password: `password'7`.The result is {code:java}[Pipeline] withCredentials[Pipeline] {[Pipeline] sh+ echo  'password'"'"'7' {code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-42950) credentials-binding-plugin not masking secret text when it includes a single quote

2019-01-11 Thread cowlina...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 p cowlinator commented on  JENKINS-42950  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: credentials-binding-plugin not masking secret text when it includes a single quote
 

  
 
 
 
 

 
 I get this problem with the following environment: Jenkins server: runs on jenkins/jenkins:lts docker image (image id: 5907903170ad), with Jenkins version 2.150.1.  Credentials-binding-plugin version: 1.17.  Agent: runs on the server node.  When running the following pipeline: 

 

pipeline {
agent { docker { image 'alpine:3.8' } }
stages {
stage('run_for_ranapas') {
steps {
withCredentials([usernamePassword(credentialsId: 'quote_pw', usernameVariable: 'USER', passwordVariable: 'PASS')]) {
sh '''
echo $USER $PASS
'''
}
}
}
}
}

 

 Where "quote_pw" is a global scope, global domain credential who's "kind" is "username and password", and who's values are: username: `username7`, password: `password'7`. The result is  

 

[Pipeline] withCredentials
[Pipeline] {
[Pipeline] sh
+ echo  'password'"'"'7'
 
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more 

[JIRA] (JENKINS-42950) credentials-binding-plugin not masking secret text when it includes a single quote

2019-01-11 Thread cowlina...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 p cowlinator edited a comment on  JENKINS-42950  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: credentials-binding-plugin not masking secret text when it includes a single quote
 

  
 
 
 
 

 
 I get this problem with the following environment:Jenkins server: runs on jenkins/jenkins:lts docker image (image id: 5907903170ad), with Jenkins version 2.150.1. Credentials-binding-plugin version: 1.17. Agent: runs on  the server node  a Alpine Linux 3 .   8 docker image When running the following pipeline:{code:java}pipeline {agent { docker { image 'alpine:3.8' } }stages {stage('run_for_ranapas') {steps {withCredentials([usernamePassword(credentialsId: 'quote_pw', usernameVariable: 'USER', passwordVariable: 'PASS')]) {sh ''' echo $USER $PASS'''}}}}}{code}Where "quote_pw" is a global scope, global domain credential who's "kind" is "username and password", and who's values are: username: `username7`, password: `password'7`.The result is {code:java}[Pipeline] withCredentials[Pipeline] {[Pipeline] sh+ echo  'password'"'"'7' {code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55552) NullPointerException when using Credentials Binding Plugin

2019-01-11 Thread cowlina...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 p cowlinator commented on  JENKINS-2  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: NullPointerException when using Credentials Binding Plugin   
 

  
 
 
 
 

 
 I have found a resolution for this issue. By including the "usernameVariable" argument, the null reference exception goes away: 

 

withCredentials([usernamePassword(credentialsId: 'mysecret', passwordVariable: 'SECRET2', usernameVariable: 'USELESS')]) {
 

 Please no longer require arguments that may not be useful to the user; or, document that all arguments are required and print a more helpful error when they are not provided.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-42950) credentials-binding-plugin not masking secret text when it includes a single quote

2019-01-11 Thread cowlina...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 p cowlinator updated  JENKINS-42950  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42950  
 
 
  credentials-binding-plugin not masking secret text when it includes a single quote
 

  
 
 
 
 

 
Change By: 
 p cowlinator  
 
 
Status: 
 Resolved In 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-42950) credentials-binding-plugin not masking secret text when it includes a single quote

2019-01-11 Thread cowlina...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 p cowlinator commented on  JENKINS-42950  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: credentials-binding-plugin not masking secret text when it includes a single quote
 

  
 
 
 
 

 
 I am able to reproduce this issue.  I will post more details in the next comment.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55552) NullPointerException when using Credentials Binding Plugin

2019-01-11 Thread cowlina...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 p cowlinator created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-2  
 
 
  NullPointerException when using Credentials Binding Plugin   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 credentials-binding-plugin  
 
 
Created: 
 2019-01-11 23:33  
 
 
Environment: 
 Jenkins server: runs on jenkins/jenkins:lts docker image (image id: 5907903170ad), with Jenkins version 2.150.1.  Credentials-binding-plugin version: 1.17.  Agent: runs on the server node.   
 
 
Priority: 
  Major  
 
 
Reporter: 
 p cowlinator  
 

  
 
 
 
 

 
 A NullPointerException with no stacktrace is experienced when trying to run the following pipeline: 

 

pipeline {
agent any
stages {
stage('stage usernameColonPassword') {
steps {
sh 'echo usernameColonPassword 1'
withCredentials([usernameColonPassword(credentialsId: 'mysecret', variable: 'SECRET')]) {
sh 'echo usernameColonPassword 2' 
}
}
}
stage('stage usernamePassword') {
steps {
sh 'echo usernamePassword 3'
withCredentials([usernamePassword(credentialsId: 'mysecret', passwordVariable: 'SECRET2')]) {
sh 'echo usernamePassword 4' 
}
}
}
}
}

 

 where "mysecret" is a credential with it's "kind" being "username and password". This exception causes the job to fail.   Specifically, `usernameColonPassword` succeeds, while `usernamePassword` fails; `usernamePassword 4` is never 

[JIRA] (JENKINS-44609) Docker inspect failing on named multi-stage builds

2019-01-11 Thread ste...@weathers.me (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Steven Weathers commented on  JENKINS-44609  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Docker inspect failing on named multi-stage builds
 

  
 
 
 
 

 
 Jesse Glick that's one thing I tried but makes things like deploying to registry more of a hassle.  Overall I've since abandoned trying to use Jenkins and have gone with another CI that worked flawlessly from the start since it was docker oriented.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-48556) timestamps() randomly not recognized as a valid option

2019-01-11 Thread joshwoodc...@beagile.biz (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Woodcock commented on  JENKINS-48556  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: timestamps() randomly not recognized as a valid option   
 

  
 
 
 
 

 
 We are on version 1.3.4.1 now. Is this resolved and released?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-31953) Stopping build running parallel branches can doubly deliver stop

2019-01-11 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-31953  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Stopping build running parallel branches can doubly deliver stop   
 

  
 
 
 
 

 
 Possibly. Hard to say.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-43413) RejectedExecutionException at SingleLaneExecutorService when loading CpsFlowExecution after restart

2019-01-11 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Unclear if this specific bug was definitively tracked down and covered by the round of fixes.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-43413  
 
 
  RejectedExecutionException at SingleLaneExecutorService when loading CpsFlowExecution after restart   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 Closed Reopened  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-41339) Environment variables referencing other variables broken

2019-01-11 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-41339  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Environment variables referencing other variables broken   
 

  
 
 
 
 

 
 Tobin Davis 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'
  }
}
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55024) Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs

2019-01-11 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-55024  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs   
 

  
 
 
 
 

 
 After the back and forth here, I am unclear on what the status of this is. Do we have a reproducible bug?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-44609) Docker inspect failing on named multi-stage builds

2019-01-11 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-44609  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Docker inspect failing on named multi-stage builds
 

  
 
 
 
 

 
 Steven Weathers simply run sh 'docker build…' and do not use this feature.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55551) RedactedPasswordTaskListenerDecorator.run is illegal

2019-01-11 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-1  
 
 
  RedactedPasswordTaskListenerDecorator.run is illegal   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Phil Grayson  
 
 
Components: 
 redacted-password-parameters-plugin  
 
 
Created: 
 2019-01-11 22:50  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Jesse Glick  
 

  
 
 
 
 

 
 As per Javadoc: 

Expected to be serializable either locally or over Remoting, so an implementation of decorate(OutputStream) cannot assume that JenkinsJVM.isJenkinsJVM(). Any master-side configuration should thus be saved into instance fields when the decorator is constructed.
 Improve WorkflowTest to 
 
use RestartableJenkinsRule to simulate Jenkins restarts with a running build (try SemaphoreStep to pause in the middle) 
use JenkinsRule.createSlave to simulate use of an agent and thus Remoting 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
  

[JIRA] (JENKINS-14605) Simple means to obtain logged in user's id

2019-01-11 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-14605  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-14605  
 
 
  Simple means to obtain logged in user's id   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Reopened Open  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-14605) Simple means to obtain logged in user's id

2019-01-11 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 

Remember that these methods are generally only meaningful within the dynamic scope of an HTTP request or CLI command. Use the dev mailing list or IRC if you still have issues.
  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-14605  
 
 
  Simple means to obtain logged in user's id   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-46697) Pipeline hangs on allocate node step

2019-01-11 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-46697  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline hangs on allocate node step   
 

  
 
 
 
 

 
 A Pipeline maintainer would need to check whether this is indeed reproducible, and then take it from there.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-21695) IllegalStateException: WRITER masks original exception

2019-01-11 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Please use separate issues for follow-ups rather than reopening.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-21695  
 
 
  IllegalStateException: WRITER masks original exception   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-21695) IllegalStateException: WRITER masks original exception

2019-01-11 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-21695  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-21695  
 
 
  IllegalStateException: WRITER masks original exception   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Reopened Open  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-53575) Configuration-as-Code compatibility

2019-01-11 Thread stefan.wolf....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stefan Wolf updated  JENKINS-53575  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fixed in the Gradle plugin 1.30.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-53575  
 
 
  Configuration-as-Code compatibility   
 

  
 
 
 
 

 
Change By: 
 Stefan Wolf  
 
 
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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55318) Maven logs are not colorized

2019-01-11 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-55318  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Maven logs are not colorized   
 

  
 
 
 
 

 
 Yeah, should suffice to add a dependency on ansicolor and then give Maven the right flag to enable ANSI sequences despite being in batch mode.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55550) SCM polling is failing with Authentication error with Scripted Pipeline

2019-01-11 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-0  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SCM polling is failing with Authentication error with Scripted Pipeline   
 

  
 
 
 
 

 
 That distinction will still most likely be shown to be a configuration issue rather than a bug in the software. If you wish to continue with the bug report, please provide sufficient information so that someone else can duplicate the problem in their environment. The report you've submitted is missing many, many critical details. The community will tend to help you identify those critical details without consuming the time of the one person that does most of the testing and maintenance work on the git plugin. Many of the general items you'll need to provide in the bug report are described in "How to report an issue". Once those general items have been gathered and investigated, then you'll need to provide the details of the specific problem you've reported. If you use the mailing list or chat, you have a much larger pool of people that may be able to spend their time assisting you with the issue. Specific details that will be needed for this use case: 
 
Numbered series of steps which lead from freshly installed system to duplicate the problem 
Jenkins version 
Jenkins master platform (Windows, Linux, etc.) 
Jenkins agent platform where it is succeeding 
Authentication technique used (assumed https and username / password, but could be http and username / password) 
Network configuration surprises (is there a proxy between the agent and the git server, is there a proxy between the master and the git server, etc.) 
Special cases in directory, username or password (does the workspace directory path contain a space, does the password contain characters which are special to the shell, does the username include any surprising characters) 
Git plugin version 
Git client plugin version 
Job definition which shows the problem 
Is the failure specific to this job or do all jobs which use this git server have the same problem? 
Is the failure specific to this git server or does the same thing happen with publicly accessible git servers (like github.com or bitbucket.org)? 
  
 

  
 
 
 
 

 
 
 

 
 
  

[JIRA] (JENKINS-29144) SimpleBuildStep to receive EnvVars

2019-01-11 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-29144  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SimpleBuildStep to receive EnvVars   
 

  
 
 
 
 

 
 Jeremy Marshall CHANGE_URL is defined in branch-api. GIT_URL etc. are map keys in the return value of git / checkout, done in JENKINS-26100.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-12160) Add ability to shelve many projects at once

2019-01-11 Thread pibe...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pierre Beitz resolved as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-12160  
 
 
  Add ability to shelve many projects at once   
 

  
 
 
 
 

 
Change By: 
 Pierre Beitz  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Won't Fix  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-12160) Add ability to shelve many projects at once

2019-01-11 Thread pibe...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pierre Beitz edited a comment on  JENKINS-12160  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add ability to shelve many projects at once   
 

  
 
 
 
 

 
 [~dougborg] this is an interesting feature but I won't have the time to work correctly on it. More interesting I think is to use a groovy script. This is far more powerful as it will allow you to add any kind of logic into your bulk shelve. [Here is an example of such script| [ https://support.cloudbees.com/hc/en-us/articles/236353928-Groovy-Scripts-To-Shelve-Jobs].] I would gladly accept a PR on this feature if somebody has the time to work on it though.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-41319) Not compatible with Pipeline restart feature

2019-01-11 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-41319  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Not compatible with Pipeline restart feature   
 

  
 
 
 
 

 
 I cannot definitely speak for Nicolas De Loof but I believe that plugin is abandoned. You can try dockerNode from the docker-plugin as a conceptual successor.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-12160) Add ability to shelve many projects at once

2019-01-11 Thread pibe...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pierre Beitz commented on  JENKINS-12160  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add ability to shelve many projects at once   
 

  
 
 
 
 

 
 Doug Borg this is an interesting feature but I won't have the time to work correctly on it. More interesting I think is to use a groovy script. This is far more powerful as it will allow you to add any kind of logic into your bulk shelve. [Here is an example of such script|https://support.cloudbees.com/hc/en-us/articles/236353928-Groovy-Scripts-To-Shelve-Jobs.]   I would gladly accept a PR on this feature if somebody has the time to work on it though.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-42873) NPE when retry a failed job when there is a similar job in queue

2019-01-11 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-42873  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42873  
 
 
  NPE when retry a failed job when there is a similar job in queue   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Fixed but Unreleased Reopened  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-42873) NPE when retry a failed job when there is a similar job in queue

2019-01-11 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick resolved as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42873  
 
 
  NPE when retry a failed job when there is a similar job in queue   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Reopened 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-45693) Ability to decorate Pipeline builds as a global extension

2019-01-11 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-45693  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ability to decorate Pipeline builds as a global extension   
 

  
 
 
 
 

 
 It already is. You do need to 

 

true
 

 to acknowledge that you are consuming an experimental API.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-12160) Add ability to shelve many projects at once

2019-01-11 Thread pibe...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pierre Beitz assigned an issue to Pierre Beitz  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-12160  
 
 
  Add ability to shelve many projects at once   
 

  
 
 
 
 

 
Change By: 
 Pierre Beitz  
 
 
Assignee: 
 ashlux Pierre Beitz  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-36997) sshAgent {} inside docker.image().inside {} does not work with long project name

2019-01-11 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-36997  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: sshAgent {} inside docker.image().inside {} does not work with long project name   
 

  
 
 
 
 

 
 Evgeny Shepelyuk maybe ssh-agent is not in $PATH or something.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-40822) After unintentional double-click on Shelve button SCM sync fails and shows log info about project delete in page footer

2019-01-11 Thread pibe...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pierre Beitz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40822  
 
 
  After unintentional double-click on Shelve button SCM sync fails and shows log info about project delete in page footer   
 

  
 
 
 
 

 
Change By: 
 Pierre Beitz  
 
 
Component/s: 
 shelve-project-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-40822) After unintentional double-click on Shelve button SCM sync fails and shows log info about project delete in page footer

2019-01-11 Thread pibe...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pierre Beitz commented on  JENKINS-40822  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: After unintentional double-click on Shelve button SCM sync fails and shows log info about project delete in page footer   
 

  
 
 
 
 

 
 Wojciech Błaszczuk removing the shelve-project-plugin component from this issue, please re-add in case you have a reproduction test case of the latest version of the plugin.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55349) Duplicate symbols in different plugins cause NPEs

2019-01-11 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55349  
 
 
  Duplicate symbols in different plugins cause NPEs
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Labels: 
 diagnostics  robustness  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55328) recordIssues and ScanForIssues in Pipeline get NPE Errors

2019-01-11 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-55328  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: recordIssues and ScanForIssues in Pipeline get NPE Errors   
 

  
 
 
 
 

 
 

there is no way to prevent the exception
 WDYM? Fix the collision—rename or delete the symbol in one of the plugins. Maybe I am missing some context.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54968) Branch API 2.1.1 Path Length

2019-01-11 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Update to 2.1.2. Otherwise, I cannot help without complete steps to reproduce the problem from scratch.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-54968  
 
 
  Branch API 2.1.1 Path Length   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Assignee: 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55244) Shelved projects footprint increased by factor 10

2019-01-11 Thread pibe...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pierre Beitz commented on  JENKINS-55244  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Shelved projects footprint increased by factor 10   
 

  
 
 
 
 

 
 Jens Brejner I confirm the compression was not something that was taken into consideration. This is an interesting feature though, I'll look into adding back some compression using a tar.gz and document this as a real feature to avoid a regression in the future.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55349) Duplicate symbols in different plugins cause NPEs

2019-01-11 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55349  
 
 
  Duplicate symbols in different plugins cause NPEs
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55349) Duplicate symbols in different plugins cause NPEs

2019-01-11 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55349  
 
 
  Duplicate symbols in different plugins cause NPEs
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Labels: 
 diagnostics  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-34313) Exceptions by parallel SCM checkout

2019-01-11 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-34313  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Exceptions by parallel SCM checkout   
 

  
 
 
 
 

 
 AFAIK workflow-scm-step 2.7 should have resolved this (JENKINS-47201), unless you are talking about some unrelated 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55382) Shelve Project plugin does not correctly handle shelvedProjects symbolic link

2019-01-11 Thread pibe...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pierre Beitz commented on  JENKINS-55382  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Shelve Project plugin does not correctly handle shelvedProjects symbolic link   
 

  
 
 
 
 

 
 Ross Oliver I confirm I reproduced the issue, it appeared in version 2.0 of the plugin, I'll need some time to dig into it.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-33274) "Base build" link for first build of branch project

2019-01-11 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-33274  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Base build" link for first build of branch project   
 

  
 
 
 
 

 
 Yeah the only real workaround for the example James Nord gave is to use Sonar to track regressions and give up on doing it from Jenkins.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-34019) ANSIColor plugin leaks format onto next line's timestamp

2019-01-11 Thread dnusb...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum commented on  JENKINS-34019  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ANSIColor plugin leaks format onto next line's timestamp   
 

  
 
 
 
 

 
 And if PR 137 doesn't help, it would be worth checking if PR 147 makes a difference.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes

2019-01-11 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-33510  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes   
 

  
 
 
 
 

 
 Attila Szeremi dir with an absolute path is not supported inside a Docker container. Not really related to this issue. Simply start your sh script with cd. Or avoid using the withDockerContainer step alogether—if it works perfectly for you out of the box, great, otherwise forget about it.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-34019) ANSIColor plugin leaks format onto next line's timestamp

2019-01-11 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-34019  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ANSIColor plugin leaks format onto next line's timestamp   
 

  
 
 
 
 

 
 Recheck after PR 137 (unreleased as of this writing).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55550) SCM polling is failing with Authentication error with Scripted Pipeline

2019-01-11 Thread rajeshherefor...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Raj G commented on  JENKINS-0  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SCM polling is failing with Authentication error with Scripted Pipeline   
 

  
 
 
 
 

 
 Thanks for the quick response. The reason behind posting this a bug (for the Authentication issue) is, it's working perfectly fine if the build is triggered manually but failing with SCM poll  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55550) SCM polling is failing with Authentication error with Scripted Pipeline

2019-01-11 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated  JENKINS-0  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Please don't use the bug database to request help with authentication issues. Authentication issues are almost always related to configuration rather than to bugs in the code. If after more detailed evaluation through questions and answers it is confirmed to be an actual bug in the code, then submit a bug report with sufficient detail that someone else can duplicate the bug. Please use the Jenkins users mailing list or the chat system to seek answers to question.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-0  
 
 
  SCM polling is failing with Authentication error with Scripted Pipeline   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 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 

[JIRA] (JENKINS-55550) SCM polling is failing with Authentication error with Scripted Pipeline

2019-01-11 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated  JENKINS-0  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-0  
 
 
  SCM polling is failing with Authentication error with Scripted Pipeline   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Status: 
 Fixed but Unreleased Closed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55462) "shelve project" button missing for all non-admin users

2019-01-11 Thread pibe...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pierre Beitz commented on  JENKINS-55462  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "shelve project" button missing for all non-admin users   
 

  
 
 
 
 

 
 Roger Wang I reproduced the issue, it seems the check for the delete permission is not correct. I'll work on a fix as soon as possible. In the meantime, I confirm only the admin rights allows to shelve/unshelve. This doesn't seem like a regression as the guilty code has been here for a long time.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55550) SCM polling is failing with Authentication error with Scripted Pipeline

2019-01-11 Thread rajeshherefor...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Raj G created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-0  
 
 
  SCM polling is failing with Authentication error with Scripted Pipeline   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Mark Waite  
 
 
Components: 
 git-plugin  
 
 
Created: 
 2019-01-11 21:29  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Raj G  
 

  
 
 
 
 

 
 I've set up a pipeline project that is configured with "Pipeline script from SCM". The Poll SCM scheduled is set to each minute.  The repo that contains the Jenkinsfile is different than the repo that contains the code.  In this case, the SCM polling failing with Authentication error.   Below are the details from Poll Log   

 

ERROR: polling failed in /var/lib/jenkins/workspace/@script on 
hudson.plugins.git.GitException: Command "git ls-remote -h " returned status code 128:
stdout: 
stderr: remote: HTTP Basic: Access denied
fatal: Authentication failed for ''

	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2038)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1757)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1662)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1653)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getHeadRev(CliGitAPIImpl.java:2820)
	at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:698)
	at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:657)
Caused: java.io.IOException
	at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:659)
	at org.jenkinsci.plugins.workflow.job.WorkflowJob.poll(WorkflowJob.java:629)
	at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:603)
	at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:649)
	at 

[JIRA] (JENKINS-25508) Git plugin doesn't parse changelog (false "First time build")

2019-01-11 Thread nileshpatel....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nilesh Patel commented on  JENKINS-25508  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git plugin doesn't parse changelog (false "First time build")   
 

  
 
 
 
 

 
 Does issue solve for anyone ?    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55376) Fix default date format to show time in console logs

2019-01-11 Thread pibe...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pierre Beitz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55376  
 
 
  Fix default date format to show time in console logs   
 

  
 
 
 
 

 
Change By: 
 Pierre Beitz  
 
 
Labels: 
 2.4-fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55376) Fix default date format to show time in console logs

2019-01-11 Thread pibe...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pierre Beitz updated  JENKINS-55376  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55376  
 
 
  Fix default date format to show time in console logs   
 

  
 
 
 
 

 
Change By: 
 Pierre Beitz  
 
 
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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-44129) Log file logger for Audit trail plugin leaks open file descriptors

2019-01-11 Thread pibe...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pierre Beitz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-44129  
 
 
  Log file logger for Audit trail plugin leaks open file descriptors   
 

  
 
 
 
 

 
Change By: 
 Pierre Beitz  
 
 
Labels: 
 2.4-fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-44129) Log file logger for Audit trail plugin leaks open file descriptors

2019-01-11 Thread pibe...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pierre Beitz updated  JENKINS-44129  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-44129  
 
 
  Log file logger for Audit trail plugin leaks open file descriptors   
 

  
 
 
 
 

 
Change By: 
 Pierre Beitz  
 
 
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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55549) CppCheck Cannot load sidepanel.jelly

2019-01-11 Thread lace...@roboticresearch.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Zachary LaCelle created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55549  
 
 
  CppCheck Cannot load sidepanel.jelly   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Marco Steffan  
 
 
Components: 
 cppcheck-plugin  
 
 
Created: 
 2019-01-11 20:45  
 
 
Environment: 
 jenkinsci/blue-ocean Docker container  Ubuntu 18.04  cppcheck-plugin 1.24  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Zachary LaCelle  
 

  
 
 
 
 

 
 When clicking on the cppcheck results link, I get the following Java dump. This was working on all projects before updating.   org.apache.commons.jelly.JellyTagException: jar:file:/var/jenkins_home/plugins/cppcheck/WEB-INF/lib/cppcheck.jar!/org/jenkinsci/plugins/cppcheck/CppcheckResult/index.jelly:4:62:  No page found 'sidepanel.jelly' for class org.jenkinsci.plugins.cppcheck.CppcheckResult at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:124) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) ...  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

[JIRA] (JENKINS-55546) Warnings-ng crashing on recordIssues

2019-01-11 Thread lace...@roboticresearch.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Zachary LaCelle closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55546  
 
 
  Warnings-ng crashing on recordIssues   
 

  
 
 
 
 

 
Change By: 
 Zachary LaCelle  
 
 
Status: 
 Resolved Closed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55546) Warnings-ng crashing on recordIssues

2019-01-11 Thread lace...@roboticresearch.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Zachary LaCelle commented on  JENKINS-55546  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warnings-ng crashing on recordIssues   
 

  
 
 
 
 

 
 Ah, got it. Thank you.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-27126) New Scroll bar in Jenkins Build history is showing when shouldn't be

2019-01-11 Thread tsorre...@bossfight.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tim Sorrells updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-27126  
 
 
  New Scroll bar in Jenkins Build history is showing when shouldn't be   
 

  
 
 
 
 

 
Change By: 
 Tim Sorrells  
 
 
Labels: 
 ui user-experience  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-27126) New Scroll bar in Jenkins Build history is showing when shouldn't be

2019-01-11 Thread tsorre...@bossfight.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tim Sorrells commented on  JENKINS-27126  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: New Scroll bar in Jenkins Build history is showing when shouldn't be   
 

  
 
 
 
 

 
 I'm seeing this on Jenkins version 2.73.2.  I don't know if we have any plugins installed that affect this problem or not. It doesn't matter how big the Build History box is relative to the size of the job name.  The scrollbar seems to show up whenever the job name gets past a certain fixed length.  Pic included:   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-27126) New Scroll bar in Jenkins Build history is showing when shouldn't be

2019-01-11 Thread tsorre...@bossfight.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tim Sorrells updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-27126  
 
 
  New Scroll bar in Jenkins Build history is showing when shouldn't be   
 

  
 
 
 
 

 
Change By: 
 Tim Sorrells  
 
 
Attachment: 
 Jenkins scroll bar.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55427) Blue Ocean display of sequential stages in parallel stages is flaky

2019-01-11 Thread mlandma...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 boris ivan commented on  JENKINS-55427  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Blue Ocean display of sequential stages in parallel stages is flaky   
 

  
 
 
 
 

 
 We see the same flaky behavior, re: nodes complete but not showing as complete (and often not clickable). Also, note the truncation in the picture you've attached, re: the name of that stage. The truncation of that stage name is too aggressive, making it useless (https://issues.jenkins-ci.org/browse/JENKINS-55393)    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-27668) Add support for multiple git repositories in a single workspace

2019-01-11 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite closed an issue as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-27668  
 
 
  Add support for multiple git repositories in a single workspace   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Status: 
 Resolved Closed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub

2019-01-11 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54126  
 
 
  Jenkinsfile not found in PR on GitHub   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Priority: 
 Critical Blocker  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-25891) Ability to link to individual pipeline

2019-01-11 Thread christoph.oberm...@gmx.at (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Obermair edited a comment on  JENKINS-25891  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ability to link to individual pipeline   
 

  
 
 
 
 

 
 This feature would be very helpful! In particular, I would like to refer to the pipeline of a certain run of the pipeline's "Initial Job" (e.g. the build number of  the  pipeline's "Initial Job" could be a parameter in the URL's query string).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55535) Warnings does not fail the build

2019-01-11 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner commented on  JENKINS-55535  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warnings does not fail the build   
 

  
 
 
 
 

 
 Where is the documentation missing? In a freestyle build (and snippet generator) all these options are described in detail.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-25891) Ability to link to individual pipeline

2019-01-11 Thread christoph.oberm...@gmx.at (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Obermair edited a comment on  JENKINS-25891  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ability to link to individual pipeline   
 

  
 
 
 
 

 
 This feature would be very helpful! In particular, I would like to refer to  a  the pipeline of a certain run of the pipeline's "Initial Job" (e.g. the build number of pipeline's "Initial Job" could be a parameter in the URL's query string).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-25891) Ability to link to individual pipeline

2019-01-11 Thread christoph.oberm...@gmx.at (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Obermair commented on  JENKINS-25891  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ability to link to individual pipeline   
 

  
 
 
 
 

 
 This feature would be very helpful! In particular, I would like to refer to a the pipeline of a certain run of the pipeline's "Initial Job" (e.g. the build number of pipeline's "Initial Job" could be a parameter in the URL's query string).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55539) determining blame via git fails with out-off-tree builds

2019-01-11 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner commented on  JENKINS-55539  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: determining blame via git fails with out-off-tree builds   
 

  
 
 
 
 

 
 Is this option an official Git client option? I have a freestyle build with the additional behavior 'Checkout to local sub-directory' that correctly identifies a sub folder 'repository'. 

 
[Java] GIT_COMMIT env = '6d599b80b43a3ab061d20083429cb53832f14f51'
[Java] Git working tree = '/tmp/node2/workspace/New - Freestyle - Git SubFolder - Model/repository'
[Java] Git commit ID = '6d599b80b43a3ab061d20083429cb53832f14f51'
[Java] Job workspace = '/private/tmp/node2/workspace/New - Freestyle - Git SubFolder - Model/repository'
 

 Can you please check if you can get a similar job running with a freestyle build?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-25276) Job Disappears from ListView after rename

2019-01-11 Thread sebastien.bon...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sebastien Bonami commented on  JENKINS-25276  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Job Disappears from ListView after rename   
 

  
 
 
 
 

 
 I have this problem using Jenkins ver. 2.89.4. Can someone please confirm on which version this was 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55536) Add an option to add additional remotes to the git repository in SCM

2019-01-11 Thread flashmo...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Danila M commented on  JENKINS-55536  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add an option to add additional remotes to the git repository in SCM   
 

  
 
 
 
 

 
 Thanks for clarifying. However, your screenshot shows that the snippet generator (forgot about that) doesn't have the same option to add more remotes, as freestyle projects have which furthers the confusion. What are its current limitations? I wouldn't call it advanced in the git world, since it's what a lot of git users sometimes deal with one way or another. It's just a simple `git remote add  `. Heh, asking for documentation PRs from users that'd just found out about feature existence and don't really know yet how it fully works is a bold move ;P  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55536) Add an option to add additional remotes to the git repository in SCM

2019-01-11 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated  JENKINS-55536  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55536  
 
 
  Add an option to add additional remotes to the git repository in SCM   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Status: 
 Fixed but Unreleased Closed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55536) Add an option to add additional remotes to the git repository in SCM

2019-01-11 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite edited a comment on  JENKINS-55536  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add an option to add additional remotes to the git repository in SCM   
 

  
 
 
 
 

 
 You're correct that the "add additional repositories" option is a source of confusion.  Other users assumed it was some way to include multiple independent repositories in a single workspace.  Rather, it handles only the case that you're describing, additional additional remotes as sources for the same repository.The Pipeline Syntax hint for the {{checkout}} step presents a similar user interface as is available with Freestyle jobs.  It is quite a helpful utility to construct Pipeline syntax.  It is available as:* !pipeline-syntax-access.png|thumbnail!* !pipeline-syntax-checkout.png|thumbnail! It Multiple remotes for a single job  is not a widely used or well-known feature because it has significant limitations on its use.  I don't especially want to document its use because it is such an advanced feature.  You're welcome to use it.  There are several automated tests which confirm that it is still working, but it is a narrow enough use that I'd rather not publicize it widely.If you feel strongly that it should be documented, you're welcome to submit documentation to the git plugin wiki page or to submit a pull request to jenkins.io with documentation.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55539) determining blame via git fails with out-off-tree builds

2019-01-11 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55539  
 
 
  determining blame via git fails with out-off-tree builds   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Labels: 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55546) Warnings-ng crashing on recordIssues

2019-01-11 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 The format has slightly changed, see documentation: 

 

recordIssues enabledForFailure: false, aggregatingResults : false, tool: gcc4()
 

  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-55546  
 
 
  Warnings-ng crashing on recordIssues   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit 

[JIRA] (JENKINS-55546) Warnings-ng crashing on recordIssues

2019-01-11 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55546  
 
 
  Warnings-ng crashing on recordIssues   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Status: 
 Reopened Resolved  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55536) Add an option to add additional remotes to the git repository in SCM

2019-01-11 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-55536  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add an option to add additional remotes to the git repository in SCM   
 

  
 
 
 
 

 
 You're correct that the "add additional repositories" option is a source of confusion. Other users assumed it was some way to include multiple independent repositories in a single workspace. Rather, it handles only the case that you're describing, additional additional remotes as sources for the same repository. The Pipeline Syntax hint for the checkout step presents a similar user interface as is available with Freestyle jobs. It is quite a helpful utility to construct Pipeline syntax. It is available as: 
 
 
 
 It is not a widely used or well-known feature because it has significant limitations on its use. I don't especially want to document its use because it is such an advanced feature. You're welcome to use it. There are several automated tests which confirm that it is still working, but it is a narrow enough use that I'd rather not publicize it widely. If you feel strongly that it should be documented, you're welcome to submit documentation to the git plugin wiki page or to submit a pull request to jenkins.io with documentation.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55546) Warnings-ng crashing on recordIssues

2019-01-11 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55546  
 
 
  Warnings-ng crashing on recordIssues   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 Resolved Reopened  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55536) Add an option to add additional remotes to the git repository in SCM

2019-01-11 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55536  
 
 
  Add an option to add additional remotes to the git repository in SCM   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Attachment: 
 pipeline-syntax-checkout.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55536) Add an option to add additional remotes to the git repository in SCM

2019-01-11 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55536  
 
 
  Add an option to add additional remotes to the git repository in SCM   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Attachment: 
 screenshot-1.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55536) Add an option to add additional remotes to the git repository in SCM

2019-01-11 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55536  
 
 
  Add an option to add additional remotes to the git repository in SCM   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Attachment: 
 screenshot-1.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50739) Active Choices - The variables jenkinsProject and jenkinsBuild are NOT available in pipeline projects

2019-01-11 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50739  
 
 
  Active Choices - The variables jenkinsProject and jenkinsBuild are NOT available in pipeline projects   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Labels: 
 active-choices  jenkins 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50739) Active Choices - The variables jenkinsProject and jenkinsBuild are NOT available in pipeline projects

2019-01-11 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50739  
 
 
  Active Choices - The variables jenkinsProject and jenkinsBuild are NOT available in pipeline projects   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Environment: 
 Active Choices 2.1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55536) Add an option to add additional remotes to the git repository in SCM

2019-01-11 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55536  
 
 
  Add an option to add additional remotes to the git repository in SCM   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Attachment: 
 pipeline-syntax-access.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55271) Jenkinsfile Active Choice Parameter

2019-01-11 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler updated  JENKINS-55271  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55271  
 
 
  Jenkinsfile Active Choice Parameter   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55271) Jenkinsfile Active Choice Parameter

2019-01-11 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55271  
 
 
  Jenkinsfile Active Choice Parameter   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Issue Type: 
 Bug Task  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-47324) FilePath API in Jenkins should propagate errors

2019-01-11 Thread bat...@batmat.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Baptiste Mathus closed an issue as Done  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-47324  
 
 
  FilePath API in Jenkins should propagate errors   
 

  
 
 
 
 

 
Change By: 
 Baptiste Mathus  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Done  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-47324) FilePath API in Jenkins should propagate errors

2019-01-11 Thread bat...@batmat.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Baptiste Mathus commented on  JENKINS-47324  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: FilePath API in Jenkins should propagate errors   
 

  
 
 
 
 

 
 OK, then let's consider this fixed until proven otherwise. Like I wrote above anyway, it can be reopened anytime once we know about left things to be still fixed. Thanks for the feedback Devin.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-30515) scm (git) command does not fail correctly when it cannot look up credentials

2019-01-11 Thread jtabo...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jose Blas Camacho Taboada updated  JENKINS-30515  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-30515  
 
 
  scm (git) command does not fail correctly when it cannot look up credentials   
 

  
 
 
 
 

 
Change By: 
 Jose Blas Camacho Taboada  
 
 
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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55536) Add an option to add additional remotes to the git repository in SCM

2019-01-11 Thread flashmo...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Danila M edited a comment on  JENKINS-55536  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add an option to add additional remotes to the git repository in SCM   
 

  
 
 
 
 

 
 There is no option to specify additional remotes in the SCM configuration (for freestyle project).There is also absolutely no info/documentation on how to properly set this up in the pipeline. Even knowing what I need to search for thanks to your links I didn't find any conclusive info on how to properly use `userRemoteConfigs` (though I can guess from some examples). Is this the only way?Before that, I've tried consulting with several knowledgeable people, but they were also not aware of this feature.What do you mean by the ""Advanced" button on the git repository configuration for Pipeline syntax."? There is no such thing. The declarative pipeline configuration is contained withing Jenkinsfile. Freestyle project doesn't have advanced options, beside specifying name and refspec.There is an option to add additional repositories, however it's not clear what it actually does and I  assumed it just clones additional repositories, though now, it seems like it might've been what I was looking for. Then, this option should've been named "add remote" since it adds new remotes to the existing local repository. Of course only if it;s indeed what it does.I  don't know about multibranch. I've only tried freestyle and regular pipeline projects.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55544) kubernetes-plugin creates blank kubeconfig

2019-01-11 Thread m...@laverse.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Max Laverse assigned an issue to Ruben Fernandez  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55544  
 
 
  kubernetes-plugin creates blank kubeconfig   
 

  
 
 
 
 

 
Change By: 
 Max Laverse  
 
 
Assignee: 
 Max Laverse Ruben 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55536) Add an option to add additional remotes to the git repository in SCM

2019-01-11 Thread flashmo...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Danila M commented on  JENKINS-55536  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add an option to add additional remotes to the git repository in SCM   
 

  
 
 
 
 

 
 There is no option to specify additional remotes in the SCM configuration (for freestyle project). There is also absolutely no info/documentation on how to properly set this up in the pipeline. Even knowing what I need to search for thanks to your links I didn't find any conclusive info on how to properly use `userRemoteConfigs` (though I can guess from some examples). Is this the only way? Before that, I've tried consulting with several knowledgeable people, but they were also not aware of this feature. What do you mean by the ""Advanced" button on the git repository configuration for Pipeline syntax."? There is no such thing. The declarative pipeline configuration is contained withing Jenkinsfile. I don't know about multibranch. I've only tried freestyle and regular pipeline projects.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


  1   2   >