[JIRA] [text-finder-plugin] (JENKINS-3612) Allow text-finder plugin to carry out multiple searches.

2015-12-31 Thread daniel.la...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Laügt commented on  JENKINS-3612 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Allow text-finder plugin to carry out multiple searches.  
 
 
 
 
 
 
 
 
 
 
With Flexible Publish plugin, several text-finder plugins can be added to the project. For example with this solution, you can have a regular _expression_ for marking the build as failed and a regular _expression_ for marking the build as unstable. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated

2015-12-31 Thread emilvar...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 E Varona commented on  JENKINS-20941 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Stored git credentials not used when submodule is updated  
 
 
 
 
 
 
 
 
 
 
After struggling with this for much longer than I cared for, I was not able to get the git submodules working using either ssh or https from my EC2 backed Jenkins host to our private GitHub organization repo. I tried every suggestion in this post with no luck. 
What did however work although it's a far less than ideal solution, is to put the credentials in `~/.netrc` on both the master and slaves. Now not only do my configs not require an external p/w but my submodule sync is working. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated

2015-12-31 Thread emilvar...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 E Varona edited a comment on  JENKINS-20941 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Stored git credentials not used when submodule is updated  
 
 
 
 
 
 
 
 
 
 After struggling with this for much longer than I cared for, I was not able to get the git submodules working using either ssh or https from my EC2 backed Jenkins host to our private GitHub organization repo. I tried every suggestion in this post with no luck.What did however work although it's a far less than ideal solution, is to put the credentials in  `  {{ ~/.netrc ` }}  on both the master and slaves. Now not only do my configs not require an external p/w but my submodule sync is working. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-30744) multibranch issues if branch contains /

2015-12-31 Thread janar...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jan Arend Jansen commented on  JENKINS-30744 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: multibranch issues if branch contains /  
 
 
 
 
 
 
 
 
 
 
The encoded path seems to create problems on windows when using 'bat'.  
Any branch that has a slash in it for example ('feature/myfeature') will get an encoded path on windows like /feature%2Fmyfeature@script and /feature%2Fmyfeature.  
When I apply the following workflow, Jenkins hangs forever on the bat command 

 

node {
stage 'Checkout'
checkout scm
stage 'Build'
bat "echo 'test'"
}
 

 
When I add this same script on the 'master' branch everything is fine. 
Environment: Windows 8.1 Jenkins 1.643 Workflow Plugin 1.12 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-30043) Build Step Jobs are placed after Post Build Action Jobs in delivery

2015-12-31 Thread cristianofon...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 cristiano fontes commented on  JENKINS-30043 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Build Step Jobs are placed after Post Build Action Jobs in delivery  
 
 
 
 
 
 
 
 
 
 
Also note that Join plugin triggered jobs also show in the middle while it should be the last one to show. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-30043) Build Step Jobs are placed after Post Build Action Jobs in delivery

2015-12-31 Thread cristianofon...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 cristiano fontes edited a comment on  JENKINS-30043 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Build Step Jobs are placed after Post Build Action Jobs in delivery  
 
 
 
 
 
 
 
 
 
 Great!!! Also note that Join plugin triggered jobs also show in the middle while it should be the last one to show. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [nodelabelparameter-plugin] (JENKINS-32209) NodeLabel parameter not working inside workflow

2015-12-31 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32209 
 
 
 
  NodeLabel parameter not working inside workflow  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

Component/s:
 
 workflow-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] [maven-plugin] (JENKINS-24869) POM_VERSION is not resetted

2015-12-31 Thread diego...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Diego Marinelli commented on  JENKINS-24869 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: POM_VERSION is not resetted  
 
 
 
 
 
 
 
 
 
 
Any updates or plans of release for this ticket? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [envinject-plugin] (JENKINS-15146) EnvJect unsets empty string properties returned in maps

2015-12-31 Thread bochenski.kuba+jenk...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jakub Bochenski updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-15146 
 
 
 
  EnvJect unsets empty string properties returned in maps  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jakub Bochenski 
 
 
 

Environment:
 
 1.69 , 1.92.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [envinject-plugin] (JENKINS-15146) EnvJect unsets empty string properties returned in maps

2015-12-31 Thread bochenski.kuba+jenk...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jakub Bochenski reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
I'm getting the same behaviour (blank properties are not set) in 1.92.1 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-15146 
 
 
 
  EnvJect unsets empty string properties returned in maps  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jakub Bochenski 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Resolved Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [downstream-buildview-plugin] (JENKINS-5761) Projects triggered by "Parameterized Build Plugin" do not show in view with "Downstream-buildview"

2015-12-31 Thread vladic...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vlad Aginsky commented on  JENKINS-5761 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Projects triggered by "Parameterized Build Plugin" do not show in view with "Downstream-buildview"  
 
 
 
 
 
 
 
 
 
 
same here. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [nodelabelparameter-plugin] (JENKINS-32209) NodeLabel parameter not working inside workflow

2015-12-31 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32209 
 
 
 
  NodeLabel parameter not working inside workflow  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

Labels:
 
 workflow 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-30043) Build Step Jobs are placed after Post Build Action Jobs in delivery

2015-12-31 Thread cristianofon...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Cristiano Fontes edited a comment on  JENKINS-30043 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Build Step Jobs are placed after Post Build Action Jobs in delivery  
 
 
 
 
 
 
 
 
 
 That is Great! !!  Thanks. Also note that Join plugin triggered jobs also show in the middle while it should be the last one to show. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-30043) Build Step Jobs are placed after Post Build Action Jobs in delivery

2015-12-31 Thread cristianofon...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Cristiano Fontes edited a comment on  JENKINS-30043 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Build Step Jobs are placed after Post Build Action Jobs in delivery  
 
 
 
 
 
 
 
 
 
 That is Great! Thanks.Also note that Join plugin triggered jobs also show in the middle while it should be the last one to show  since they only are called after all other jobs are finished . 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [jclouds-plugin] (JENKINS-23406) Immediate destroying VMs

2015-12-31 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Bayer commented on  JENKINS-23406 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Immediate destroying VMs  
 
 
 
 
 
 
 
 
 
 
Single-use slave has always worked fine for that for me? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-30744) multibranch issues if branch contains /

2015-12-31 Thread janar...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jan Arend Jansen reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30744 
 
 
 
  multibranch issues if branch contains /  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jan Arend Jansen 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Resolved Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32231) Rendering HTML file from build artifacts is ignoring the

2015-12-31 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck resolved as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
The previous comment is correct. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-32231 
 
 
 
  Rendering HTML file from build artifacts is ignoring the 

[JIRA] [robot-plugin] (JENKINS-32118) Opening Robot Framework log failed

2015-12-31 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-32118 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Opening Robot Framework log failed  
 
 
 
 
 
 
 
 
 
 
This is likely a result of the security content in Jenkins 1.625.3 and 1.641: 
https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-12-09 https://wiki.jenkins-ci.org/display/JENKINS/Configuring+Content+Security+Policy 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [cloudbees-folder-plugin] (JENKINS-32232) RSS entry id's are not unique for Freestyle multi-branch project

2015-12-31 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-32232 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: RSS entry id's are not unique for Freestyle multi-branch project  
 
 
 
 
 
 
 
 
 
 
Reference: https://github.com/jenkinsci/jenkins/blob/9ab3f1d6aa15a242d226b45664bbb1a8dd0c9818/core/src/main/java/hudson/model/Run.java#L2397 probably just needs a getFullName() instead. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [nodelabelparameter-plugin] (JENKINS-32209) NodeLabel parameter not working inside workflow

2015-12-31 Thread rodr...@freebsd.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Rodrigues commented on  JENKINS-32209 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: NodeLabel parameter not working inside workflow  
 
 
 
 
 
 
 
 
 
 
See fix: https://github.com/jenkinsci/nodelabelparameter-plugin/pull/10/commits 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-30744) multibranch issues if branch contains /

2015-12-31 Thread janar...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jan Arend Jansen commented on  JENKINS-30744 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: multibranch issues if branch contains /  
 
 
 
 
 
 
 
 
 
 
Confirmed that it is related to the encoding of the filepath by dirty-hacking the Branch API Plugin 

 

 public String getEncodedName() {
return Util.rawEncode(getName()).replace("%2F","_");
}
 

 
After updating the plugin to this hacked one on my Windows Jenkins installation, the branches with / in the name work in the MultiBranch Workflow Project 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32260) Exclusive lock on configuration

2015-12-31 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-32260 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Exclusive lock on configuration  
 
 
 
 
 
 
 
 
 
 
Confluence achieves this by having a notification up that other users are editing the wiki page at the same time. Doesn't prevent overriding, but may suffice (plus doesn't let idiot users "lock" a job forever). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-26680) Extraneous Forward-Slash in ssh:// path to repository

2015-12-31 Thread jer...@oufella.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jerome Oufella commented on  JENKINS-26680 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Extraneous Forward-Slash in ssh:// path to repository  
 
 
 
 
 
 
 
 
 
 
Note, this was tested with the following configuration: 
 

Jenkins 1.643
 

Git plugin 2.4.1
 

Git client plugin 1.19.1
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ec2-plugin] (JENKINS-32088) Timed out after 0 seconds of waiting for winrm

2015-12-31 Thread fran...@oaklandsoftware.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Francis Upton resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32088 
 
 
 
  Timed out after 0 seconds of waiting for winrm  
 
 
 
 
 
 
 
 
 

Change By:
 
 Francis Upton 
 
 
 

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] [ec2-plugin] (JENKINS-32088) Timed out after 0 seconds of waiting for winrm

2015-12-31 Thread fran...@oaklandsoftware.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Francis Upton closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32088 
 
 
 
  Timed out after 0 seconds of waiting for winrm  
 
 
 
 
 
 
 
 
 

Change By:
 
 Francis Upton 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ec2-plugin] (JENKINS-31804) After a while the ec2-plugin stops spinning up nodes, and spits out stacktraces. It also stops terminating nodes after their idle time

2015-12-31 Thread fran...@oaklandsoftware.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Francis Upton assigned an issue to Kohsuke Kawaguchi 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Moving to Jenkins core, does not look like ec2 plugin issue (how do I pick who to assign this to in core)? 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-31804 
 
 
 
  After a while the ec2-plugin stops spinning up nodes, and spits out stacktraces. It also stops terminating nodes after their idle time  
 
 
 
 
 
 
 
 
 

Change By:
 
 Francis Upton 
 
 
 

Assignee:
 
 Francis Upton Kohsuke Kawaguchi 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-26639) JClouds failing after upgrade to 1.598

2015-12-31 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Bayer resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-26639 
 
 
 
  JClouds failing after upgrade to 1.598  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andrew Bayer 
 
 
 

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] [packaging] (JENKINS-31889) Packaging tests can't be run on EC2 due to VirtualBox

2015-12-31 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Bayer resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
The new Docker-based packaging tests solve this! 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-31889 
 
 
 
  Packaging tests can't be run on EC2 due to VirtualBox  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andrew Bayer 
 
 
 

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] [core] (JENKINS-20913) [jar caching] - winp.x64.dll access conflicts

2015-12-31 Thread arie.bele...@ironsrc.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arie Belenky reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Hi, This issue started to reproduce during the last week on our AWS Windows Server 2012 R2 base machines. Jenkins ver. 1.640 Traceback: SEVERE: I/O error in channel channel java.net.SocketException: Connection reset at java.net.SocketInputStream.read(Unknown Source) at java.net.SocketInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:82) at hudson.remoting.ChunkedInputStream.readHeader(ChunkedInputStream.java:72) at hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:103) at hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:39) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) 
Dec 31, 2015 5:17:38 PM hudson.remoting.Request$2 run SEVERE: Failed to send back a reply java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(Unknown Source) at java.net.SocketOutputStream.write(Unknown Source) at java.io.BufferedOutputStream.flushBuffer(Unknown Source) at java.io.BufferedOutputStream.write(Unknown Source) at hudson.remoting.ChunkedOutputStream.sendFrame(ChunkedOutputStream.java:94) at hudson.remoting.ChunkedOutputStream.drain(ChunkedOutputStream.java:89) at hudson.remoting.ChunkedOutputStream.write(ChunkedOutputStream.java:58) at java.io.OutputStream.write(Unknown Source) at hudson.remoting.ChunkedCommandTransport.writeBlock(ChunkedCommandTransport.java:45) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.write(AbstractSynchronousByteArrayCommandTransport.java:45) at hudson.remoting.Channel.send(Channel.java:582) at hudson.remoting.Request$2.run(Request.java:340) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:62) at java.lang.Thread.run(Unknown Source) 
Dec 31, 2015 5:17:38 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Terminated Dec 31, 2015 5:17:48 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Locating server among https://jenkins.interjunk.com/ Dec 31, 2015 5:17:48 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Handshaking Dec 31, 2015 5:17:48 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Connecting to jenkins.interjunk.com:15400 Dec 31, 2015 5:17:48 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Trying protocol: JNLP2-connect Dec 31, 2015 5:17:48 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Connected Dec 31, 2015 5:19:00 PM hudson.util.ProcessTree get WARNING: Failed to load winp. Reverting to the default java.lang.UnsatisfiedLinkError: Native Library C:\Users\automation\.jenkins\cache\jars\4A\winp.x64.22D9AB310A3FA2D96B6E03A836A47724.dll already loaded in another classloader at java.lang.ClassLoader.loadLibrary1(Unknown Source) at java.lang.ClassLoader.loadLibrary0(Unknown Source) at java.lang.ClassLoader.loadLibrary(Unknown Source) at java.lang.Runtime.load0(Unknown Source) at java.lang.System.load(Unknown Source) at org.jvnet.winp.Native.loadDll(Native.java:190) at org.jvnet.winp.Native.load(Native.java:122) at org.jvnet.winp.Native.(Native.java:56) at org.jvnet.winp.WinProcess.enableDebugPrivilege(WinProcess.java:212) at hudson.util.ProcessTree$Windows.(ProcessTree.java:494) at hudson.util.ProcessTree.get(ProcessTree.java:345) at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:965) at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:956) at hudson.remoting.UserRequest.perform(UserRequest.java:120) at hudson.remoting.UserRequest.perform(UserRequest.java:48) 

[JIRA] [core] (JENKINS-32231) Rendering HTML file from build artifacts is ignoring the

2015-12-31 Thread bsl...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ben Sluis commented on  JENKINS-32231 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Rendering HTML file from build artifacts is ignoring the 

[JIRA] [core] (JENKINS-32231) Rendering HTML file from build artifacts is ignoring the

2015-12-31 Thread bsl...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ben Sluis closed an issue as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
This is a known security feature. See https://wiki.jenkins-ci.org/display/JENKINS/Configuring+Content+Security+Policy for more details 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-32231 
 
 
 
  Rendering HTML file from build artifacts is ignoring the 

[JIRA] [git-plugin] (JENKINS-26680) Extraneous Forward-Slash in ssh:// path to repository

2015-12-31 Thread jer...@oufella.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jerome Oufella commented on  JENKINS-26680 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Extraneous Forward-Slash in ssh:// path to repository  
 
 
 
 
 
 
 
 
 
 
The bug does not only manifest itself when using relative repositories, but also when using variables to compose a git URI. For example with the Gerrit plugin, you may want to use a git uri such as ssh://$GERRIT_HOST:$GERRIT_PORT/$GERRIT_PROJECT. In this case, the URI will be rewritten with a triple slash, leading to a failure with most git distributions. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32232) RSS entry id's are not unique for Freestyle multi-branch project

2015-12-31 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32232 
 
 
 
  RSS entry id's are not unique for Freestyle multi-branch project  
 
 
 
 
 
 
 
 
 
 
Probably also an issue in e.g. Maven projects. 
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Component/s:
 
 cloudbees-folder-plugin 
 
 
 

Component/s:
 
 multi-branch-project-plugin 
 
 
 

Labels:
 
 multibranch nested 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [jobconfighistory-plugin] (JENKINS-30089) new config history created on each multibranch build

2015-12-31 Thread mjdetul...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio assigned an issue to Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30089 
 
 
 
  new config history created on each multibranch build  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 

Assignee:
 
 Mirko Friedenhagen Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-26680) Extraneous Forward-Slash in ssh:// path to repository

2015-12-31 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite commented on  JENKINS-26680 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Extraneous Forward-Slash in ssh:// path to repository  
 
 
 
 
 
 
 
 
 
 
Jerome Oufella I don't understand how the rewrite is happening in your case, since you're using the platform portable form of the URL (assuming GERRIT_PORT is either a port number or the name of a port as listed in /etc/services). The other entries in this bug report are asking for a URI syntax which is not platform portable, but as far as I can tell, your URI syntax is platform portable. 
Are you sure that your case $GERRIT_PORT actually is evaluating to a port number? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-26680) Extraneous Forward-Slash in ssh:// path to repository

2015-12-31 Thread jer...@oufella.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jerome Oufella commented on  JENKINS-26680 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Extraneous Forward-Slash in ssh:// path to repository  
 
 
 
 
 
 
 
 
 
 
Hi Mark Waite, yes I can confirm that from the job instance's console log. As you can see below, the URL is rewritten using an extra slash. 
Job's git repository URL: ssh://$GERRIT_HOST:$GERRIT_PORT/$GERRIT_PROJECT Result: {{ ... Fetching upstream changes from ssh:///obfuscatedhostname.com:29419/some/repo > git --version # timeout=10 > git -c core.askpass=true fetch --tags --progress ssh:///obfuscatedhostname.com:29419/some/repo +refs/heads/:refs/remotes/origin/ ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Command "git -c core.askpass=true fetch --tags --progress ssh:///obfuscatedhostname.com:29419/some/repo +refs/heads/:refs/remotes/origin/" returned status code 128: stdout:  stderr: ssh: Could not resolve hostname : Name or service not known fatal: Could not read from remote repository. ... }} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-31183) System configuration return java.lang.NullPointerException

2015-12-31 Thread fran...@oaklandsoftware.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Francis Upton assigned an issue to Kohsuke Kawaguchi 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31183 
 
 
 
  System configuration return java.lang.NullPointerException  
 
 
 
 
 
 
 
 
 

Change By:
 
 Francis Upton 
 
 
 

Assignee:
 
 Francis Upton Kohsuke Kawaguchi 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ws-cleanup-plugin] (JENKINS-13939) Workspace cleanup plugin causes Jenkins to consider a job as completed before it is actually done

2015-12-31 Thread bsl...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ben Sluis commented on  JENKINS-13939 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Workspace cleanup plugin causes Jenkins to consider a job as completed before it is actually done  
 
 
 
 
 
 
 
 
 
 
I no longer have this job config setup to verify the fix and I should have replied sooner to verify, sorry about that. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-automation-plugin] (JENKINS-32261) Exclude bcprov dependencies

2015-12-31 Thread ever...@free.fr (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 evernat created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32261 
 
 
 
  Exclude bcprov dependencies  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Kris Thieler 
 
 
 

Components:
 

 vmware-vrealize-automation-plugin 
 
 
 

Created:
 

 31/Dec/15 4:15 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 evernat 
 
 
 
 
 
 
 
 
 
 
vmware-vrealize-automation-plugin.hpi v1.0.1 contains bcmail-jdk16-1.46.jar, bcprov-jdk15on-1.53.jar and bcprov-jdk16-1.46.jar But Jenkins already contains bcprov-jdk15on-1.47.jar. 
I suggest to exclude bcprov-jdk15on-1.53.jar and bcprov-jdk16-1.46.jar from the dependencies of the plugin in order to avoid conflicts in Jenkins and other plugins. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 

[JIRA] [core] (JENKINS-32134) RFE - Add relative path tip in help message of Build Other Projects step

2015-12-31 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-32134 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: RFE - Add relative path tip in help message of Build Other Projects step  
 
 
 
 
 
 
 
 
 
 

have to specify a relative path to define downstream projects using the Build Other Projects post-build action
 
To clarify, specifying an absolute path, both with and without leading slash does not work? Or what do you mean here? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [mesos-plugin] (JENKINS-22054) Failed to instantiate class org.jenkinsci.plugins.mesos.MesosCloud from

2015-12-31 Thread vinc...@latombe.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vincent Latombe closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
This must have been fixed since 0.3, at least in 0.8.0 the plugin doesn't fail like this. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-22054 
 
 
 
   Failed to instantiate class org.jenkinsci.plugins.mesos.MesosCloud from   
 
 
 
 
 
 
 
 
 

Change By:
 
 Vincent Latombe 
 
 
 

Status:
 
 Open Closed 
 
 
 

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] [ec2-plugin] (JENKINS-5516) NPE in Amazon EC2 plugin

2015-12-31 Thread fran...@oaklandsoftware.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Francis Upton closed an issue as Cannot Reproduce 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Ancient issue, closing. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-5516 
 
 
 
  NPE in Amazon EC2 plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Francis Upton 
 
 
 

Status:
 
 Open Closed 
 
 
 

Assignee:
 
 Kohsuke Kawaguchi Francis Upton 
 
 
 

Resolution:
 
 Cannot Reproduce 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [jira-plugin] (JENKINS-31268) @Exported returns double XML value for getter

2015-12-31 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31268 
 
 
 
  @Exported returns double XML value for getter  
 
 
 
 
 
 
 
 
 
 
This is caused by the JiraIssueParameterValue's getValue() method having the same signature as its superclass method, but a different return type. 
This means class.getMethods() returns two different entries, one for String and one for Object. The Exported annotation apparently applies to both these methods (probably because it only considers signatures?), so both get serialized independently. 
This is looks like a bug in Stapler, which assumes getMethods() has no "duplicates", caused by a very unusual case in the Jira Plugin. 
Possible workarounds for Jira plugin, that would fix this issue for past releases of Jenkins core/Stapler: 
 

Export a new method public String value() instead, so the Exported annotation does not apply to the supertype method
 

Change the return type of getValue() to Object, so there won't be two entries in JiraIssueParameterValue.class.getMethods() for getValue. Minor changes to other methods in the same class need to be done (add a few toString() calls).
 
 
Since Stapler issues are tracked elsewhere, reassigning this to the Jira Plugin which could apply one of the workarounds mentioned above. 
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Component/s:
 
 jira-plugin 
 
 
 

Component/s:
 
 core 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 

[JIRA] [core] (JENKINS-32231) Rendering HTML file from build artifacts is ignoring the

2015-12-31 Thread cobe...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Obexer commented on  JENKINS-32231 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Rendering HTML file from build artifacts is ignoring the 

[JIRA] [cloudbees-folder-plugin] (JENKINS-32232) RSS entry id's are not unique for Freestyle multi-branch project

2015-12-31 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-32232 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: RSS entry id's are not unique for Freestyle multi-branch project  
 
 
 
 
 
 
 
 
 
 
Would something like tag:hudson.dev.java.net,2015:foo/bar/trunk:19 be a valid ID? That would be trivial to do, but RFC 3987 is a bit more than I'd like to deal with right 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] [mesos-plugin] (JENKINS-26236) [mesos-plugin] Add Docker Parameters option

2015-12-31 Thread vinc...@latombe.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vincent Latombe commented on  JENKINS-26236 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: [mesos-plugin] Add Docker Parameters option  
 
 
 
 
 
 
 
 
 
 
This has been released in 0.6.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [mesos-plugin] (JENKINS-26236) [mesos-plugin] Add Docker Parameters option

2015-12-31 Thread vinc...@latombe.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vincent Latombe closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-26236 
 
 
 
  [mesos-plugin] Add Docker Parameters option  
 
 
 
 
 
 
 
 
 

Change By:
 
 Vincent Latombe 
 
 
 

Status:
 
 Open Closed 
 
 
 

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] [git-plugin] (JENKINS-26680) Extraneous Forward-Slash in ssh:// path to repository

2015-12-31 Thread jer...@oufella.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jerome Oufella edited a comment on  JENKINS-26680 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Extraneous Forward-Slash in ssh:// path to repository  
 
 
 
 
 
 
 
 
 
 Hi [~markewaite], yes I can confirm that from the job instance's console log. As you can see below, the URL is rewritten using an extra slash.Job's git repository URL: ssh://$GERRIT_HOST:$GERRIT_PORT/$GERRIT_PROJECTResult:{code :none }...Fetching upstream changes from ssh:///obfuscatedhostname.com:29419/some/repo > git --version # timeout=10 > git -c core.askpass=true fetch --tags --progress ssh:///obfuscatedhostname.com:29419/some/repo +refs/heads/*:refs/remotes/origin/*ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException: Command "git -c core.askpass=true fetch --tags --progress ssh:///obfuscatedhostname.com:29419/some/repo +refs/heads/*:refs/remotes/origin/*" returned status code 128:stdout: stderr: ssh: Could not resolve hostname : Name or service not knownfatal: Could not read from remote repository{code}EDIT: fix code block 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-30744) multibranch issues if branch contains /

2015-12-31 Thread janar...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jan Arend Jansen edited a comment on  JENKINS-30744 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: multibranch issues if branch contains /  
 
 
 
 
 
 
 
 
 
 The encoded path seems to create problems on windows when using 'bat'. Any branch that has a slash in it for example ('feature/myfeature') will get an encoded path on windows like {{/feature%2Fmyfeature@script}} and {{/feature%2Fmyfeature}}. When I apply the following workflow  in a multibranch job in a root file 'Jenkinsfile' , Jenkins hangs forever on the bat command{code}node {stage 'Checkout'checkout scmstage 'Build'bat "echo 'test'"}{code}When I add this same script on the 'master' branch everything is fine.Environment:Windows 8.1Jenkins 1.643Workflow Plugin 1.12 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32260) Exclusive lock on configuration

2015-12-31 Thread adrien.lecharpent...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Adrien Lecharpentier created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32260 
 
 
 
  Exclusive lock on configuration  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 31/Dec/15 3:37 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Adrien Lecharpentier 
 
 
 
 
 
 
 
 
 
 
As a user, I'd like to be sure that when editing the configuration of a job, it doesn't get overwritten by another user because he/she submitted its changes after I did.  
It could be done by preventing multiple user to edit the job configuration at the same time or by having some "modification" marks which would be checked before submitting the configuration. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


[JIRA] [core] (JENKINS-32210) ldap and proxy access problem

2015-12-31 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32210 
 
 
 
  ldap and proxy access problem  
 
 
 
 
 
 
 
 
 
 
It is not clear what your setup looks like. Is the LDAP server behind a proxy, or what's going on here? 
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Priority:
 
 Blocker Minor 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-26680) Extraneous Forward-Slash in ssh:// path to repository

2015-12-31 Thread jer...@oufella.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jerome Oufella edited a comment on  JENKINS-26680 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Extraneous Forward-Slash in ssh:// path to repository  
 
 
 
 
 
 
 
 
 
 Hi [~markewaite], yes I can confirm that from the job instance's console log. As you can see below, the URL is rewritten using an extra slash.Job's git repository URL: ssh://$GERRIT_HOST:$GERRIT_PORT/$GERRIT_PROJECTResult:{ { code} ...Fetching upstream changes from ssh:///obfuscatedhostname.com:29419/some/repo > git --version # timeout=10 > git -c core.askpass=true fetch --tags --progress ssh:///obfuscatedhostname.com:29419/some/repo +refs/heads/*:refs/remotes/origin/*ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException: Command "git -c core.askpass=true fetch --tags --progress ssh:///obfuscatedhostname.com:29419/some/repo +refs/heads/*:refs/remotes/origin/*" returned status code 128:stdout: stderr: ssh: Could not resolve hostname : Name or service not knownfatal: Could not read from remote repository {code } } EDIT: fix code block 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ec2-plugin] (JENKINS-32088) Timed out after 0 seconds of waiting for winrm

2015-12-31 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-32088 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Timed out after 0 seconds of waiting for winrm  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Francis Upton IV Path: src/main/java/hudson/plugins/ec2/win/EC2WindowsLauncher.java http://jenkins-ci.org/commit/ec2-plugin/1f72deb858fe7462bff5b6361bb1bd115d7b8cb0 Log: Merge pull request #175 from liutongxing/master 
JENKINS-32088 Timed out after 0 seconds of waiting for winrm 
Compare: https://github.com/jenkinsci/ec2-plugin/compare/36a16ca458f4...1f72deb858fe 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-26680) Extraneous Forward-Slash in ssh:// path to repository

2015-12-31 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite commented on  JENKINS-26680 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Extraneous Forward-Slash in ssh:// path to repository  
 
 
 
 
 
 
 
 
 
 
Thanks for the further clarification. I think I see the same condition you're seeing in my test job. 
If I create a test URI that includes the port number (like ssh://wheezy64b.markwaite.net:45022/var/lib/git/mwaite/bin.git) then the clone works. 
If I create a parameterized test job with PORT_NUMBER as the parameter and assign it a value of 45022, and reference that port number in the URL, then the clone fails. It is as though the rewrite is somehow involved in the code path that expands that parameter. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ec2-plugin] (JENKINS-25322) EnvInject channel is already closed when used with ec2 autoscaling plugin

2015-12-31 Thread franc...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Francis Upton commented on  JENKINS-25322 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: EnvInject channel is already closed when used with ec2 autoscaling plugin  
 
 
 
 
 
 
 
 
 
 
Can you try this on the current master course (taking 1.30-SNAPSHOT)? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ec2-plugin] (JENKINS-26493) Use new EC2 API endpoint hostnames

2015-12-31 Thread franc...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Francis Upton commented on  JENKINS-26493 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Use new EC2 API endpoint hostnames  
 
 
 
 
 
 
 
 
 
 
Unfortunately there are some regressions in the current master unreleased version. I'm going to try and address those in the next few days and once they are fixed and it seems reliable, I will do a new release. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32134) RFE - Add relative path tip in help message of Build Other Projects step

2015-12-31 Thread aburdajew...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Allan BURDAJEWICZ updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32134 
 
 
 
  RFE - Add relative path tip in help message of Build Other Projects step  
 
 
 
 
 
 
 
 
 

Change By:
 
 Allan BURDAJEWICZ 
 
 
 
 
 
 
 
 
 
 This issue is relevant only to people using the Folder plugin (or other plugins providing an ItemGroup implementation like Multi-Branch).  It is not obvious for customers that they have to specify a relative path to define downstream projects using the Build Other Projects post-build action. It would be nice to have a tip in the help message for that. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [accurev-plugin] (JENKINS-25247) Accurev Plugin should calculate change log based on update when using reftree or workspace

2015-12-31 Thread rym...@netscape.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ray Munian closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Fixed 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-25247 
 
 
 
  Accurev Plugin should calculate change log based on update when using reftree or workspace  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ray Munian 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-22853) SEVERE: Trying to unexport an object that's already unexported

2015-12-31 Thread richard.eck...@googlemail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Eckart de Castilho commented on  JENKINS-22853 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: SEVERE: Trying to unexport an object that's already unexported  
 
 
 
 
 
 
 
 
 
 
I hit this error but it turned out now that it was caused for me by an infinite loop in a unit test. Might be worth for others too to look whether they see any timeouts in the build log before hitting the stack trace reported in this issue. 
Timeout: 

 
Build timed out (after 235 minutes). Marking the build as failed.

Results :

Tests run: 3, Failures: 0, Errors: 0, Skipped: 0

[ERROR] There was a timeout or other error in the fork
 

 
Stack trace later 

 
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 3:54:51.866s
[INFO] Finished at: Tue Dec 29 23:01:30 CET 2015
[INFO] Final Memory: 136M/247M
[INFO] 
[ERROR] Internal error: java.lang.IllegalStateException: Invalid object ID 41 iota=300: Object was recently deallocated
[ERROR] #41 (ref.0) : object=null type=$Proxy53 interfaces=[hudson.maven.MavenBuildProxy2]
[ERROR] Created at Tue Dec 29 19:06:33 CET 2015
[ERROR] at hudson.remoting.ExportTable$Entry.(ExportTable.java:99)
[ERROR] at hudson.remoting.ExportTable.export(ExportTable.java:305)
[ERROR] at hudson.remoting.Channel.internalExport(Channel.java:626)
[ERROR] at hudson.remoting.Channel.export(Channel.java:617)
[ERROR] at hudson.remoting.Channel.export(Channel.java:587)
[ERROR] at hudson.maven.MavenBuild$ProxyImpl2.writeReplace(MavenBuild.java:751)
[ERROR] at sun.reflect.GeneratedMethodAccessor2332.invoke(Unknown Source)
[ERROR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[ERROR] at java.lang.reflect.Method.invoke(Method.java:597)
[ERROR] at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:1032)
[ERROR] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1115)
[ERROR] at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518)
[ERROR] at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483)
[ERROR] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400)
[ERROR] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158)
[ERROR] at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330)
[ERROR] at java.util.HashMap.writeObject(HashMap.java:1001)
[ERROR] at sun.reflect.GeneratedMethodAccessor2336.invoke(Unknown Source)
[ERROR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[ERROR] at java.lang.reflect.Method.invoke(Method.java:597)
[ERROR] at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945)
[ERROR] at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1469)
[ERROR] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400)
[ERROR] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158)
[ERROR] at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518)
[ERROR] at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483)
[ERROR] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400)
[ERROR] at 

[JIRA] [job-dsl-plugin] (JENKINS-31830) Add support for some RubyMetrics report plugin

2015-12-31 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-31830 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add support for some RubyMetrics report plugin  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Victor Martinez Path: job-dsl-core/src/main/docs/examples/javaposse/jobdsl/dsl/helpers/publisher/PublisherContext/rcov.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/PublisherContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/RcovContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/publisher/PublisherContextSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/d0d9d599f06904ba59230e777f054919fd5cb3dd Log: JENKINS-31830 Added support for rcov publisher as part of the RubyMetrics Reports 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] [job-dsl-plugin] (JENKINS-31830) Add support for some RubyMetrics report plugin

2015-12-31 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Spilker resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Will be released in 1.42. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-31830 
 
 
 
  Add support for some RubyMetrics report plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Spilker 
 
 
 

Status:
 
 Reopened 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] [core] (JENKINS-32134) RFE - Add relative path tip in help message of Build Other Projects step

2015-12-31 Thread aburdajew...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Allan BURDAJEWICZ commented on  JENKINS-32134 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: RFE - Add relative path tip in help message of Build Other Projects step  
 
 
 
 
 
 
 
 
 
 
Thanks for reminding me, I need to change the description. Both path works. When I created the issue I did not realize that the absolute path works as well. This is a core functionality but this issue is relevant only to people using the Folder plugin (or other plugins providing an ItemGroup implementation like Multi-Branch).  The main problem is that it not clear to users that they need to specify the path of downstream projects located inside folders. They may think that specifying the project name is sufficient. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [categorized-view-plugin] (JENKINS-32071) Slow Performance with Category View Plugin

2015-12-31 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-32071 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Slow Performance with Category View Plugin  
 
 
 
 
 
 
 
 
 
 
The issue report does not contain enough information to determine what the bug is, or whether it is indeed a bug. The stack trace in question loads a single build (the latest one) for a job. If your disk is so slow, there's something seriously wrong with your setup. 
Also, 1.609.4.6 is not a Jenkins version. This needs to happen with an actual Jenkins release for anyone on this tracker to care. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [job-dsl-plugin] (JENKINS-32195) Add support for JSLint Plugin

2015-12-31 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Spilker resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Will be released in 1.42. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-32195 
 
 
 
  Add support for JSLint Plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Spilker 
 
 
 

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] [job-dsl-plugin] (JENKINS-32195) Add support for JSLint Plugin

2015-12-31 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-32195 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add support for JSLint Plugin  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Victor Martinez Path: docs/Home.md job-dsl-core/src/main/docs/examples/javaposse/jobdsl/dsl/helpers/step/StepContext/jslint.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/JSLintContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/StepContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/step/StepContextSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/47589a210d073d1cfa10773b061f50b329d62ebc Log: 

JENKINS-32195
 Added support for JSLint 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.