[JIRA] [ivy-plugin] (JENKINS-32141) Possibility to add credentials to Ivy settings

[d...@fortysix.ch (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dominik Bartholdi assigned an issue to Timothy Bingaman 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32141 
 
 
 
  Possibility to add credentials to Ivy settings  
 
 
 
 
 
 
 
 
 

Change By:
 
 Dominik Bartholdi 
 
 
 

Component/s:
 
 ivy-plugin 
 
 
 

Component/s:
 
 config-file-provider-plugin 
 
 
 

Assignee:
 
 Dominik Bartholdi Timothy Bingaman 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [config-file-provider-plugin] (JENKINS-32141) Possibility to add credentials to Ivy settings

[christian.haeuss...@huk-coburg.de (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Häussler commented on  JENKINS-32141 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Possibility to add credentials to Ivy settings  
 
 
 
 
 
 
 
 
 
 
New feature request for the ivy plugin: https://issues.jenkins-ci.org/browse/JENKINS-34192 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [config-file-provider-plugin] (JENKINS-32142) Possibility to add Gradle settings file

[christian.haeuss...@huk-coburg.de (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Häussler commented on  JENKINS-32142 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Possibility to add Gradle settings file  
 
 
 
 
 
 
 
 
 
 
New feature request for the gradle plugin: https://issues.jenkins-ci.org/browse/JENKINS-34193 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [gradle-plugin] (JENKINS-34193) Integrate with the config file provider plugin

[christian.haeuss...@huk-coburg.de (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Häussler assigned an issue to George Simpson 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34193 
 
 
 
  Integrate with the config file provider plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Häussler 
 
 
 

Assignee:
 
 Dominik Bartholdi George Simpson 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [config-file-provider-plugin] (JENKINS-34193) Integrate with the config file provider plugin

[christian.haeuss...@huk-coburg.de (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Häussler created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34193 
 
 
 
  Integrate with the config file provider plugin  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Dominik Bartholdi 
 
 
 

Components:
 

 config-file-provider-plugin 
 
 
 

Created:
 

 2016/Apr/13 5:41 AM 
 
 
 

Labels:
 

 Gradle 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Christian Häussler 
 
 
 
 
 
 
 
 
 
 
Make it possibility to add Gradle settings file (init.gradle) for Gradle configuartion with credentials. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 
  

[JIRA] [gradle-plugin] (JENKINS-34193) Integrate with the config file provider plugin

[christian.haeuss...@huk-coburg.de (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Häussler updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34193 
 
 
 
  Integrate with the config file provider plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Häussler 
 
 
 

Component/s:
 
 gradle-plugin 
 
 
 

Component/s:
 
 config-file-provider-plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [gradle-plugin] (JENKINS-34193) Integrate with the config file provider plugin

[christian.haeuss...@huk-coburg.de (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Häussler commented on  JENKINS-34193 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Integrate with the config file provider plugin  
 
 
 
 
 
 
 
 
 
 
The config file provider plugin already provides an extension point [2] that should be integrated by the gradle plugin. 
[1] https://wiki.jenkins-ci.org/display/JENKINS/Gradle+Plugin [2] https://wiki.jenkins-ci.org/display/JENKINS/Config+File+Provider+Plugin#ConfigFileProviderPlugin-ExtensionPoint 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [ivy-plugin] (JENKINS-34192) Integrate with the config file provider plugin

[christian.haeuss...@huk-coburg.de (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Häussler commented on  JENKINS-34192 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Integrate with the config file provider plugin  
 
 
 
 
 
 
 
 
 
 
The config file provider plugin already provides an extension point [1] that should be integrated by the ivy plugin. 
[1] https://wiki.jenkins-ci.org/display/JENKINS/Config+File+Provider+Plugin#ConfigFileProviderPlugin-ExtensionPoint 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [ivy-plugin] (JENKINS-34192) Integrate with the config file provider plugin

[christian.haeuss...@huk-coburg.de (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Häussler assigned an issue to Timothy Bingaman 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34192 
 
 
 
  Integrate with the config file provider plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Häussler 
 
 
 

Assignee:
 
 Dominik Bartholdi Timothy Bingaman 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [config-file-provider-plugin] (JENKINS-34192) Integrate with the config file provider plugin

[christian.haeuss...@huk-coburg.de (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Häussler created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34192 
 
 
 
  Integrate with the config file provider plugin  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Dominik Bartholdi 
 
 
 

Components:
 

 config-file-provider-plugin 
 
 
 

Created:
 

 2016/Apr/13 5:35 AM 
 
 
 

Labels:
 

 Ivy 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Christian Häussler 
 
 
 
 
 
 
 
 
 
 
Make it possibility to add credentials to Ivy configuration file. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

   

[JIRA] [ivy-plugin] (JENKINS-34192) Integrate with the config file provider plugin

[christian.haeuss...@huk-coburg.de (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Häussler updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34192 
 
 
 
  Integrate with the config file provider plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Häussler 
 
 
 

Component/s:
 
 ivy-plugin 
 
 
 

Component/s:
 
 config-file-provider-plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [active-choices-plugin] (JENKINS-34188) jenkins.log noise: "script parameter ... is not an instance of Java.util.Map."

[danagoye...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dana Goyette updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34188 
 
 
 
  jenkins.log noise: "script parameter ... is not an instance of Java.util.Map."  
 
 
 
 
 
 
 
 
 

Change By:
 
 Dana Goyette 
 
 
 
 
 
 
 
 
 
 On my Jenkins master, I see a lot of the following noise in jenkins.log:Apr 12, 2016 3:21:06 PM org.biouno.unochoice.AbstractScriptableParameter getChoicesWARNING: Script parameter with name 'PARAM_NAME_HERE' is not an instance of java.util.Map. The parameter value isApr 12, 2016 3:21:06 PM org.biouno.unochoice.AbstractScriptableParameter getChoicesWARNING: Script parameter with name 'PARAM_NAME_HERE' is not an instance of java.util.Map. The parameter value isThe mentioned parameter (name altered here for privacy) is an Active Choices Reactive Reference Parameter, of type "formatted html", and the HTML contains the following field  (with value also altered for privacy) : 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [remoting] (JENKINS-33886) Can only connect one JNLP3 slave per IP address

[jeff.kay...@dbdr.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jeff Kayser commented on  JENKINS-33886 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Can only connect one JNLP3 slave per IP address  
 
 
 
 
 
 
 
 
 
 
Hi, Akshay. 
You don't need a proxy. Just using an intervening Firewall/Router should do the trick. Basically, if your Master is connecting to slaves across the Internet, the JNLP3 logic will have problems. 
You should be able to replicate via: 
Master <=> Firewall/Router <=> Internet <=> Firewall/Router <=> multiple slave machines. 
Or, more simply: 
Master <=> Network <=> Firewall/Router <=> Slaves. 
The idea is that the Firewall/Router will NAT the IP addresses of the slaves to one IP address, and the Master, seeing multiple slaves connecting via the same IP address, will get confused. 
For example: 
Slave IP addresses: 192.168.10.1 192.168.10.2 192.168.10.3  
NAT firewall / Router: 
Private IP <=> Public IP 192.168.10.1 <=> 1.2.3.4 port 100 192.168.10.2 <=> 1.2.3.4 port 200 192.168.10.3 <=> 1.2.3.4 port 300 
Converts all private IP addresses of the slave machines (behind the firewall) to the publicly routeable IP address that firewall uses to connect to the Internet. 
Internet: 
Or any other intervening network. 
Master: 
Will see three different slaves try to connect with the same IP address (1.2.3.4) and different NAT ports. 
Master will get confused. 
I hope this helps. 
I have slaves that are on a remote network, across the Internet, with an intervening Firewall/Router, and JNLP3 did not work. JNLP2 works fine with that configuration. 
I'll create a simple test to replicate. 
Jeff Kayser jeff.kay...@dbdr.com 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
  

[JIRA] [ssh-credentials-plugin] (JENKINS-34191) Unable to run scripts which is present in a app id which is a sudo user. I am connecting Jenkins to Linux from SSH using Shell commands.

[ajith3...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ajith KR created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34191 
 
 
 
  Unable to run scripts which is present in a app id which is a sudo user. I am connecting Jenkins to Linux from SSH using Shell commands.   
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 stephenconnolly 
 
 
 

Components:
 

 ssh-credentials-plugin 
 
 
 

Created:
 

 2016/Apr/13 1:57 AM 
 
 
 

Environment:
 

 Jenkins is installed in Windows and i want to invoke scripts in Linux through Jenkins web 
 
 
 

Priority:
 
  Blocker 
 
 
 

Reporter:
 
 Ajith KR 
 
 
 
 
 
 
 
 
 
 
Jenkins is installed in Windows and i want to invoke scripts in Linux through Jenkins web. The scripts are present in the Linux server which is secured inside a sudo app. Please help me to find a possible solution. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
  

[JIRA] [configurationslicing-plugin] (JENKINS-34190) Configuration slicer for Maven Snapshot dependency build trigger

[or...@rikus.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jeff Bischoff commented on  JENKINS-34190 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Configuration slicer for Maven Snapshot dependency build trigger  
 
 
 
 
 
 
 
 
 
 
Pull request created: https://github.com/jenkinsci/configurationslicing-plugin/pull/18 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [extended-choice-parameter-plugin] (JENKINS-19867) resolve variables on the config. parameters

[vi...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 vimil resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Fixed in 0.63 version 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-19867 
 
 
 
  resolve variables on the config. parameters  
 
 
 
 
 
 
 
 
 

Change By:
 
 vimil 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [configurationslicing-plugin] (JENKINS-34190) Configuration slicer for Maven Snapshot dependency build trigger

[or...@rikus.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jeff Bischoff created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34190 
 
 
 
  Configuration slicer for Maven Snapshot dependency build trigger  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Jeff Bischoff 
 
 
 

Components:
 

 configurationslicing-plugin 
 
 
 

Created:
 

 2016/Apr/13 1:13 AM 
 
 
 

Labels:
 

 configuration maven 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Jeff Bischoff 
 
 
 
 
 
 
 
 
 
 
The configuration slicer plugin does not currently support slicing the Maven build triggers boolean properties. This improvement will add support for configuration slicing of the "Build whenever a SNAPSHOT dependency is built" build trigger in particular. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
  

[JIRA] [configurationslicing-plugin] (JENKINS-34190) Configuration slicer for Maven Snapshot dependency build trigger

[or...@rikus.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jeff Bischoff started work on  JENKINS-34190 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Jeff Bischoff 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [subversion-plugin] (JENKINS-31455) Build instability with "ISVNAuthentication provider did not provide credentials"

[drkstr...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aaron Miller commented on  JENKINS-31455 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Build instability with "ISVNAuthentication provider did not provide credentials"  
 
 
 
 
 
 
 
 
 
 
Happens rather consistently here (close to every-other build). I would happily accept any consistent work around. 
Jenkins: 1.656 Subversion: 2.5.7 Ubuntu 14.04.4 LTS 
Example Config: 

 



  
  
  false
  
"mantis@0.26">
  http://jenkins.my.local/mantisbt/
  -1
  Not Selected
  
(?=issue #?)(\d+)(?=)
0
  
  false

  
  "hudson.scm.SubversionSCM" plugin="subversion@2.5.7">

  
http://vlstb2.my.local:222/svn/widget/trunk
5b01e1f8-4d5b-487e-8b66-1143d4bca506
.
infinity
false
  


  
http://vlstb2.my.local:222/svn/externs
5b01e1f8-4d5b-487e-8b66-1143d4bca506
  
  
http://vlstb2.my.local:222/svn/commons/trunk
5b01e1f8-4d5b-487e-8b66-1143d4bca506
  
  






"hudson.scm.subversion.UpdateUpdater"/>
false
false
  
  true
  false
  false
  true
  

  
  commons,externs/font-awesome/trunk,externs/jquery-mobile/trunk,externs/createjs/trunk,
  
SUCCESS
0
BLUE
true
  


  @midnight
  false

  
  false
  
"ant@1.2">
  clean build test
  (Default)
  sass.cmd=/usr/local/bin/sass

  
  
"junit@1.11">
  build/report/xunit/*.xml
  false
  1.0
  false

  
  
"ansicolor@0.4.2">
  xterm

  

 

 
Cheers and thanks for your time! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[JIRA] [core] (JENKINS-34189) footer overlaps with content due to css settings

[tba...@circle.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Trevor Baker commented on  JENKINS-34189 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: footer overlaps with content due to css settings  
 
 
 
 
 
 
 
 
 
 
See https://github.com/jenkinsci/jenkins/pull/2254 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [core] (JENKINS-34189) footer overlaps with content due to css settings

[tba...@circle.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Trevor Baker created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34189 
 
 
 
  footer overlaps with content due to css settings  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Frédéric Camblor 
 
 
 

Attachments:
 

 Screen Shot 2016-04-12 at 7.24.31 PM.png 
 
 
 

Components:
 

 core, scm-sync-configuration-plugin 
 
 
 

Created:
 

 2016/Apr/13 12:37 AM 
 
 
 

Environment:
 

 Jenkins 1.648  scm-sync-configuration 0.0.9 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Trevor Baker 
 
 
 
 
 
 
 
 
 
 
The footer CSS has position: absolute and had a variable height. Since the footer can contain error messages from plugins, the height would grow to cover up actual content (console logs, etc.). 
For example, the scm-sync-configuration plugin has the option to put scm failures in the footer. It adds as many newlines are there are failing commits, which can be many lines until someone fixes the problem or clears the log. The footer expands upwards and occludes the console log, which makes diagnosing failed builds problematic. 

 
 

[JIRA] [active-choices-plugin] (JENKINS-34188) jenkins.log noise: "script parameter ... is not an instance of Java.util.Map."

[danagoye...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dana Goyette created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34188 
 
 
 
  jenkins.log noise: "script parameter ... is not an instance of Java.util.Map."  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Bruno P. Kinoshita 
 
 
 

Components:
 

 active-choices-plugin 
 
 
 

Created:
 

 2016/Apr/13 12:24 AM 
 
 
 

Environment:
 

 Jenkins 1.656. Active Choices 1.4 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Dana Goyette 
 
 
 
 
 
 
 
 
 
 
On my Jenkins master, I see a lot of the following noise in jenkins.log: 
Apr 12, 2016 3:21:06 PM org.biouno.unochoice.AbstractScriptableParameter getChoices WARNING: Script parameter with name 'PARAM_NAME_HERE' is not an instance of java.util.Map. The parameter value is Apr 12, 2016 3:21:06 PM org.biouno.unochoice.AbstractScriptableParameter getChoices WARNING: Script parameter with name 'PARAM_NAME_HERE' is not an instance of java.util.Map. The parameter value is 
The mentioned parameter (name altered here for privacy) is an Active Choices Reactive Reference Parameter, of type "formatted html", and the HTML contains the following field: 
" class="setting-input"/> 
 
 
 
 
 
 
 

[JIRA] [core] (JENKINS-33546) Regression with build parameters in XML API

[vivek.pan...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vivek Pandey commented on  JENKINS-33546 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Regression with build parameters in XML API  
 
 
 
 
 
 
 
 
 
 
Fixed in Stapler 1.242. Waiting to get integrated in to Jenkins 2.x. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [copyartifact-plugin] (JENKINS-24892) Copyartifact 2.0

[de...@ikedam.jp (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ikedam commented on  JENKINS-24892 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Copyartifact 2.0  
 
 
 
 
 
 
 
 
 
 
Work still in progress, and no progress for some months  Please also see following pages for the current status: 
 

https://wiki.jenkins-ci.org/display/JENKINS/Preview+for+Copy+Artifact+2.0
 

https://github.com/jenkinsci/copyartifact-plugin/pull/71
 
 
Completed implementations, but no tests for new implementations and features. I don't have time to work that for now. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [core] (JENKINS-25704) Scheduled triggering stops working until restart

[jwstr...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jonathan Strickland commented on  JENKINS-25704 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Scheduled triggering stops working until restart  
 
 
 
 
 
 
 
 
 
 
Tom Lachner See in your thread dump if you see that of a thread dump at JENKINS-30588 
java.net.SocketInputStream.socketRead0  followed in stack is the stashpullrequest timer 
Its misleading but yes the cron thread is may be waiting on completion of the timer task of the stash pull request, which will never complete due to a hung socket. David Resnick, we actually didn't see the issue until multiple teams in our group starting having multiple repos each with pull requests (thus multiple jobs with more load on our production stash instance) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [core] (JENKINS-25704) Scheduled triggering stops working until restart

[jwstr...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jonathan Strickland edited a comment on  JENKINS-25704 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Scheduled triggering stops working until restart  
 
 
 
 
 
 
 
 
 
 [~timguy] See in your thread dump if you see that of a thread dump at JENKINS-30588java.net.SocketInputStream.socketRead0followed in stack is the stashpullrequest timerIts misleading but yes the cron thread  is  may be waiting on completion of the timer task of the stash pull request, which will never complete due to a hung socket.  [~david_resnick], we actually didn't see the issue until multiple teams in our group starting having multiple repos each with pull requests (thus multiple jobs with more load on our production stash instance) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [git-plugin] (JENKINS-21264) inverse build strategy issues

[yanf...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Yan-Fa Li commented on  JENKINS-21264 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: inverse build strategy issues  
 
 
 
 
 
 
 
 
 
 
Running Jenkins in a docker container. v.1642.4 official docker hub image. Plugins Git plugin 2.4.4. Github plugin 1.18.2.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [git-plugin] (JENKINS-21264) inverse build strategy issues

[yanf...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Yan-Fa Li commented on  JENKINS-21264 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: inverse build strategy issues  
 
 
 
 
 
 
 
 
 
 
I've got a very similar issue, but I think it may be related to how git-client tracks what has been built. We use github-enterprise and it has a feature called gh-pages. This is a special branch that has only documentation, it's built and force pushed from master from a documentation task. 
The job is configured as build `*/gh-pages` branch with the inverse strategy. Logically I want it to build everything but gh-pages. 
Here's what I'm seeing. Github client checks branch and detects that gh-pages has changed, but can't tell not to build it because it has never been built. It kicks off a build. The builder builds the default branch because it can't tell what branch has changed because the inverse strategy tells it to ignore gh-pages. 
We are using polling to avoid giving jenkins too many privileges on github enterprise. Next time it polls, git client can see gh-pages has changed, but can't find a build with that commit, rinse repeat. 
What would be great is if github client were smart enough to detect that it's running inverse and not build the branch that matches and not kick off a build. My only recourse at this point is to do 1 of 2 things. Stop building branches and only build master; not a great choice. Add a fake build task to gh-pages branch that will allow the branch to be built without error and stop using the inverse strategy. 
Since this involves multiple plugins and strategies I'm not sure who's responsible for fixing it. It's basically a bug expressed because of a particular combination of features and plugins. Any help you can offer is appreciated. Thanks for all the amazing work that goes into Jenkins. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[JIRA] [coverity-plugin] (JENKINS-16797) Coverity plugin insert cov-build commands into perforce workspace causing P4 to fail

[cmay...@cisco.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Caleb Mayeux resolved as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
I know this bug is three years old, but ran into this myself, and wanted to update for those who still might run into it. 
It's not really a defect - it's a configuration issue. By default coverity wraps all the commands, but there's a field, "cov-build blacklist", where you put a comma-delimited list of commands that shouldn't be wrapped. Thus, the proper configuration where this will work is to put the path to your p4 executable in that field, something like: /auto/perforce/p4bin/current/p4. Then you can checkout without issue. 
Also you can use the newer P4 Jenkins plugin (as opposed to the Perforce Plugin) that's supported by perforce itself, and it doesn't require this configuration. 
Hope this helps. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-16797 
 
 
 
  Coverity plugin insert cov-build commands into perforce workspace causing P4 to fail  
 
 
 
 
 
 
 
 
 

Change By:
 
 Caleb Mayeux 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Not A Defect 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 

[JIRA] [build-name-setter-plugin] (JENKINS-34181) NullPointerException in BuildNameSetter.setup

[jeys...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jey Saba commented on  JENKINS-34181 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: NullPointerException in BuildNameSetter.setup  
 
 
 
 
 
 
 
 
 
 
I'm also seeing this issue. The problem is fixed only when an existing job is re-saved. When this happens, the job's config XML adds the runAtStart and runAtEnd elements: 

 

"build-name-setter@1.6.0">
...
true
true

 

 
I think the plugin should assume these defaults if they are not defined in the job. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [workflow-plugin] (JENKINS-26132) Executor should show the current stage the flow run is in

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-26132 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Executor should show the current stage the flow run is in  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Jesse Glick Path: src/main/java/org/jenkinsci/plugins/workflow/cps/DSL.java src/main/java/org/jenkinsci/plugins/workflow/cps/steps/LoadStepExecution.java http://jenkins-ci.org/commit/workflow-cps-plugin/32c5626173ff03becc9e563d4aad1058899ba783 Log: Merge pull request #5 from jglick/JENKINS-26132-FlowNodeSerialWalker 
Load step flow graph fix 
Compare: https://github.com/jenkinsci/workflow-cps-plugin/compare/5e8cbc2be2b3...32c5626173ff 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [workflow-plugin] (JENKINS-26156) Erroneous handling of BodyInvoker.withDisplayName

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-26156 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Erroneous handling of BodyInvoker.withDisplayName  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Jesse Glick Path: src/main/java/org/jenkinsci/plugins/workflow/cps/CpsBodyExecution.java src/main/java/org/jenkinsci/plugins/workflow/cps/CpsBodyInvoker.java src/test/java/org/jenkinsci/plugins/workflow/DynamicEnvironmentExpanderTest.java http://jenkins-ci.org/commit/workflow-cps-plugin/ff4ab3e544a346400aaead547565f29d99c74990 Log: [FIXED JENKINS-26156] Fixed BodyInvoker.withDisplayName implementation to allow a non-null argument. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [workflow-plugin] (JENKINS-30088) Clean up step display

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-30088 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Clean up step display  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Jesse Glick Path: src/main/java/org/jenkinsci/plugins/workflow/cps/nodes/StepEndNode.java src/main/java/org/jenkinsci/plugins/workflow/cps/nodes/StepStartNode.java src/test/java/org/jenkinsci/plugins/workflow/WorkflowJobNonRestartingTest.java http://jenkins-ci.org/commit/workflow-cps-plugin/2ef59e10507b5293912913f4865b26ead5568d02 Log: 

JENKINS-30088
 Cleaner appearance of nodes with blocks. · Use the function name, not step display name, on the overall start and end nodes. · Omit any text on the block start and end nodes. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [workflow-plugin] (JENKINS-26156) Erroneous handling of BodyInvoker.withDisplayName

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-26156 
 
 
 
  Erroneous handling of BodyInvoker.withDisplayName  
 
 
 
 
 
 
 
 
 

Change By:
 
 SCM/JIRA link daemon 
 
 
 

Status:
 
 In Progress Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [workflow-plugin] (JENKINS-26156) Erroneous handling of BodyInvoker.withDisplayName

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-26156 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Erroneous handling of BodyInvoker.withDisplayName  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Jesse Glick Path: src/main/java/org/jenkinsci/plugins/workflow/cps/CpsBodyExecution.java src/main/java/org/jenkinsci/plugins/workflow/cps/CpsBodyInvoker.java src/main/java/org/jenkinsci/plugins/workflow/cps/nodes/StepEndNode.java src/main/java/org/jenkinsci/plugins/workflow/cps/nodes/StepStartNode.java src/test/java/org/jenkinsci/plugins/workflow/DynamicEnvironmentExpanderTest.java src/test/java/org/jenkinsci/plugins/workflow/WorkflowJobNonRestartingTest.java http://jenkins-ci.org/commit/workflow-cps-plugin/5e8cbc2be2b340c2532d4720c7a24ca44d53c4c3 Log: Merge pull request #3 from jglick/

JENKINS-26156
-BodyInvoker.withDisplayName 


JENKINS-26156
 BodyInvoker.displayName was broken 
Compare: https://github.com/jenkinsci/workflow-cps-plugin/compare/654e8b4fdbde...5e8cbc2be2b3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [assembla-plugin] (JENKINS-29882) Authentication Fails

[jvsc...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jordan schinella commented on  JENKINS-29882 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Authentication Fails   
 
 
 
 
 
 
 
 
 
 
same issue here. Getting a 401 with correct credentials. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [promoted-builds-plugin] (JENKINS-34187) promoted-builds plugin NullPointerException on getProcess

[antek.baran...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antek Baranski updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34187 
 
 
 
  promoted-builds plugin NullPointerException on getProcess  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antek Baranski 
 
 
 

Priority:
 
 Minor Critical 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [promoted-builds-plugin] (JENKINS-34187) promoted-builds plugin NullPointerException on getProcess

[antek.baran...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antek Baranski created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34187 
 
 
 
  promoted-builds plugin NullPointerException on getProcess  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Oleg Nenashev 
 
 
 

Components:
 

 promoted-builds-plugin 
 
 
 

Created:
 

 2016/Apr/12 8:59 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Antek Baranski 
 
 
 
 
 
 
 
 
 
 
1. Setup any style of project 2. Select [Promote immediately once the build is complete based on build parameters] 3. Add action 4. Trigger/call builds on other projects (reference a simple project) 5. Add predefined parameters. 
javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at 

[JIRA] [workflow-plugin] (JENKINS-34186) Pipeline package manager

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34186 
 
 
 
  Pipeline package manager  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 Jesse Glick 
 
 
 

Components:
 

 workflow-plugin 
 
 
 

Created:
 

 2016/Apr/12 8:58 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Oleg Nenashev 
 
 
 
 
 
 
 
 
 
 
It's a follow-up to the discussion to FOSDEM: https://docs.google.com/document/d/1yK2J_sv1ceLYYbeLzEW8VZ3HEr8AxZcZr8GhMk6gLUY/edit#heading=h.wif2w2yslznh 
It would be great to have a library manager for Pipeline. The following features would be useful: 1) Ability to develop, store and version Pipeline packages in SCM (e.g. Git) 2) Ability to share these libraries in open-source with minimal efforts from the developer and user sides 3) require() step, which loads libs and its dependencies 4) version conflict prevention engine (API deprecation, etc.) 5) Pipeline documentation visualization for packages in Pipeline editor ... 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 

[JIRA] [workflow-plugin] (JENKINS-34185) Pipeline debugger

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34185 
 
 
 
  Pipeline debugger  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 Jesse Glick 
 
 
 

Components:
 

 workflow-plugin 
 
 
 

Created:
 

 2016/Apr/12 8:53 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Oleg Nenashev 
 
 
 
 
 
 
 
 
 
 
It's a follow-up to FOSDEM. 
We need a "Pipeline Debugger", which would allow to easily attach to Pipeline, setup breakpoints and to check Pipeline context in them. Other common debugger features would be useful as well. 
Both in-Jenkins and external-IDE implementations would be useful. 
Related Jenkins 2.0 contributor summit notes: https://docs.google.com/document/d/1yK2J_sv1ceLYYbeLzEW8VZ3HEr8AxZcZr8GhMk6gLUY/edit#heading=h.wif2w2yslznh  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 

[JIRA] [github-branch-source-plugin] (JENKINS-34154) Add option to disable non-contributors PRs

[giulio.euli...@cern.ch (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Giulio Eulisse commented on  JENKINS-34154 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add option to disable non-contributors PRs  
 
 
 
 
 
 
 
 
 
 
Ok. I guess env.CHANGE_AUTHOR is what I was lacking. Where is the documentation for all the possible env.* variables?  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [campfire-plugin] (JENKINS-34184) Campfire plugin fails to send notification when using Folder or Multi-Branch project

[jess...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Bowes created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34184 
 
 
 
  Campfire plugin fails to send notification when using Folder or Multi-Branch project  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 jenslukowski 
 
 
 

Components:
 

 campfire-plugin 
 
 
 

Created:
 

 2016/Apr/12 8:42 PM 
 
 
 

Environment:
 

 Jenkins 1.642.4, Campfire Plugin 2.7, Folders Plugin 6.7 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Jesse Bowes 
 
 
 
 
 
 
 
 
 
 
To replicate: 
 

Install the Folders Plugin
 

Install the Campfire Notification plugin and configure
 

Create a new folder
 

Within the folder, create a freestyle job 
 

Add Campfire notification as a post build action
 
 

[JIRA] [git-changelog-plugin] (JENKINS-34156) git changelog, when given 2 SHA-1s, outputs a bunch of seemingly random changes

[tomas.bjerr...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomas Bjerre commented on  JENKINS-34156 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: git changelog, when given 2 SHA-1s, outputs a bunch of seemingly random changes  
 
 
 
 
 
 
 
 
 
 
I think I found the problem, added test case for it here: https://github.com/tomasbjerre/git-changelog-lib/commit/ddfc0438c0fb09732162444b9dd7c2c33b60c195 But no solution yet... 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [core] (JENKINS-31162) New item categorization and dynamic choice offering

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-31162 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: New item categorization and dynamic choice offering  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Manuel Recena Path: .gitignore pom.xml http://jenkins-ci.org/commit/workflow-multibranch-plugin/c3a35eb301d7bbd73678a5f86faf4fe33deb881d Log: 

JENKINS-31162
 Upgraded cloudbees-folder dependency 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [core] (JENKINS-31162) New item categorization and dynamic choice offering

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-31162 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: New item categorization and dynamic choice offering  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Manuel Recena Path: .gitignore pom.xml src/main/java/org/jenkinsci/plugins/workflow/multibranch/WorkflowMultiBranchProject.java src/main/resources/org/jenkinsci/plugins/workflow/multibranch/Messages.properties src/main/resources/org/jenkinsci/plugins/workflow/multibranch/WorkflowMultiBranchProject/newInstanceDetail.jelly src/main/resources/org/jenkinsci/plugins/workflow/multibranch/WorkflowMultiBranchProject/newInstanceDetail.properties src/main/webapp/images/48x48/pipelinemultibranchproject.png http://jenkins-ci.org/commit/workflow-multibranch-plugin/46baba62e37779fc4a90792a42046629e578a1b1 Log: Merge pull request #1 from recena/master 


JENKINS-31162
 Support for Item categorization for MultiBranchProjects 
Compare: https://github.com/jenkinsci/workflow-multibranch-plugin/compare/0d311cdc4595...46baba62e377 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [core] (JENKINS-31162) New item categorization and dynamic choice offering

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-31162 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: New item categorization and dynamic choice offering  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: recena Path: pom.xml src/main/java/org/jenkinsci/plugins/workflow/multibranch/WorkflowMultiBranchProject.java src/main/resources/org/jenkinsci/plugins/workflow/multibranch/Messages.properties src/main/resources/org/jenkinsci/plugins/workflow/multibranch/WorkflowMultiBranchProject/newInstanceDetail.jelly src/main/resources/org/jenkinsci/plugins/workflow/multibranch/WorkflowMultiBranchProject/newInstanceDetail.properties src/main/webapp/images/48x48/pipelinemultibranchproject.png http://jenkins-ci.org/commit/workflow-multibranch-plugin/09d0808ab85911fcb4efcb1162f8d779ed21 Log: 

JENKINS-31162
 Support for Item categorization for MultiBranchProjects 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [pipeline-stage-view-plugin] (JENKINS-34038) New flow analyzer algorithm in pipeline stage view based on a visitor pattern

[svano...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sam Van Oort updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34038 
 
 
 
  New flow analyzer algorithm in pipeline stage view based on a visitor pattern  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sam Van Oort 
 
 
 

Labels:
 
 api  performance 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [docker-workflow-plugin] (JENKINS-33962) docker.inside broken on OSX

[dweom...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jacob Blain Christen commented on  JENKINS-33962 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: docker.inside broken on OSX  
 
 
 
 
 
 
 
 
 
 
As noted on 

https://issues.jenkins-ci.org/browse/JENKINS-33632?focusedCommentId=254211=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-254211
, I am seeing this on 1.642.2 with pipeline/workflow updates prior to the 2.0 split and docker-workflow 1.4. Invoking the command manually that jenkins is invoking and delving into the container, I see that the mounted volumes are showing up as owned by root. I wonder if the 1.9 client going against the 1.10 server is causing this. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [docker-workflow-plugin] (JENKINS-33962) docker.inside broken on OSX

[dweom...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jacob Blain Christen edited a comment on  JENKINS-33962 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: docker.inside broken on OSX  
 
 
 
 
 
 
 
 
 
 As noted on [ JENKINS-33632| https://issues.jenkins-ci.org/browse/JENKINS-33632?focusedCommentId=254211=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-254211 |JENKINS-33632 ], I am seeing this on 1.642.2 with pipeline/workflow updates prior to the 2.0 split and docker-workflow 1.4. Invoking the command manually that jenkins is invoking and delving into the container, I see that the mounted volumes are showing up as owned by root. I wonder if the 1.9 client going against the 1.10 server is causing this. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [docker-workflow-plugin] (JENKINS-33632) docker.inside broken

[dweom...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jacob Blain Christen commented on  JENKINS-33632 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: docker.inside broken  
 
 
 
 
 
 
 
 
 
 
I am seeing this on 1.642.2 with pipeline/workflow updates prior to the 2.0 split and doker-workflow 1.4.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [embeddable-build-status-plugin] (JENKINS-33911) Allow Embeddable build status for Folders

[jgl...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick assigned an issue to Antonio Muñiz 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33911 
 
 
 
  Allow Embeddable build status for Folders  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Component/s:
 
 cloudbees-folder-plugin 
 
 
 

Labels:
 
 plugin folders 
 
 
 

Assignee:
 
 Jesse Glick Antonio Muñiz 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [pipeline-stage-view-plugin] (JENKINS-34038) New flow analyzer algorithm in pipeline stage view based on a visitor pattern

[jgl...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34038 
 
 
 
  New flow analyzer algorithm in pipeline stage view based on a visitor pattern  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Labels:
 
 api 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [ssh-slaves-plugin] (JENKINS-33021) trilead ssh MAC and key exchange algorithms severely outdated

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev edited a comment on  JENKINS-33021 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: trilead ssh MAC and key exchange algorithms severely outdated  
 
 
 
 
 
 
 
 
 
 I see the same issue when I connect the clean Ubuntu Server 14.04 .4  LTS with the latest openssh-server from the update center 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [ssh-slaves-plugin] (JENKINS-33021) trilead ssh MAC and key exchange algorithms severely outdated

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev commented on  JENKINS-33021 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: trilead ssh MAC and key exchange algorithms severely outdated  
 
 
 
 
 
 
 
 
 
 
In my case I had to weaken the security settings and to use the common RSA algorithm 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [build-name-setter-plugin] (JENKINS-34181) NullPointerException in BuildNameSetter.setup

[cody.s....@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Cody Lee commented on  JENKINS-34181 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: NullPointerException in BuildNameSetter.setup  
 
 
 
 
 
 
 
 
 
 
Update: The NPE comes from setting the build name before the build starts and using environment variables that are set as a part of the build name. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [git-changelog-plugin] (JENKINS-34156) git changelog, when given 2 SHA-1s, outputs a bunch of seemingly random changes

[tomas.bjerr...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomas Bjerre commented on  JENKINS-34156 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: git changelog, when given 2 SHA-1s, outputs a bunch of seemingly random changes  
 
 
 
 
 
 
 
 
 
 
What does your repo look like? What is the output of: 

 

git log --graph --full-history --all --color --date=short --pretty=format:"%Cred%x09%h %Creset%ad%Cgreen%d %Creset %s %C(bold)(%an)%Creset"
 

 
What were the values you used as from and to commits? 
What did your template look like? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [clone-workspace-plugin] (JENKINS-34182) Special clone case for multi-configuration build handling

[mikel...@aol.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 MICHAEL LUPO created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34182 
 
 
 
  Special clone case for multi-configuration build handling  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 Andrew Bayer 
 
 
 

Components:
 

 clone-workspace-plugin 
 
 
 

Created:
 

 2016/Apr/12 6:14 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 MICHAEL LUPO 
 
 
 
 
 
 
 
 
 
 
When a user creates a multi configuration build, then wants to archive the entire workspace, the plugin only archives the sub-configuration. 
For example let's call it, "My_Jenkins_Multiconfig" which is effectively the parent level job, and builds 2 configurations using the Configuration Matrix plugin. I have two configs. Release and Debug. What happens is that I get two builds in the jenkins workspace that look like this: My_Jenkins_Multiconfig/label//Debug My_Jenkins_Multiconfig/label//Release 
You end up with two implied job names to match each of those configurations. This is as expected. So far so good. 
The clone workspace plugin will then archive TWO clones. The one for release and the one for debug. This is working as designed.  
The special case here is that I'd like to archive the parent level job so that the clone workspace plugin has the option to clone outside of the loop (for lack of a better term) for each config in the matrix. 
The result is that I end up with one clone of that contains both build outputs. i.e. cloned at this level, "My_Jenkins_Multiconfig" instead of "My_Jenkins_Multiconfig/local//Release" 
Any workaround suggestions to this would be 

[JIRA] [git-changelog-plugin] (JENKINS-34156) git changelog, when given 2 SHA-1s, outputs a bunch of seemingly random changes

[tomas.bjerr...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomas Bjerre assigned an issue to Tomas Bjerre 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34156 
 
 
 
  git changelog, when given 2 SHA-1s, outputs a bunch of seemingly random changes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tomas Bjerre 
 
 
 

Assignee:
 
 Paul Wellner Bou Tomas Bjerre 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [git-changelog-plugin] (JENKINS-34155) Git Changelog Plugin does not seem to take short SHA-1s as input

[tomas.bjerr...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomas Bjerre resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34155 
 
 
 
  Git Changelog Plugin does not seem to take short SHA-1s as input  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tomas Bjerre 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [github-branch-source-plugin] (JENKINS-34120) Do not suppress unmergeable PRs

[magn...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 magnayn commented on  JENKINS-34120 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Do not suppress unmergeable PRs  
 
 
 
 
 
 
 
 
 
 
When I looked in github, as far as it was concerned it was still mergeable; the only check that had failed (and the only one we use) was the Jenkins build. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [build-name-setter-plugin] (JENKINS-34181) NullPointerException in BuildNameSetter.setup

[cody.s....@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Cody Lee updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34181 
 
 
 
  NullPointerException in BuildNameSetter.setup  
 
 
 
 
 
 
 
 
 

Change By:
 
 Cody Lee 
 
 
 
 
 
 
 
 
 
 Similar NPE on all of our jobs using build name setter: {{ ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-us...@googlegroups.comjava.lang.NullPointerException at org.jenkinsci.plugins.buildnamesetter.BuildNameSetter.setUp(BuildNameSetter.java:41) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:655) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)project=hudson.maven.MavenModuleSet@19c9e8a[player-services-test]project.getModules()=[hudson.maven.MavenModule@1209012[player-services-test/com.sonos.services:player-services-test][player-services-test/com.sonos.services:player-services-test][relativePath:], hudson.maven.MavenModule@23fe5f[player-services-test/com.sonos.services:sonos-test][player-services-test/com.sonos.services:sonos-test][relativePath:sonos-test], hudson.maven.MavenModule@89efd9[player-services-test/com.sonos.services:sonos-test-dependencies][player-services-test/com.sonos.services:sonos-test-dependencies][relativePath:sonos-test-dependencies]]project.getRootModule()=hudson.maven.MavenModule@1209012[player-services-test/com.sonos.services:player-services-test][player-services-test/com.sonos.services:player-services-test][relativePath:]FATAL: nulljava.lang.NullPointerException at org.jenkinsci.plugins.buildnamesetter.BuildNameSetter.setUp(BuildNameSetter.java:41) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:655) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) }} Build Name:  {{ #${BUILD_NUMBER}-${ENV,var="STREAM"} }} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 

[JIRA] [build-name-setter-plugin] (JENKINS-34181) NullPointerException in BuildNameSetter.setup

[cody.s....@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Cody Lee updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34181 
 
 
 
  NullPointerException in BuildNameSetter.setup  
 
 
 
 
 
 
 
 
 

Change By:
 
 Cody Lee 
 
 
 
 
 
 
 
 
 
 Similar NPE on all of our jobs using build name setter: {{ ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-us...@googlegroups.comjava.lang.NullPointerException at org.jenkinsci.plugins.buildnamesetter.BuildNameSetter.setUp(BuildNameSetter.java:41) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:655) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)project=hudson.maven.MavenModuleSet@19c9e8a[player-services-test]project.getModules()=[hudson.maven.MavenModule@1209012[player-services-test/com.sonos.services:player-services-test][player-services-test/com.sonos.services:player-services-test][relativePath:], hudson.maven.MavenModule@23fe5f[player-services-test/com.sonos.services:sonos-test][player-services-test/com.sonos.services:sonos-test][relativePath:sonos-test], hudson.maven.MavenModule@89efd9[player-services-test/com.sonos.services:sonos-test-dependencies][player-services-test/com.sonos.services:sonos-test-dependencies][relativePath:sonos-test-dependencies]]project.getRootModule()=hudson.maven.MavenModule@1209012[player-services-test/com.sonos.services:player-services-test][player-services-test/com.sonos.services:player-services-test][relativePath:]FATAL: nulljava.lang.NullPointerException at org.jenkinsci.plugins.buildnamesetter.BuildNameSetter.setUp(BuildNameSetter.java:41) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:655) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) }} Build Name: #${BUILD_NUMBER}-${ENV,var="STREAM"} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
   

[JIRA] [build-name-setter-plugin] (JENKINS-34181) NullPointerException in BuildNameSetter.setup

[cody.s....@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Cody Lee updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34181 
 
 
 
  NullPointerException in BuildNameSetter.setup  
 
 
 
 
 
 
 
 
 

Change By:
 
 Cody Lee 
 
 
 
 
 
 
 
 
 
 Similar NPE on all of our jobs using build name setter: {{ ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-us...@googlegroups.comjava.lang.NullPointerException at org.jenkinsci.plugins.buildnamesetter.BuildNameSetter.setUp(BuildNameSetter.java:41) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:655) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)project=hudson.maven.MavenModuleSet@19c9e8a[player-services-test]project.getModules()=[hudson.maven.MavenModule@1209012[player-services-test/com.sonos.services:player-services-test][player-services-test/com.sonos.services:player-services-test][relativePath:], hudson.maven.MavenModule@23fe5f[player-services-test/com.sonos.services:sonos-test][player-services-test/com.sonos.services:sonos-test][relativePath:sonos-test], hudson.maven.MavenModule@89efd9[player-services-test/com.sonos.services:sonos-test-dependencies][player-services-test/com.sonos.services:sonos-test-dependencies][relativePath:sonos-test-dependencies]]project.getRootModule()=hudson.maven.MavenModule@1209012[player-services-test/com.sonos.services:player-services-test][player-services-test/com.sonos.services:player-services-test][relativePath:]FATAL: nulljava.lang.NullPointerException at org.jenkinsci.plugins.buildnamesetter.BuildNameSetter.setUp(BuildNameSetter.java:41) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:655) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) }} Build Name: #${BUILD_NUMBER}-${ENV,var="STREAM"} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
   

[JIRA] [build-name-setter-plugin] (JENKINS-34181) NullPointerException in BuildNameSetter.setup

[cody.s....@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Cody Lee created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34181 
 
 
 
  NullPointerException in BuildNameSetter.setup  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Lev Mishin 
 
 
 

Components:
 

 build-name-setter-plugin 
 
 
 

Created:
 

 2016/Apr/12 5:58 PM 
 
 
 

Environment:
 

 Jenkins 1.642.4, build-name-setter 1.6.0 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Cody Lee 
 
 
 
 
 
 
 
 
 
 
Similar NPE on all of our jobs using build name setter: 
{{ ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-us...@googlegroups.com java.lang.NullPointerException at org.jenkinsci.plugins.buildnamesetter.BuildNameSetter.setUp(BuildNameSetter.java:41) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:655) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) project=hudson.maven.MavenModuleSet@19c9e8a[player-services-test] project.getModules()=[hudson.maven.MavenModule@1209012[player-services-test/com.sonos.services:player-services-test][player-services-test/com.sonos.services:player-services-test][relativePath:], 

[JIRA] [git-changelog-plugin] (JENKINS-34155) Git Changelog Plugin does not seem to take short SHA-1s as input

[tomas.bjerr...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomas Bjerre commented on  JENKINS-34155 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Git Changelog Plugin does not seem to take short SHA-1s as input  
 
 
 
 
 
 
 
 
 
 
Should be fixed in 1.19. I just released it, will be in the update sites within a few hours. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [git-changelog-plugin] (JENKINS-34155) Git Changelog Plugin does not seem to take short SHA-1s as input

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-34155 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Git Changelog Plugin does not seem to take short SHA-1s as input  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Tomas Bjerre Path: pom.xml http://jenkins-ci.org/commit/git-changelog-plugin/49a392944c937667d6c41c43499585d942b6b395 Log: JENKINS-34155 Support short SHA 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [core] (JENKINS-34174) Jenkins 2.0-rc1 - Getting started hangs installing plugins

[russell.gal...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russell Gallop commented on  JENKINS-34174 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins 2.0-rc1 - Getting started hangs installing plugins  
 
 
 
 
 
 
 
 
 
 
I wonder if there is a deadlock somewhere in the plugin download code due to higher latency. My ping times to updates.jenkins-ci.org are about 100ms. 
Is there an option to download plugins sequentially? Or can I specify a mirror with a lower ping? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [parameterized-trigger-plugin] (JENKINS-28908) Subjob completion not detected

[m...@milijan.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Milijan Mudrinic commented on  JENKINS-28908 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Subjob completion not detected  
 
 
 
 
 
 
 
 
 
 
I have the same issue but I am unable to enable the Maven Integration plugin which I presume is what you mean.  The pop-up message suggest that the Javadoc Plugin plugin in disabled, which I can also confirm but I don't have an option to enable it as it is greyed out. I am running 1.655 jenkins with quite a lot of other plugins (inc those mentioned in this bug report). I'd like to get the warning pluging working so any suggestions would be much appreciated. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [github-branch-source-plugin] (JENKINS-33530) Pull Requests "submitted from origin repository, skipping" not clear why this is skipping

[jgl...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick resolved as Duplicate 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33530 
 
 
 
  Pull Requests "submitted from origin repository, skipping" not clear why this is skipping  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Duplicate 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [github-branch-source-plugin] (JENKINS-33909) Prevent automatic trigger of of jobs once scan has created them

[jgl...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick resolved as Duplicate 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33909 
 
 
 
  Prevent automatic trigger of of jobs once scan has created them  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Duplicate 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [github-branch-source-plugin] (JENKINS-34154) Add option to disable non-contributors PRs

[jgl...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick resolved as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Untrusted PRs are built, but using the Jenkinsfile from the base branch, disregarding any modifications to the Jenkinsfile made in the PR. 
You can inspect env.CHANGE_AUTHOR etc. if you want. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-34154 
 
 
 
  Add option to disable non-contributors PRs  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Not A Defect 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [github-branch-source-plugin] (JENKINS-34180) Improve the status posted to GitHub when Jenkins validates the branch from a PR merge

[pw...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrick Wolf created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34180 
 
 
 
  Improve the status posted to GitHub when Jenkins validates the branch from a PR merge  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Jesse Glick 
 
 
 

Attachments:
 

 PRMergeToBranch.png 
 
 
 

Components:
 

 github-branch-source-plugin 
 
 
 

Created:
 

 2016/Apr/12 4:56 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Patrick Wolf 
 
 
 
 
 
 
 
 
 
 
confusion with the master branch status posted by Jenkins after a PR is merged: Refer the attached screenshots: The “details” of the merged pull request commit (hash b688… in this case) has a link that points to the last pull request build (PR/2 in this case) It was observed that the master branch with commit b688… was built, but the results are pointing to the PR validation link on Jenkins. (validated with CJP and Jenkins 2.0-alpha-3, plugins - GitHub Organization Folder 1.2, GitHub Branch Source 1.4, GitHub 1.17.1) 
detail - 1- Create pull request w/commit b978… Jenkins PR/1 builds Jenkins job/build Link added to PR ok 2- Make change on PR source branch PR/2 builds (w/commit 2719…) starts and completes Jenkins PR job's build Link added to github pull request ok 3- Pull request is merged which creates commit b688… Jenkins builds master branch build is good But the last link added to the pull result points to the PR/2 result, not the master branch build result. 
 

[JIRA] [github-branch-source-plugin] (JENKINS-34120) Do not suppress unmergeable PRs

[jgl...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34120 
 
 
 
  Do not suppress unmergeable PRs  
 
 
 
 
 
 
 
 
 
 
I thought this was already filed, but cannot find it now. Anyway, the suggested resolution is simple: do not check mergeability during branch indexing, so always create the branch project; when performing the build, if there is a merge failure, fail the build. 
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Summary:
 
 Do not suppress unmergeable PRs  that fail builds immediately disappear from the build list 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [github-branch-source-plugin] (JENKINS-34120) PRs that fail builds immediately disappear from the build list

[jgl...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Dubious. The stated error message indicates that GitHub considers the PR to not be mergeable without conflict. Has nothing to do with Jenkins build results. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-34120 
 
 
 
  PRs that fail builds immediately disappear from the build list  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Component/s:
 
 workflow-plugin 
 
 
 

Assignee:
 
 Jesse Glick 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [github-branch-source-plugin] (JENKINS-33637) Github PR's ignore Github Org Folder Orphan Strategy

[jgl...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick resolved as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Behaving as designed, since the orphan policy on an organization folder applies to repositories, not branches; but JENKINS-33819 would allow you to configure both policies. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-33637 
 
 
 
  Github PR's ignore Github Org Folder Orphan Strategy  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Not A Defect 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [build-pipeline-plugin] (JENKINS-33935) Can't rerun a build

[rpimen...@planview.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Pimentel commented on  JENKINS-33935 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Can't rerun a build  
 
 
 
 
 
 
 
 
 
 
Same problem here on 1.656 using 1.5.2 plugin. Version 1.5.1 is working nicely on Jenkins 1.643. Will downgrade Jenkins until fix is released. Thanks. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [core] (JENKINS-34174) Jenkins 2.0-rc1 - Getting started hangs installing plugins

[russell.gal...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russell Gallop updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34174 
 
 
 
  Jenkins 2.0-rc1 - Getting started hangs installing plugins  
 
 
 
 
 
 
 
 
 
 
Tail of log 

 

←[0mApr 12, 2016 4:51:25 PM jenkins.InitReactorRunner$1 onAttained
INFO: Started initialization
Apr 12, 2016 4:51:25 PM jenkins.InitReactorRunner$1 onAttained
INFO: Listed all plugins
Apr 12, 2016 4:51:25 PM jenkins.InitReactorRunner$1 onAttained
INFO: Prepared all plugins
Apr 12, 2016 4:51:25 PM jenkins.InitReactorRunner$1 onAttained
INFO: Started all plugins
Apr 12, 2016 4:51:25 PM jenkins.InitReactorRunner$1 onAttained
INFO: Augmented all extensions
Apr 12, 2016 4:51:25 PM jenkins.InitReactorRunner$1 onAttained
INFO: Loaded all jobs
Apr 12, 2016 4:51:25 PM jenkins.InitReactorRunner$1 onAttained
INFO: Completed initialization
Apr 12, 2016 4:51:25 PM hudson.ClassicPluginStrategy updateDependency
INFO: Updated dependency of matrix-auth
Apr 12, 2016 4:51:25 PM hudson.PluginManager dynamicLoad
INFO: Plugin cloudbees-folder:5.7 dynamically installed
Apr 12, 2016 4:51:25 PM hudson.model.UpdateCenter$DownloadJob run
INFO: Installation successful: Folders Plugin
Apr 12, 2016 4:51:25 PM hudson.model.UpdateCenter$DownloadJob run
INFO: Starting the installation of Credentials Plugin on behalf of admin
Apr 12, 2016 4:51:26 PM hudson.model.UpdateCenter$UpdateCenterConfiguration down
load
INFO: Downloading Credentials Plugin
Apr 12, 2016 4:51:27 PM hudson.PluginManager dynamicLoad
INFO: Attempting to dynamic load C:\j2\plugins\credentials.jpi
Apr 12, 2016 4:51:31 PM jenkins.InitReactorRunner$1 onAttained
INFO: Started initialization
Apr 12, 2016 4:51:31 PM jenkins.InitReactorRunner$1 onAttained
INFO: Listed all plugins
Apr 12, 2016 4:51:31 PM jenkins.InitReactorRunner$1 onAttained
INFO: Prepared all plugins
Apr 12, 2016 4:51:31 PM jenkins.InitReactorRunner$1 onAttained
INFO: Started all plugins
Apr 12, 2016 4:51:31 PM jenkins.InitReactorRunner$1 onAttained
INFO: Augmented all extensions
Apr 12, 2016 4:51:31 PM jenkins.InitReactorRunner$1 onAttained
INFO: Loaded all jobs
Apr 12, 2016 4:51:31 PM jenkins.InitReactorRunner$1 onAttained
INFO: Completed initialization
Apr 12, 2016 4:51:31 PM hudson.ClassicPluginStrategy updateDependency
INFO: Updated dependency of cloudbees-folder
Apr 12, 2016 4:51:31 PM hudson.PluginManager dynamicLoad
INFO: Plugin credentials:1.27 dynamically installed
Apr 12, 2016 4:51:31 PM hudson.model.UpdateCenter$DownloadJob run
INFO: Installation successful: Credentials Plugin
Apr 12, 2016 4:51:31 PM hudson.model.UpdateCenter$DownloadJob run
INFO: Starting the installation of Structs Plugin on behalf of admin
Apr 12, 2016 4:51:32 PM hudson.model.UpdateCenter$UpdateCenterConfiguration down
load
INFO: Downloading Structs Plugin
Apr 12, 2016 4:56:42 PM hudson.model.AsyncPeriodicWork$1 run
INFO: Started Fingerprint cleanup
Apr 12, 2016 4:56:42 PM hudson.model.AsyncPeriodicWork$1 run
INFO: Finished Fingerprint cleanup. 2 ms
 

 
 
 
 
 
 
 
 
 
 

Change By:
 
 Russell Gallop 
 
   

[JIRA] [core] (JENKINS-34174) Jenkins 2.0-rc1 - Getting started hangs installing plugins

[russell.gal...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russell Gallop commented on  JENKINS-34174 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins 2.0-rc1 - Getting started hangs installing plugins  
 
 
 
 
 
 
 
 
 
 
Okay, I have a script which is successfully downloading plugins from https://updates.jenkins-ci.org/latest/. It has successfully downloaded about 50 and still going. Jenkins seems to have stopped after getting 8. I don't think I've been redirected to a mirror. 
Tried a different browser (in case the problem is browser side) and get the same thing. 
I attached a thread dump to the initial report, corresponding to the screenshot. 
I'll attach threadDump2.txt. This is having downloaded (Ant, OWASP, build timeout, Folders, LDAP, Mailer, Matrix auth and PAM auth). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [delivery-pipeline-plugin] (JENKINS-33594) Rebuilding broken in Jenkins ver. 1.653

[rpimen...@planview.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Pimentel commented on  JENKINS-33594 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Rebuilding broken in Jenkins ver. 1.653  
 
 
 
 
 
 
 
 
 
 
Apologies. Just realized this bug was tied to Delivery Pipeline plugin. I also have that plugin installed, but my issue is tied to Build Pipeline plugin. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [msbuild-plugin] (JENKINS-24132) MSBuild Output encoding vs Jenkins' encoding vs Browser Encoding

[dncarre...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Duarte Carreira edited a comment on  JENKINS-24132 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: MSBuild Output encoding vs Jenkins' encoding vs Browser Encoding  
 
 
 
 
 
 
 
 
 
 Just adding my solution in case anyone is stuck with this.I had the same issue running psql queries with some characters.What ended working was setting in my "Windows batch command" jobs  was setting  the code page to the  same code  as Jenkins' default 1252:{{...set PGCLIENTENCODING="WIN1252"chcp 1252...}}The relevant part is the chcp 1252 command. This corresponds to ANSI Latin 1; Western European (Windows), according to this: [https://msdn.microsoft.com/en-us/library/windows/desktop/dd317756(v=vs.85).aspx].The PGCLIENTENCODING is specific to psql so applies only to my specific case.Hope this helps. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [msbuild-plugin] (JENKINS-24132) MSBuild Output encoding vs Jenkins' encoding vs Browser Encoding

[dncarre...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Duarte Carreira commented on  JENKINS-24132 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: MSBuild Output encoding vs Jenkins' encoding vs Browser Encoding  
 
 
 
 
 
 
 
 
 
 
Just adding my solution in case anyone is stuck with this. 
I had the same issue running psql queries with some characters. 
What ended working was setting in my "Windows batch command" jobs was setting the code page to the as Jenkins' default 1252: 
{{... set PGCLIENTENCODING="WIN1252" chcp 1252 ...}} 
The relevant part is the chcp 1252 command. This corresponds to ANSI Latin 1; Western European (Windows), according to this: https://msdn.microsoft.com/en-us/library/windows/desktop/dd317756(v=vs.85).aspx. 
The PGCLIENTENCODING is specific to psql so applies only to my specific case. 
Hope this helps. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [delivery-pipeline-plugin] (JENKINS-33594) Rebuilding broken in Jenkins ver. 1.653

[rpimen...@planview.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Pimentel commented on  JENKINS-33594 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Rebuilding broken in Jenkins ver. 1.653  
 
 
 
 
 
 
 
 
 
 
Not sure if I need to reopen this or create a new issue. The symptoms are nearly identical, except I am not sure of the OP's meaning of "A new build is started for the step's job, but it's not visible in the delivery pipeline view." I also see that a new build is started (or at least it tries to start a new build), but there is no indication of a new build either in the pipeline view, or in the history of that job. The job is never triggered. I am running Jenkins 1.656. I first encountered issue 33591 (unable to trigger manual build in pipeline), because I was running version 1.5.1 of the plugin. I upgraded the plugin to 1.5.2, am able to manually trigger builds in the pipeline, but not able to retry builds in the pipeline. Thanks! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [core] (JENKINS-34174) Jenkins 2.0-rc1 - Getting started hangs installing plugins

[db...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-34174 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins 2.0-rc1 - Getting started hangs installing plugins  
 
 
 
 
 
 
 
 
 
 
The URL /threadDump should be manually accessible and tell us what Jenkins is doing while showing this screen. (https://wiki.jenkins-ci.org/display/JENKINS/Obtaining+a+thread+dump) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [pipeline-stage-view-plugin] (JENKINS-33700) Visualization color should not be green for an UNSTABLE build

[svano...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sam Van Oort assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33700 
 
 
 
  Visualization color should not be green for an UNSTABLE build  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sam Van Oort 
 
 
 

Assignee:
 
 Antonio Muñiz 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [pipeline-stage-view-plugin] (JENKINS-33700) Visualization color should not be green for an UNSTABLE build

[svano...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sam Van Oort commented on  JENKINS-33700 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Visualization color should not be green for an UNSTABLE build  
 
 
 
 
 
 
 
 
 
 
The other issue here is that the enum used in APIs to report build statuses does not actually have a notion of unstable at this point:  
https://github.com/jenkinsci/pipeline-stage-view-plugin/blob/master/rest-api/src/main/java/com/cloudbees/workflow/rest/external/StatusExt.java 
Easy enough to add, but we'll need to double check that anything depending on the StatusExt can handle an unrecognized Status (shouldn't be an issue, but worth verifying just in case).  
Thankfully, we have two ways to get directly at the status, which are accessible to the RunExt object upon creation: both the WorkFlowRun and the concrete implementation of its FlowExecution (CPSFlowExecution) provide a getResult() method. Then we can just do 'myThing.getResult() == Result.UNSTABLE' when creating the RunExt.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [core] (JENKINS-34174) Jenkins 2.0-rc1 - Getting started hangs installing plugins

[db...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-34174 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins 2.0-rc1 - Getting started hangs installing plugins  
 
 
 
 
 
 
 
 
 
 
Ping isn't enough. May be a problem related to mirrorbrain – try to download stuff from that site, e.g. plugin files in http://updates.jenkins-ci.org/latest/ – note which mirror you get HTTP redirected to (if any).  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [junit-attachments-plugin] (JENKINS-34179) Support xUnit for publishing attachments

[as.fireflas...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ashley Straw created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34179 
 
 
 
  Support xUnit for publishing attachments  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 huybrechts 
 
 
 

Components:
 

 junit-attachments-plugin 
 
 
 

Created:
 

 2016/Apr/12 3:25 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Ashley Straw 
 
 
 
 
 
 
 
 
 
 
It'd be very helpful if this could be extended to support the xUnit plugin's Junit parsing as well.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 

[JIRA] [core] (JENKINS-34174) Jenkins 2.0-rc1 - Getting started hangs installing plugins

[russell.gal...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russell Gallop commented on  JENKINS-34174 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins 2.0-rc1 - Getting started hangs installing plugins  
 
 
 
 
 
 
 
 
 
 
> Is your internet connection unstable? 
I don't have any other problems with it. 
> While this plugin download is going on, are you able to reach e.g. updates.jenkins-ci.org from the same host? 
I can reliably ping updates.jenkins-ci.org while it hangs. 
I did have both wired and wireless network connections enabled but I've just recreated it with just wired. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [vmware-vrealize-orchestrator-plugin] (JENKINS-34178) There *may* be a problem with the vm@VC:VirtualMachine parameter name.

[bob.krae...@agfa.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bob Kraemer created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34178 
 
 
 
  There *may* be a problem with the vm@VC:VirtualMachine parameter name.   
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Agila Govindaraju 
 
 
 

Components:
 

 vmware-vrealize-orchestrator-plugin 
 
 
 

Created:
 

 2016/Apr/12 3:02 PM 
 
 
 

Environment:
 

 Jenkins Master (CentOS) 1.609.1 LTS  vmware-realize-orchestrator-plugin version 2.0  Java version: JDK1.8  Orchestrator vApp version 7.0.1 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Bob Kraemer 
 
 
 
 
 
 
 
 
 
 
There may be a problem with the vm@VC:VirtualMachine parameter name. As an example, I have two jenkins jobs, each job passing a single parameter to it's linked orchestrator workflow (Copy file from vCO to guest). The only difference between the two scenarios is that in one case (the failure) Jenkins uses the vm@VC:VirtualMachine parameter name as the sole input to the orchestrator workflow. In the case that succeeds, the VM variable is set in the orchestrator workflow as an attribute, and the jenkins job passes another variable, instead (the VM password) as the sole parameter passed from jenkins to orchestrator. Other than the change to the single input type passed by jenkins (vm@VC:VirtualMachine parameter versus VM Password) all other aspects appear identical. When I manually run the orchestrator workflow from the failed scenario in workflow designer, the workflow runs fine after specifying the VC:VirtualMachine input parameter.  
  

[JIRA] [github-organization-folder-plugin] (JENKINS-34176) Trigger when Github tag is pushed

[jenkins-j...@mycloudand.me (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pete Wagner created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34176 
 
 
 
  Trigger when Github tag is pushed  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 Kohsuke Kawaguchi 
 
 
 

Components:
 

 github-organization-folder-plugin 
 
 
 

Created:
 

 2016/Apr/12 3:01 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Pete Wagner 
 
 
 
 
 
 
 
 
 
 
As a github-organization-folder-plugin user, I want to trigger a pipeline when a Github tag/release is created, So that I can perform special release tasks. 
i.e. when 1.0.0 is tagged, publish project:1.0.0 docker image. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 

[JIRA] [workflow-plugin] (JENKINS-34177) Pipeline Multibranch Not Cleaning Workspaces

[pi...@pioto.org (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mike Kelly created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34177 
 
 
 
  Pipeline Multibranch Not Cleaning Workspaces  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Jesse Glick 
 
 
 

Components:
 

 workflow-plugin 
 
 
 

Created:
 

 2016/Apr/12 3:01 PM 
 
 
 

Labels:
 

 workflow 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Mike Kelly 
 
 
 
 
 
 
 
 
 
 
When working with many short-lived feature branches, Jenkins can start to eat up a lot of disk space by leaving old workspaces around from old builds. 
This seems to be especially true with the Pipeline Multibranch Plugin. When that plugin deletes the job for a branch when the branch is deleted, it should simultaneously clean up any of the workspaces created for that branch job (e.g. "feature-foo", "feature-foo@2", "feature-foo@3", etc). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
   

[JIRA] [github-branch-source-plugin] (JENKINS-33305) Ability to configure branch name filters at organization folder level

[afernan...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Armando Fernandez started work on  JENKINS-33305 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Armando Fernandez 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [github-branch-source-plugin] (JENKINS-33305) Ability to configure branch name filters at organization folder level

[afernan...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Armando Fernandez assigned an issue to Armando Fernandez 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33305 
 
 
 
  Ability to configure branch name filters at organization folder level  
 
 
 
 
 
 
 
 
 

Change By:
 
 Armando Fernandez 
 
 
 

Assignee:
 
 Armando Fernandez 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [github-branch-source-plugin] (JENKINS-33305) Ability to configure branch name filters at organization folder level

[afernan...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Armando Fernandez commented on  JENKINS-33305 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Ability to configure branch name filters at organization folder level  
 
 
 
 
 
 
 
 
 
 
Filed PR 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [vmware-vrealize-orchestrator-plugin] (JENKINS-34175) It does not seem possible to execute an orchestrator workflow that requires no user input.

[bob.krae...@agfa.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bob Kraemer created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34175 
 
 
 
  It does not seem possible to execute an orchestrator workflow that requires no user input.   
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Agila Govindaraju 
 
 
 

Components:
 

 vmware-vrealize-orchestrator-plugin 
 
 
 

Created:
 

 2016/Apr/12 2:43 PM 
 
 
 

Environment:
 

 Jenkins Master (CentOS) 1.609.1 LTS  vmware-realize-orchestrator-plugin version 2.0  Java version: JDK1.8  Orchestrator vApp version 7.0.1 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Bob Kraemer 
 
 
 
 
 
 
 
 
 
 
It does not seem possible to execute an orchestrator workflow that requires no user input. (Example = all orchestrator workflow inputs are set as attributes). When the plugin has nothing to pass, the jenkins console reports there has been a "HTTP/1.1 400 Bad Request" 
Jenkins Console Output: 07:35:15 Started by user anonymous 07:35:15 [EnvInject] - Loading node environment variables. 07:35:15 Building remotely on anonymous in workspace F:\jenkins\workspace\anonymous_orchestrator_jenkins_send_notification_null 07:35:16 Starting Orchestrator workflow execution : a18ceeea-e29e-4d04-8f73-4733e63f76d4 07:35:19 FATAL: Server responded with status code HTTP/1.1 400 Bad Request 07:35:19 java.io.IOException: Server responded with status code HTTP/1.1 400 Bad Request 07:35:19 at com.vmware.vro.jenkins.plugin.OrchestratorCallable.call(OrchestratorCallable.java:66) 07:35:19 at 

[JIRA] [core] (JENKINS-34167) Add Build Step -> Execute Shell returns 500 from render

[jbram...@corelogic.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Justin Bramley commented on  JENKINS-34167 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add Build Step -> Execute Shell returns 500 from render  
 
 
 
 
 
 
 
 
 
 
We're running apache as the frontend with tomcat behind it, so in the words of our SA, "technically yes." The URL in jenkins.model.JenkinsLocationConfiguration.xml is the URL I use to access the site. No other resources return 500 when loading the configuration form (or anywhere else that I've seen). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [core] (JENKINS-34118) long page load times in pluginManager/available

[db...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-34118 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: long page load times in pluginManager/available  
 
 
 
 
 
 
 
 
 
 
Cannot reproduce in 2.0-rc-1. James Nord Could you take a thread dump or two while the page is loading? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [core] (JENKINS-34164) Jenkins web interface in need of usability and aesthetic improvements

[jenk...@alper.nl (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alper Cugun commented on  JENKINS-34164 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins web interface in need of usability and aesthetic improvements  
 
 
 
 
 
 
 
 
 
 
Maybe then make it actionable? That facelift sounds like a good idea and I look forward to seeing that and a lot more in an upcoming version. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [core] (JENKINS-34146) Disabled parametrized jobs could be build from build URL

[db...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck edited a comment on  JENKINS-34146 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Disabled parametrized jobs could be build from build URL  
 
 
 
 
 
 
 
 
 
 Cannot reproduce on 1.642.2. While the page "This build requires parameters" appears, submitting the form does not result in a queue item.{noformat}Apr 12, 2016 4:31:16 PM hudson.model.Executor finish1SEVERE: Executor threw an exceptionjava.lang.Error: The null Executable has been created for hudson.model.queue.WorkUnit@35711043[work=jobname]. The task cannot be executed at hudson.model.Executor.run(Executor.java:397){ quote noformat }This could probably be improved, but Jenkins does not expose the reported problem (anymore).Please make sure issues you report actually occur in current versions of Jenkins. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [core] (JENKINS-34146) Disabled parametrized jobs could be build from build URL

[db...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck resolved as Cannot Reproduce 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Cannot reproduce on 1.642.2. While the page "This build requires parameters" appears, submitting the form does not result in a queue item. 

 
 

 
Apr 12, 2016 4:31:16 PM hudson.model.Executor finish1 SEVERE: Executor threw an exception java.lang.Error: The null Executable has been created for hudson.model.queue.WorkUnit@35711043[work=jobname]. The task cannot be executed at hudson.model.Executor.run(Executor.java:397) 
 
This could probably be improved, but Jenkins does not expose the reported problem (anymore). 
Please make sure issues you report actually occur in current versions of Jenkins. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-34146 
 
 
 
  Disabled parametrized jobs could be build from build URL  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Cannot Reproduce 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)