date:20160503

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 vimil updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34524 
 
 
 
  Extended Choice Parameter Plug in in Jenkins 2.0 always show that there are scripts to approve   
 
 
 
 
 
 
 
 
 

Change By:
 
 vimil 
 
 
 

Attachment:
 
 screenshot-1.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34524) Extended Choice Parameter Plug in in Jenkins 2.0 always show that there are scripts to approve

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 vimil updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34524 
 
 
 
  Extended Choice Parameter Plug in in Jenkins 2.0 always show that there are scripts to approve   
 
 
 
 
 
 
 
 
 

Change By:
 
 vimil 
 
 
 

Attachment:
 
 screenshot-1.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-flow-plugin] (JENKINS-34580) Enable downstream test result aggregation in Pipeline jobs like in Buildflow jobs

2016-05-03 Thread damien.no...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Damien Nozay assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34580 
 
 
 
  Enable downstream test result aggregation in Pipeline jobs like in Buildflow jobs  
 
 
 
 
 
 
 
 
 

Change By:
 
 Damien Nozay 
 
 
 

Assignee:
 
 Damien Nozay 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34524) Extended Choice Parameter Plug in in Jenkins 2.0 always show that there are scripts to approve

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 vimil updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34524 
 
 
 
  Extended Choice Parameter Plug in in Jenkins 2.0 always show that there are scripts to approve   
 
 
 
 
 
 
 
 
 

Change By:
 
 vimil 
 
 
 

Attachment:
 
 config-example.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34524) Extended Choice Parameter Plug in in Jenkins 2.0 always show that there are scripts to approve

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 vimil commented on  JENKINS-34524 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Extended Choice Parameter Plug in in Jenkins 2.0 always show that there are scripts to approve   
 
 
 
 
 
 
 
 
 
 
In the example you sent, you have to use the 'default groovy script' option to enter the groovyscript instead of 'groovyscript' See attached example. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34585) Please release new version of EC2 plugin

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Francis Upton commented on  JENKINS-34585 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Please release new version of EC2 plugin  
 
 
 
 
 
 
 
 
 
 
Give me a couple of days, there is one more critical bug I want to fix. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34585) Please release new version of EC2 plugin

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Johnny Shields created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34585 
 
 
 
  Please release new version of EC2 plugin  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Francis Upton 
 
 
 

Components:
 

 ec2-plugin 
 
 
 

Created:
 

 2016/May/04 4:19 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Johnny Shields 
 
 
 
 
 
 
 
 
 
 
There are a number of critical fixes and enhancements to spot instance behavior since last published release. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[JIRA] [ec2-plugin] (JENKINS-32399) Change the name of spot instances to be more readable

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Francis Upton resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
The spot instance id is perfect for this. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-32399 
 
 
 
  Change the name of spot instances to be more readable  
 
 
 
 
 
 
 
 
 

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-32399) Change the name of spot instances to be more readable

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Francis Upton closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32399 
 
 
 
  Change the name of spot instances to be more readable  
 
 
 
 
 
 
 
 
 

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-27529) Refactor ec2-plugin's Spot instance support to use spotinstancerequest polling

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Francis Upton resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-27529 
 
 
 
  Refactor ec2-plugin's Spot instance support to use spotinstancerequest polling  
 
 
 
 
 
 
 
 
 

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-27529) Refactor ec2-plugin's Spot instance support to use spotinstancerequest polling

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Francis Upton closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-27529 
 
 
 
  Refactor ec2-plugin's Spot instance support to use spotinstancerequest polling  
 
 
 
 
 
 
 
 
 

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-19059) [ec2-plugin] spot instance feature cannot be used when the master deployed internally (no public access)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Francis Upton closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-19059 
 
 
 
  [ec2-plugin] spot instance feature cannot be used when the master deployed internally (no public access)  
 
 
 
 
 
 
 
 
 

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-19059) [ec2-plugin] spot instance feature cannot be used when the master deployed internally (no public access)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Francis Upton resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-19059 
 
 
 
  [ec2-plugin] spot instance feature cannot be used when the master deployed internally (no public access)  
 
 
 
 
 
 
 
 
 

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-34584) Refactor spot instance launching workflow

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Johnny Shields closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Done here: https://github.com/jenkinsci/ec2-plugin/pull/179 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-34584 
 
 
 
  Refactor spot instance launching workflow  
 
 
 
 
 
 
 
 
 

Change By:
 
 Johnny Shields 
 
 
 

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-34584) Refactor spot instance launching workflow

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Johnny Shields commented on  JENKINS-34584 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Refactor spot instance launching workflow  
 
 
 
 
 
 
 
 
 
 
This was already done! https://github.com/jenkinsci/ec2-plugin/pull/179 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34584) Refactor spot instance launching workflow

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Johnny Shields commented on  JENKINS-34584 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Refactor spot instance launching workflow  
 
 
 
 
 
 
 
 
 
 
Please close this issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34584) Refactor spot instance launching workflow

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Johnny Shields created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34584 
 
 
 
  Refactor spot instance launching workflow  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Francis Upton 
 
 
 

Components:
 

 ec2-plugin 
 
 
 

Created:
 

 2016/May/04 4:01 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Johnny Shields 
 
 
 
 
 
 
 
 
 
 
I think the current slave launching workflow for spot instances could be done without the need to install special scripts to the slave instance. It could look something like: 
1) Raise spot instance request 2) Jenkins polls for spot instance request to be fulfilled 3) Get info of instance inside spot instance request 4) Jenkins polls for associated ec2 instance to be live (if not already) 5) From this time, Jenkins treats it exactly like an on-demand (i.e. non-spot) ec2 instance, with a reference to the spot request. 
This would reduce the headache associated with installing boot script and allow the ec2-plugin code to be cleaned up. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [ec2-plugin] (JENKINS-32915) Spot instance launched one after another until capacity reached for single task in queue

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

 
 
 
 
 
 
 
  Re: Spot instance launched one after another until capacity reached for single task in queue  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: James Judd Path: src/main/java/hudson/plugins/ec2/EC2AbstractSlave.java src/main/java/hudson/plugins/ec2/EC2Cloud.java http://jenkins-ci.org/commit/ec2-plugin/ac5574e23654ae1a7cff8be6bced44b3d6320470 Log: JENKINS-32915 (#193) 
 

JENKINS-32915: Corrected horizontal scaling if cloud/job label is null - is not defined in configuration. Better handling of inproper Jenkins core manegment over excessWorkload - if an instance takes 5 minutes to wake up Jenkins does not take it into consideration and tries to provision more until capacity is reached or queue is picked finally. Added logging message that provisioning for spot instance will not be possible if label is not configured. It should be made explicit for the user in configuration that it is needed.
 
 
 

JENKINS-32915: Added missing implementation of method
 
 
 

JENKINS-32915: Amendments to match tested bottom up code to minimize risk of inproper behaviour.
 
 
 

JENKINS-32915: Negation fix
 
 
 

JENKINS-32915: Refactored code to make it more readable and perform better
 
 
 

JENKINS-32915: Refactored code to scale out properly. Added warning messages, information messages, amended future task to hold for timeout time
 
 
 

Cleaning up PR as requested by @francisu
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [ec2-plugin] (JENKINS-32399) Change the name of spot instances to be more readable

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Johnny Shields commented on  JENKINS-32399 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Change the name of spot instances to be more readable  
 
 
 
 
 
 
 
 
 
 
This is a duplicate of JENKINS-29355. Propose to close it. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [gitlab-plugin] (JENKINS-34534) Gitlab-Plugin via Job DSL not activated

2016-05-03 Thread pyt...@pyther.net (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew Gyurgyik commented on  JENKINS-34534 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Gitlab-Plugin via Job DSL not activated  
 
 
 
 
 
 
 
 
 
 
PR: https://github.com/jenkinsci/job-dsl-plugin/pull/835 
This appears to happen because the following trigger parameters were replace/added:  
 


 
allowAllBranches 

 
 was replaced with  

 
branchFilterType 


 

new parameter 

 
targetBranchRegex 


 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34551) scm#git#cleanBeforeCheckout is wrong.

2016-05-03 Thread wuhui...@126.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 zuo wuhui edited a comment on  JENKINS-34551 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: scm#git#cleanBeforeCheckout is wrong.  
 
 
 
 
 
 
 
 
 
 Re: [~daspilker]    But, there are some methods under  `  {code:java} scm -> git -> extensioins ` {code} . how and when to use them? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34551) scm#git#cleanBeforeCheckout is wrong.

2016-05-03 Thread wuhui...@126.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 zuo wuhui edited a comment on  JENKINS-34551 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: scm#git#cleanBeforeCheckout is wrong.  
 
 
 
 
 
 
 
 
 
 @ [~ daspilker  ] But, there are some methods under `scm -> git -> extensioins`. how and when to use them? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34551) scm#git#cleanBeforeCheckout is wrong.

2016-05-03 Thread wuhui...@126.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 zuo wuhui commented on  JENKINS-34551 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: scm#git#cleanBeforeCheckout is wrong.  
 
 
 
 
 
 
 
 
 
 
@daspilker But, there are some methods under `scm -> git -> extensioins`. how and when to use them? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33663) Upgrade wizard step #1: recommended plugin installation

2016-05-03 Thread pw...@cloudbees.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrick Wolf updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33663 
 
 
 
  Upgrade wizard step #1: recommended plugin installation  
 
 
 
 
 
 
 
 
 

Change By:
 
 Patrick Wolf 
 
 
 

Labels:
 
 2.0  community-bee 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-15331) Workaround Windows unpredictable file locking in Util.deleteContentsRecursive

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

 
 
 
 
 
 
 
  Re: Workaround Windows unpredictable file locking in Util.deleteContentsRecursive  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/Util.java core/src/test/java/hudson/UtilTest.java http://jenkins-ci.org/commit/jenkins/240405dfc33e9c9a96a159b36be269b3201567fa Log: Merge pull request #2026 from pjdarton/fix_jenkins_15331 
[FIX JENKINS-15331] Windows file locking workaround 
Compare: https://github.com/jenkinsci/jenkins/compare/49a65c2bbbd8...240405dfc33e 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-15331) Workaround Windows unpredictable file locking in Util.deleteContentsRecursive

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-15331 
 
 
 
  Workaround Windows unpredictable file locking in Util.deleteContentsRecursive  
 
 
 
 
 
 
 
 
 

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] [core] (JENKINS-15331) Workaround Windows unpredictable file locking in Util.deleteContentsRecursive

Title: Message Title

SCM/JIRA link daemon commented on JENKINS-15331

Re: Workaround Windows unpredictable file locking in Util.deleteContentsRecursive

Code changed in jenkins User: Peter Darton Path: core/src/main/java/hudson/Util.java core/src/test/java/hudson/UtilTest.java http://jenkins-ci.org/commit/jenkins/310c6747625a5e5605ac87c68d02eddaacdc8e0e Log: FIXED

JENKINS-15331
by changing Util.deleteContentsRecursive, Util.deleteFile and Util.deleteRecursive so that they can retry failed deletions. The number of deletion attempts and the time it waits between deletes are configurable via system properties (like hudson.Util.noSymlink etc). Util.DELETION_MAX is set by -Dhudson.Util.deletionMax. Default is 3 attempts. Util.WAIT_BETWEEN_DELETION_RETRIES is set by -Dhudson.Util.deletionRetryWait. Defaults is 100 milliseconds. Util.GC_AFTER_FAILED_DELETE is set by -Dhudson.Util.performGCOnFailedDelete. Default is false.
Added unit-tests for new functionality.

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-18407) Starting a job with params using REST Api doesn't return 201 http status code as stated in the documentation

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

 
 
 
 
 
 
 
  Re: Starting a job with params using REST Api doesn't return 201 http status code as stated in the documentation  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Craig Rodrigues Path: src/test/groovy/com/cloudbees/plugins/flow/ConcurrencyTest.groovy http://jenkins-ci.org/commit/build-flow-plugin/faeaa5cc2062f7c7b73073e201b12646e9538963 Log: Delete test which no longer works in 1.521+ due to improved core behavior from 

JENKINS-18407
 
Due to the improved core behavior, in JobInvocation.groovy's run() method, schedule2() no longer returns null when invoked from the test. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33231) SCMVar is in Multibranch, but Multibranch isn't a dependency of Aggregator

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
workflow-aggregator has depended on workflow-multibranch for a while now. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-33231 
 
 
 
  SCMVar is in Multibranch, but Multibranch isn't a dependency of Aggregator  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

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] [cli] (JENKINS-32874) Improve test coverage of AbstractBuildRangeCommand

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

 
 
 
 
 
 
 
  Re: Improve test coverage of AbstractBuildRangeCommand  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Ing. Pavel Janousek Path: test/src/test/java/hudson/cli/AbstractBuildRangeCommandTest.java test/src/test/java/hudson/cli/AbstractBuildRangeCommandTest2.java http://jenkins-ci.org/commit/jenkins/2eef942be6edb9793da0380eae393adaba7af24f Log: JENKINS-32874 Improved test coverage of AbstractBuildRangeCommand 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [cli] (JENKINS-32874) Improve test coverage of AbstractBuildRangeCommand

2016-05-03 Thread stu...@somepointinthefuture.co.nz (JIRA)

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

 
 
 
 
 
 
 
  Re: Improve test coverage of AbstractBuildRangeCommand  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Daniel Beck Path: test/src/test/java/hudson/cli/AbstractBuildRangeCommandTest.java test/src/test/java/hudson/cli/AbstractBuildRangeCommandTest2.java http://jenkins-ci.org/commit/jenkins/49a65c2bbbd8bd2d2596ca79ab69e374d42eda24 Log: Merge pull request #2257 from pjanouse/JENKINS-32874 
JENKINS-32874 Improved test coverage of AbstractBuildRangeCommand 
Compare: https://github.com/jenkinsci/jenkins/compare/134abbd6d32d...49a65c2bbbd8 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34583) Remove arbitrarily bundled plugins from Jenkins war

2016-05-03 Thread db...@cloudbees.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck moved an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34583 
 
 
 
  Remove arbitrarily bundled plugins from Jenkins war  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Project:
 
 Infrastructure Jenkins 
 
 
 

Key:
 
 INFRA JENKINS - 691 34583 
 
 
 

Workflow:
 
 classic default workflow JNJira 
 
 
 

Component/s:
 
 core 
 
 
 

Component/s:
 
 core 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34583) Remove arbitrarily bundled plugins from Jenkins war

2016-05-03 Thread db...@cloudbees.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34583 
 
 
 
  Remove arbitrarily bundled plugins from Jenkins war  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Assignee:
 
 R. Tyler Croy 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34582) Cross-Site scripting vulnerability in /job//job//scan-on-demand

2016-05-03 Thread jason.b.mar...@nordstrom.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jason Marzan created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34582 
 
 
 
  Cross-Site scripting vulnerability in /job//job//scan-on-demand   
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 2016/May/03 10:47 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Jason Marzan 
 
 
 
 
 
 
 
 
 
 
Jenkins ver. 1.625.3 
/job/SP/job/Windows_Hello/scan-on-demand call is vulnerable to cross-site scripting. Script Alert(1) passed as a parameter was reflected back. This gives attacker possibility to run scripts on user’s machine 
Impact: Attacker can trick a user into clicking on a link that contains code to steal user credentials and hijack the session 
Suggested Remediation: Check user input and escape HTML characters 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [core] (JENKINS-34550) Remote Command Execution - running a job on Windows machines, it is possible to escape parameters by adding “ before string and execute commands on target system.

2016-05-03 Thread jason.b.mar...@nordstrom.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jason Marzan updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34550 
 
 
 
  Remote Command Execution - running a job on Windows machines, it is possible to escape parameters by adding “ before string and execute commands on target system.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jason Marzan 
 
 
 
 
 
 
 
 
 
 *Jenkins ver. 1.625.3* When running a job on Windows machines, it is possible to escape parameters by adding “ before string and execute commands on target system.we were able to run system commands, mount shares and bring files in and out of the machine.*Impact:*By running commands on build machine, user will be able to see other user’s jobs, steal credentials, and install a backdoor shell. Criticality is set to high since user has to be authenticated to Jenkins.*Suggested Remediation:*Escape input strings for parameters, just like on Unix machines. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34550) Remote Command Execution - running a job on Windows machines, it is possible to escape parameters by adding “ before string and execute commands on target system.

2016-05-03 Thread jason.b.mar...@nordstrom.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jason Marzan commented on  JENKINS-34550 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Remote Command Execution - running a job on Windows machines, it is possible to escape parameters by adding “ before string and execute commands on target system.  
 
 
 
 
 
 
 
 
 
 
Changed priority to Critical since this is a security issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [quality-gates-plugin] (JENKINS-34427) Sonar user password is stored in plain text in every job configuration

2016-05-03 Thread pashcan....@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pasha Sh. commented on  JENKINS-34427 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Sonar user password is stored in plain text in every job configuration   
 
 
 
 
 
 
 
 
 
 
Can submitter or someone else please provide details to reproduce this issue? Mostly interested in versions of SonarQube, Jenkins and SQ Jenkins plugin that were used. We are on latest Jenkins LTS + SQ Jenkins plugin 2.4 and I'm not seeing any plaintext credentials in the job configs. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [quality-gates-plugin] (JENKINS-34427) Sonar user password is stored in plain text in every job configuration

2016-05-03 Thread pashcan....@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pasha Sh. updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34427 
 
 
 
  Sonar user password is stored in plain text in every job configuration   
 
 
 
 
 
 
 
 
 

Change By:
 
 Pasha Sh. 
 
 
 

Comment:
 
 Can submitter or someone else please provide details to reproduce this issue? Mostly interested in versions of SonarQube, Jenkins and SQ Jenkins plugin that were used. We are on latest Jenkins LTS + SQ Jenkins plugin 2.4 and I'm not seeing any plaintext credentials in the job configs. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34550) Remote Command Execution - running a job on Windows machines, it is possible to escape parameters by adding “ before string and execute commands on target system.

2016-05-03 Thread jason.b.mar...@nordstrom.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jason Marzan updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34550 
 
 
 
  Remote Command Execution - running a job on Windows machines, it is possible to escape parameters by adding “ before string and execute commands on target system.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jason Marzan 
 
 
 

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] [branch-api-plugin] (JENKINS-33819) Inability to control orphaned item strategy on multibranch children of an organization folder

2016-05-03 Thread tim.gour...@siemens.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tim Gourley commented on  JENKINS-33819 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Inability to control orphaned item strategy on multibranch children of an organization folder  
 
 
 
 
 
 
 
 
 
 
I think the analysis is incorrect in that the code in question "new DefaultOrphanedItemStrategy(..)" does not appear to be located in the branch-api-plugin. I suspect that code is in the cloudbees-folder-plugin.  
For background - this issue was reported against "Jenkins ver. 1.642.3.2 (CloudBees Jenkins Enterprise 15.11)" which uses "Branch API Pulugin" 1.5, and "CloudBees Folders Plus Plugin" 3.0. "CloudBees Folders Plus Plugin" version 3.0 appears to be pre-open source so I cannot analyze further. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [vault-scm-plugin] (JENKINS-17143) Plugin not saving vault executable path between server restarts

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stuart Whelan assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-17143 
 
 
 
  Plugin not saving vault executable path between server restarts  
 
 
 
 
 
 
 
 
 

Change By:
 
 Stuart Whelan 
 
 
 

Assignee:
 
 Stuart Whelan 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [vault-scm-plugin] (JENKINS-17143) Plugin not saving vault executable path between server restarts

2016-05-03 Thread stu...@somepointinthefuture.co.nz (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stuart Whelan resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-17143 
 
 
 
  Plugin not saving vault executable path between server restarts  
 
 
 
 
 
 
 
 
 

Change By:
 
 Stuart Whelan 
 
 
 

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] [vault-scm-plugin] (JENKINS-17143) Plugin not saving vault executable path between server restarts

2016-05-03 Thread stu...@somepointinthefuture.co.nz (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stuart Whelan closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-17143 
 
 
 
  Plugin not saving vault executable path between server restarts  
 
 
 
 
 
 
 
 
 

Change By:
 
 Stuart Whelan 
 
 
 

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] [vault-scm-plugin] (JENKINS-22953) Show paths/files in Changes reports

2016-05-03 Thread stu...@somepointinthefuture.co.nz (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stuart Whelan assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-22953 
 
 
 
  Show paths/files in Changes reports  
 
 
 
 
 
 
 
 
 

Change By:
 
 Stuart Whelan 
 
 
 

Assignee:
 
 Stuart Whelan 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [vault-scm-plugin] (JENKINS-19784) Setting of Use Non Working Folder does not work

2016-05-03 Thread stu...@somepointinthefuture.co.nz (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stuart Whelan assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-19784 
 
 
 
  Setting of Use Non Working Folder does not work  
 
 
 
 
 
 
 
 
 

Change By:
 
 Stuart Whelan 
 
 
 

Assignee:
 
 Stuart Whelan 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [vault-scm-plugin] (JENKINS-19783) Allow setting of working folder

2016-05-03 Thread stu...@somepointinthefuture.co.nz (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stuart Whelan assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-19783 
 
 
 
  Allow setting of working folder  
 
 
 
 
 
 
 
 
 

Change By:
 
 Stuart Whelan 
 
 
 

Assignee:
 
 Stuart Whelan 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [vault-scm-plugin] (JENKINS-17143) Plugin not saving vault executable path between server restarts

2016-05-03 Thread stu...@somepointinthefuture.co.nz (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stuart Whelan stopped work on  JENKINS-17143 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Stuart Whelan 
 
 
 

Status:
 
 In Progress Open 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [vault-scm-plugin] (JENKINS-22955) Make Version number shown in Changes reports a Link to that Versions info in Vault

2016-05-03 Thread stu...@somepointinthefuture.co.nz (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stuart Whelan assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-22955 
 
 
 
  Make Version number shown in Changes reports a Link to that Versions info in Vault  
 
 
 
 
 
 
 
 
 

Change By:
 
 Stuart Whelan 
 
 
 

Assignee:
 
 Stuart Whelan 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [vault-scm-plugin] (JENKINS-26487) NPE during SCM polling

2016-05-03 Thread stu...@somepointinthefuture.co.nz (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stuart Whelan assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-26487 
 
 
 
  NPE during SCM polling  
 
 
 
 
 
 
 
 
 

Change By:
 
 Stuart Whelan 
 
 
 

Assignee:
 
 Stuart Whelan 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [powershell-plugin] (JENKINS-34581) Please add support for Pipelines to the Powershell plugin

2016-05-03 Thread stu...@somepointinthefuture.co.nz (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stuart Whelan created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34581 
 
 
 
  Please add support for Pipelines to the Powershell plugin  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 powershell-plugin 
 
 
 

Created:
 

 2016/May/03 10:04 PM 
 
 
 

Labels:
 

 pipeline powershell windows microsoft 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Stuart Whelan 
 
 
 
 
 
 
 
 
 
 
I would like to use the powershell plugin from within pipelines, please add support for the pipelines to the powershell plugin. 
This is especially important as we approach Jenkins 2.0 and its move towards pipelines. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [build-flow-plugin] (JENKINS-34580) Enable downstream test result aggregation in Pipeline jobs like in Buildflow jobs

2016-05-03 Thread liyao.capeh...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Yao Li created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34580 
 
 
 
  Enable downstream test result aggregation in Pipeline jobs like in Buildflow jobs  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 Damien Nozay 
 
 
 

Components:
 

 build-flow-plugin, junit-plugin, workflow-plugin 
 
 
 

Created:
 

 2016/May/03 9:54 PM 
 
 
 

Environment:
 

 Jenkins 2.0, Pipeline-plugin 2.0 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Yao Li 
 
 
 
 
 
 
 
 
 
 
In build flow jobs, a post-build step to aggregate build flow test results (of jobs invoked by the build flow job) is available. Can a pipeline job aggregate test results of jobs invoked by the "build" step as well? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [lockable-resources-plugin] (JENKINS-30269) Add workflow support for resource locking

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

 
 
 
 
 
 
 
  Re: Add workflow support for resource locking  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/pipeline-plugin/7596ae10c2035a6c239e4ce8ca3af4c1ee1f78c8 Log: Noting 

JENKINS-30269
 (CC @amuniz) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34571) 2.0 Build Api: No valid crumb was included in the request

2016-05-03 Thread db...@cloudbees.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck resolved as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
https://wiki.jenkins-ci.org/display/JENKINS/Remote+access+API#RemoteaccessAPI-CSRFProtection 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-34571 
 
 
 
  2.0 Build Api: No valid crumb was included in the request  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

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-34548) InjectedTest failure: github plugin fails to start

2016-05-03 Thread vivek.pan...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vivek Pandey commented on  JENKINS-34548 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: InjectedTest failure: github plugin fails to start  
 
 
 
 
 
 
 
 
 
 
Yes, 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-34579) Move the Display Name from Advanced Project Options to under Project name

2016-05-03 Thread matthew.kr...@ericsson.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew Kruer created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34579 
 
 
 
  Move the Display Name from Advanced Project Options to under Project name  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 2016/May/03 8:55 PM 
 
 
 

Environment:
 

 Move the Display Name in the Project Configure Page 
 
 
 

Labels:
 

 confgure 
 
 
 

Priority:
 
  Trivial 
 
 
 

Reporter:
 
 Matthew Kruer 
 
 
 
 
 
 
 
 
 
 
Move the Display Name in the Project Configure Page to under the Project name 
Right now the Display Name for a project in the Advanced Project Options section which seems a bit odd. It is difficult to find unless you know where to look for a few reasons; because the Advanced Project Options is minimized by default and three pages down off screen. Finally, is a common human readable name really an Advanced Project Option? 
I think a better place for the name would be directly under the Project name between it and the Description. It would make it much easier to find.

[JIRA] [github-branch-source-plugin] (JENKINS-34548) InjectedTest failure: github plugin fails to start

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kirill Merkushev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34548 
 
 
 
  InjectedTest failure: github plugin fails to start  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kirill Merkushev 
 
 
 
 
 
 
 
 
 
 Our plugin has maven dependency on github -branch-source  plugin. {code:xml} org.jenkins-ci.pluginsgithub-branch-source1.6{code}Project dependency tree shows github-branch-source plugin has dependency on github plugin, that fails to load during InjectedTest run.{code}[INFO] +- org.jenkins-ci.plugins:github-branch-source:jar:1.6:compile[INFO] |  +- org.jenkins-ci.plugins:github-api:jar:1.75:compile[INFO] |  |  +- org.kohsuke:github-api:jar:1.72:compile[INFO] |  |  \- com.squareup.okhttp:okhttp-urlconnection:jar:2.5.0:compile[INFO] |  | \- com.squareup.okhttp:okhttp:jar:2.5.0:compile[INFO] |  |\- com.squareup.okio:okio:jar:1.6.0:compile[INFO] |  \- com.coravy.hudson.plugins.github:github:jar:1.14.0:compile[INFO] | +- org.apache.commons:commons-lang3:jar:3.4:compile[INFO] | \- org.jenkins-ci.plugins:plain-credentials:jar:1.1:compile{code}InjectedTest are run during test run and it fails with the following error. Failure is random so not easy to reproduce.{code:java}Running InjectedTestTests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 9.611 sec <<< FAILURE! - in InjectedTesttestPluginActive(org.jvnet.hudson.test.PluginAutomaticTestBuilder$OtherTests)  Time elapsed: 0.086 sec  <<< ERROR!java.lang.Error: Plugin github failed to start  at org.jvnet.hudson.test.PluginAutomaticTestBuilder$OtherTests.testPluginActive(PluginAutomaticTestBuilder.java:92)Caused by: java.lang.NullPointerExceptionTests run: 22, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 105.824 sec - in io.jenkins.blueocean.service.embedded.PipelineApiTestResults :Tests in error:   PluginAutomaticTestBuilder$OtherTests.testPluginActive:92  Plugin github faile...{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[JIRA] [github-branch-source-plugin] (JENKINS-34548) InjectedTest failure: github plugin fails to start

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kirill Merkushev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34548 
 
 
 
  InjectedTest failure: github plugin fails to start  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kirill Merkushev 
 
 
 

Component/s:
 
 github-branch-source-plugin 
 
 
 

Component/s:
 
 core 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34548) InjectedTest failure: github plugin fails to start

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kirill Merkushev edited a comment on  JENKINS-34548 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: InjectedTest failure: github plugin fails to start  
 
 
 
 
 
 
 
 
 
 github-branch-source has very old dep to github-plugin which may not work with latest core. But when you tried to override github dep manually, you've done it wrong. The order of dependencies in maven matters a lot. So i just ask you to check overriding in correct order. And if you don't use directly github plugin please don't fill github-plugin component next 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 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-34548) InjectedTest failure: github plugin fails to start

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kirill Merkushev commented on  JENKINS-34548 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: InjectedTest failure: github plugin fails to start  
 
 
 
 
 
 
 
 
 
 
github-branch-source has very old dep to github-plugin which may not work with latest core. But when you tried to override github dep manually, you've done it wrong. The order of dependencies in maven matters a lot. So i just ask you to check overriding in correct order. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34571) 2.0 Build Api: No valid crumb was included in the request

2016-05-03 Thread sjakubow...@pulseinc.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sylvester Jakubowski updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34571 
 
 
 
  2.0 Build Api: No valid crumb was included in the request  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sylvester Jakubowski 
 
 
 
 
 
 
 
 
 
 Fresh install of 2.0 on Ubuntu 14.04SCMSync plugin installedActive Directory plugin installedPort switched to 8081Post requests to the Build api via:sjakubowski@sjakubowski-u:~/hubot2$ curl -i -X POST -H "Content-type: plain"  http://user:pass@10.11.0.163:8081/job/hello/build HTTP/1.1 403 No valid crumb was included in the requestDate: Tue, 03 May 2016 16:59:12 GMTX-Content-Type-Options: nosniffContent-Type: text/html; charset=ISO-8859-1Cache-Control: must-revalidate,no-cache,no-storeContent-Length: 365Server: Jetty(9.2.z-SNAPSHOT)Error 403 No valid crumb was included in the requestHTTP ERROR 403Problem accessing /job/hello/build. Reason:No valid crumb was included in the requestPowered by Jetty://Return above error.Seems different from JENKINS-33813 /var/log/jenkins/jenkins.log returns:May 03, 2016 4:41:37 PM hudson.security.csrf.CrumbFilter doFilterWARNING: No valid crumb was included in request for /hubot/github-repo-listener. Returning 403. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34571) 2.0 Build Api: No valid crumb was included in the request

2016-05-03 Thread sjakubow...@pulseinc.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sylvester Jakubowski commented on  JENKINS-34571 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: 2.0 Build Api: No valid crumb was included in the request  
 
 
 
 
 
 
 
 
 
 
Switching the port back to 8080 didn't fix it either.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [cli] (JENKINS-28346) Inconsistent CLI failiures

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Raymond Accary updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-28346 
 
 
 
  Inconsistent CLI failiures  
 
 
 
 
 
 
 
 
 

Change By:
 
 Raymond Accary 
 
 
 

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] [core] (JENKINS-34548) InjectedTest failure: github plugin fails to start

2016-05-03 Thread vivek.pan...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vivek Pandey commented on  JENKINS-34548 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: InjectedTest failure: github plugin fails to start  
 
 
 
 
 
 
 
 
 
 
As I mentioned, we don't have explicit dependency on github plugin, only github-branch-source and there is this error so not sure what you are asking me to do. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34571) 2.0 Build Api: No valid crumb was included in the request

2016-05-03 Thread sjakubow...@pulseinc.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sylvester Jakubowski commented on  JENKINS-34571 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: 2.0 Build Api: No valid crumb was included in the request  
 
 
 
 
 
 
 
 
 
 
Same issue with AD plugin uninstalled. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [openstack-cloud-plugin] (JENKINS-34578) Cloud Server Options dropdown menus all blank

2016-05-03 Thread zxi...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thanh Ha created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34578 
 
 
 
  Cloud Server Options dropdown menus all blank  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Oliver Gondža 
 
 
 

Components:
 

 openstack-cloud-plugin 
 
 
 

Created:
 

 2016/May/03 8:35 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Thanh Ha 
 
 
 
 
 
 
 
 
 
 
When trying to configure the openstack cloud plugin, despite "Test connection" succeeding. All server cloud options dropdown menus are not set. The only option is None Specified. I'm guessing the plugin tries to query the API but is failing but I do not see any logs in jenkins.log that hints at what the problem could be. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [core] (JENKINS-34573) Running out of Heap Memory (2048m)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Raymond Accary updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34573 
 
 
 
  Running out of Heap Memory (2048m)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Raymond Accary 
 
 
 
 
 
 
 
 
 
 -Setup with less than 100 nodes-Things were going fine, and then the whole setup started freezing; initially errors were indicating that we're running out of PerGen space (I upped that to 512m)-Then same symptoms, setup would freeze; errors were showing running out of heap memory so I increased that 2048 on the master but I can still see the memory increasing significantly (I run GC to avoid the error (clears out more than a G), but I suspect a memory leak somewhere)-I  can ' m including t really include  a  dropbox link  full heap-dump due  to  the heapdump (>800m)  some restrictions ;  it  however here 's  one I obtained during  a list of  the  memory increase  20 objects retained by size:Class NameRetained Sizeorg.eclipse.jetty.webapp.WebAppClassLoader#19 ,  but not at crash time 885,754java .  Hopefully util.Vector#169 ,  that can help identify where the memory usage is happening : https://www 476,255java . dropbox lang . Object[]#106129,476,219org.apache.commons.jexl.util.introspection.Introspector#16,934,833class org.apache.commons.jexl.util.introspection.UberspectImpl6,934,833java.util.HashMap#75456,907,893java.util.HashMap$Entry[]#744056,907,825org.kohsuke.stapler.WebApp#16,267,722java.util.HashMap#47416,265,930java.util.HashMap$Entry[]#729916,265,862class hudson.model.Run5,730,085hudson.util.XStream2#45,730,037 com /s/bollm20ndadffxc/heapdump . hprof?dl=0 thoughtworks.xstream.core.DefaultConverterLookup#35,087,721com.thoughtworks.xstream.converters.SingleValueConverterWrapper#515,050,913com.thoughtworks.xstream.converters.basic.StringConverter#25,050,889java.util.Collections$SynchronizedMap#395,050,861com.thoughtworks.xstream.core.util.WeakCache#25,050,805java.util.WeakHashMap#3895,050,765java.util.WeakHashMap$Entry[]#57814,915,608hudson.model.Hudson#13,763,073 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[JIRA] [msbuild-plugin] (JENKINS-34577) No msbuild section in configuration or global tools after install

2016-05-03 Thread pandr...@alumni.brown.edu (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Andrews created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34577 
 
 
 
  No msbuild section in configuration or global tools after install  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 msbuild-plugin 
 
 
 

Created:
 

 2016/May/03 8:00 PM 
 
 
 

Environment:
 

 Jenkins 2.1 and msbuild plugin 1.25 
 
 
 

Labels:
 

 2.0 configuration plugins plugin 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Peter Andrews 
 
 
 
 
 
 
 
 
 
 
I installed Jenkins 2.1. I installed the msbuild plugin and it said success. There was no msbuild section in either the System Configuration or the (new?) Global tools section. 
Thinking this could be a version issue, I downgraded to Jenkins 1.651.1 and the msbuild section was in the Sytems configuration tab - presumably leftover from install under 2.1

[JIRA] [git-parameter-plugin] (JENKINS-34574) After cleaned workspace doesn't show branches

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Boguslaw Klimas stopped work on  JENKINS-34574 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Boguslaw Klimas 
 
 
 

Status:
 
 In Progress Open 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-parameter-plugin] (JENKINS-34574) After cleaned workspace doesn't show branches

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Boguslaw Klimas resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34574 
 
 
 
  After cleaned workspace doesn't show branches   
 
 
 
 
 
 
 
 
 

Change By:
 
 Boguslaw Klimas 
 
 
 

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] [git-parameter-plugin] (JENKINS-34574) After cleaned workspace doesn't show branches

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Boguslaw Klimas closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34574 
 
 
 
  After cleaned workspace doesn't show branches   
 
 
 
 
 
 
 
 
 

Change By:
 
 Boguslaw Klimas 
 
 
 

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] [docker-plugin] (JENKINS-34238) Flyweight Job Support For Docker Plugin

2016-05-03 Thread sam.mxra...@gmail.com (JIRA)

Title: Message Title

Sam Gleske commented on JENKINS-34238

Re: Flyweight Job Support For Docker Plugin

To clarify, the flyweight task is the task coordinates the sub-tasks and assembles the final results. Each of the sub-tasks already run properly in docker containers. But the coordinating flyweight task does not run in a docker container (the ability is explicitly disabled with a conditional last I checked the source).
Therefore, if the coordinating flyweight task doesn't have a place (e.g. another container or permanent host) to run it then none of the sub-tasks are created.
node() {} blocks aren't very good at matrix building without a lot of complicated scripting. (i.e. saving the script as a variable and reusing it half a dozen times in node blocks). pipeline also doesn't cleanly assemble the results like the matrix building project type can. pipeline plugin is not a good solution for this IMO or current functionality is lacking.

Add Comment

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

[JIRA] [docker-plugin] (JENKINS-34238) Flyweight Job Support For Docker Plugin

2016-05-03 Thread sam.mxra...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sam Gleske edited a comment on  JENKINS-34238 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Flyweight Job Support For Docker Plugin  
 
 
 
 
 
 
 
 
 
 To clarify, the flyweight task is the task coordinates the sub-tasks and assembles the final results.  Each of the sub-tasks already run properly in docker containers.  But the coordinating flyweight task does not run in a docker container (the ability is explicitly disabled with a conditional last I checked the  docker plugin  source).Therefore, if the coordinating flyweight task doesn't have a place (e.g. another container or permanent host) to run it then none of the sub-tasks are created.node() {} blocks aren't very good at matrix building without a lot of complicated scripting.  (i.e. saving the script as a variable and reusing it half a dozen times in node blocks).  pipeline also doesn't cleanly assemble the results like the matrix building project type can.  pipeline plugin is not a good solution for this IMO or current functionality is lacking. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [artifactory-plugin] (JENKINS-34576) Test Connection fails - TLS SNI failure

2016-05-03 Thread aledo...@vml.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex LeDonne created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34576 
 
 
 
  Test Connection fails - TLS SNI failure  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 yossis 
 
 
 

Components:
 

 artifactory-plugin 
 
 
 

Created:
 

 2016/May/03 7:47 PM 
 
 
 

Environment:
 

 Jenkins 1.654 on Centos 7.  OpenJDK 1.7.0_95  Artifactory Plugin 2.4.7  
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Alex LeDonne 
 
 
 
 
 
 
 
 
 
 
Attempting to configure Artifactory Plugin. 
When I enter the server name & credentials and "Test Connection", I get: 
Error occurred while requesting version information: Certificate for <...hostname...> doesn't match any of the subject alternative names: [...default SSL cert names...] 
The https connection test is not properly negotiating SNI, and is getting the default cert from the server instead of the correct cert for the host name.

[JIRA] [workflow-plugin] (JENKINS-34575) Provide warnings of invalid/dangerous pipeline syntax before running

2016-05-03 Thread svano...@cloudbees.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sam Van Oort created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34575 
 
 
 
  Provide warnings of invalid/dangerous pipeline syntax before running  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Jesse Glick 
 
 
 

Components:
 

 workflow-plugin 
 
 
 

Created:
 

 2016/May/03 7:43 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Sam Van Oort 
 
 
 
 
 
 
 
 
 
 
As a user of pipeline, it is problematic that some "obvious" error conditions cannot be corrected until runtime issues are encountered. It would be very helpful to identify these problems before the pipeline can run.  
This does not need to be a perfect test, false positives or false negatives are legitimate if this is supplied as a warning, but anything would be helpful. 
For example: stage steps within parallel blocks are now an error at runtime: https://github.com/jenkinsci/pipeline-stage-step-plugin/pull/3 
In any case where we can trivially see this might occur, it would be helpful to warn the user.  
Likewise, input steps within a workspace (i.e. within a 'node' block) are a problem.

[JIRA] [gitlab-plugin] (JENKINS-34396) Gitlab plugin does not work with jenkins pipeline plugin

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick commented on  JENKINS-34396 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Gitlab plugin does not work with jenkins pipeline plugin  
 
 
 
 
 
 
 
 
 
 
Allowing GitLabPushTrigger to take a Job (reference) would be useful, but it would also be useful to implement SCMSource (from scm-api) so that you could create multibranch projects, analogous to github-branch-source. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34548) InjectedTest failure: github plugin fails to start

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kirill Merkushev commented on  JENKINS-34548 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: InjectedTest failure: github plugin fails to start  
 
 
 
 
 
 
 
 
 
 
When you define dependency to github AFTER branch-source - you actually don't override it. Nothing changes. Please try to define first github dep and then branch-source. (see maven docs for explanation).  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-parameter-plugin] (JENKINS-34574) After cleaned workspace doesn't show branches

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

 
 
 
 
 
 
 
  Re: After cleaned workspace doesn't show branches   
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Boguslaw Klimas Path: src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinition.java src/main/resources/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinition/config.jelly src/main/resources/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterValue/value.jelly http://jenkins-ci.org/commit/git-parameter-plugin/cca023643126e2cd957edcb60e36f7819c3311bf Log: Merge pull request #23 from jenkinsci/bugfix/JENKINS-34574 
After cleaned workspace doesn't show branches 
Compare: https://github.com/jenkinsci/git-parameter-plugin/compare/b1cdf2653e40...cca023643126 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [gitlab-plugin] (JENKINS-34396) Gitlab plugin does not work with jenkins pipeline plugin

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34396 
 
 
 
  Gitlab plugin does not work with jenkins pipeline plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

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] [gitlab-plugin] (JENKINS-34534) Gitlab-Plugin via Job DSL not activated

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34534 
 
 
 
  Gitlab-Plugin via Job DSL not activated  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Summary:
 
 Gitlab-Plugin via  Job  DSL not activated 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34438) Activate JSHint during the build process

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

 
 
 
 
 
 
 
  Re: Activate JSHint during the build process  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: recena Path: war/gulpfile.js war/package.json war/pom.xml http://jenkins-ci.org/commit/jenkins/f523a0ee2317f93e8ad4b4da33bdbbaae5d6fb0b Log: JENKINS-34438 Activate JSHint during the build process 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34438) Activate JSHint during the build process

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

 
 
 
 
 
 
 
  Re: Activate JSHint during the build process  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Daniel Beck Path: war/gulpfile.js war/package.json war/pom.xml war/src/main/js/api/pluginManager.js war/src/main/js/pluginSetupWizardGui.js http://jenkins-ci.org/commit/jenkins/134abbd6d32d9c2520774b1acee2954bc261c162 Log: Merge pull request #2289 from recena/JENKINS-34438 
JENKINS-34438 Activate JSHint during the build process 
Compare: https://github.com/jenkinsci/jenkins/compare/4927968eb0c9...134abbd6d32d 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34438) Activate JSHint during the build process

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

 
 
 
 
 
 
 
  Re: Activate JSHint during the build process  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: recena Path: war/gulpfile.js war/pom.xml http://jenkins-ci.org/commit/jenkins/fc4435c29fbc6afd1165d0da5e14ccfa27e05827 Log: JENKINS-34438 @kzantow's comments were addressed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34438) Activate JSHint during the build process

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

 
 
 
 
 
 
 
  Re: Activate JSHint during the build process  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: recena Path: war/gulpfile.js http://jenkins-ci.org/commit/jenkins/33a765853384ce6a6dbafac99edfcdedf4b3032e Log: JENKINS-34438 The build will fail if there are JSHint errors 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34548) InjectedTest failure: github plugin fails to start

2016-05-03 Thread vivek.pan...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vivek Pandey commented on  JENKINS-34548 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: InjectedTest failure: github plugin fails to start  
 
 
 
 
 
 
 
 
 
 
Its plugin version 2.6 and core 1.652. 
I think I was not clear, we do not override github plugin dependency. It gets included transitively from github-branch-source. Basically just defining dependency on github-branch-source demonstrates this issue. 
In the past we did override github plugin version with version 1.18.2 and this problem was present even then. The dependency was defined as: 

 


org.jenkins-ci.plugins
github-branch-source
1.5


com.coravy.hudson.plugins.github
github
1.18.2

 

 
Hope it 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] [git-parameter-plugin] (JENKINS-34574) After cleaned workspace doesn't show branches

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Boguslaw Klimas started work on  JENKINS-34574 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Boguslaw Klimas 
 
 
 

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] [git-parameter-plugin] (JENKINS-34574) After cleaned workspace doesn't show branches

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Boguslaw Klimas created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34574 
 
 
 
  After cleaned workspace doesn't show branches   
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Boguslaw Klimas 
 
 
 

Components:
 

 git-parameter-plugin 
 
 
 

Created:
 

 2016/May/03 7:06 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Boguslaw Klimas 
 
 
 
 
 
 
 
 
 
 
Caused by: hudson.plugins.git.GitException: Command "git -c core.askpass=true fetch --tags --progress https://github.com/klimas7/Learn.git +refs/heads/:refs/remotes/origin/ --prune" returned status code 128: stdout: stderr: fatal: Not a git repository (or any of the parent directories): .git 
 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1719) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1463) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:63) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:314) at net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition.generateContents(GitParameterDefinition.java:278) at net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition$DescriptorImpl.doFillValueItems(GitParameterDefinition.java:408) ... 74 more

[JIRA] [core] (JENKINS-34573) Running out of Heap Memory (2048m)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Raymond Accary updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34573 
 
 
 
  Running out of Heap Memory (2048m)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Raymond Accary 
 
 
 
 
 
 
 
 
 
 -Setup with less than 100 nodes-Things were going fine, and then the whole setup started freezing; initially errors were indicating that we're running out of PerGen space (I upped that to 512m)-Then same symptoms, setup would freeze; errors were showing running out of heap memory so I increased that 2048 on the master but I can still see the memory increasing significantly (I run GC to avoid the error (clears out more than a G), but I suspect a memory leak somewhere)-I'm including a dropbox link to the heapdump (>800m); it's one I obtained during the memory increase, but not at crash time. Hopefully, that can help identify where the memory usage is happening  : https://www . dropbox.com/s/bollm20ndadffxc/heapdump.hprof?dl=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] [quality-gates-plugin] (JENKINS-34427) Sonar user password is stored in plain text in every job configuration

2016-05-03 Thread m...@jochen-fuerbacher.de (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jochen A. Fürbacher edited a comment on  JENKINS-34427 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Sonar user password is stored in plain text in every job configuration   
 
 
 
 
 
 
 
 
 
 Hi Ivana,I see two problems Stefan mentioned:- Security: When you configure the sonar instance globally and configure a job to use this sonar instance, then the CURRENT password of the sonar instance (that one, that's configured globally) get's also stored in the job configuration. All users (also those without admin rights) can see that password. It's not just the default password!- (Not sure about that) When the admin configures a sonar instance globally, and a job get's configured to use that instance (how discribed above), the  vurrent  current  password get's stored in the job configuration. When the admin changes to password for one this sonar instance, then the old password stays remain in the job config.Stefan and I noticed another major security issue: When the admin does a global configuration, the credentials (incl. the sonar password) get's logged in plaintext! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34573) Running out of Heap Memory (2048m)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Raymond Accary created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34573 
 
 
 
  Running out of Heap Memory (2048m)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 plugins1.png, plugins2.png, plugins3.png 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 2016/May/03 6:56 PM 
 
 
 

Environment:
 

 Jenkins 2.1; list of plugins shown in Attachments (plugins1/2/3.png) 
 
 
 

Priority:
 
  Blocker 
 
 
 

Reporter:
 
 Raymond Accary 
 
 
 
 
 
 
 
 
 
 
-Setup with less than 100 nodes -Things were going fine, and then the whole setup started freezing; initially errors were indicating that we're running out of PerGen space (I upped that to 512m) -Then same symptoms, setup would freeze; errors were showing running out of heap memory so I increased that 2048 on the master but I can still see the memory increasing significantly (I run GC to avoid the error (clears out more than a G), but I suspect a memory leak somewhere) 
-I'm including a dropbox link to the heapdump (>800m); it's one I obtained during the memory increase, but not at crash time.

[JIRA] [quality-gates-plugin] (JENKINS-34427) Sonar user password is stored in plain text in every job configuration

2016-05-03 Thread m...@jochen-fuerbacher.de (JIRA)

Title: Message Title

Jochen A. Fürbacher commented on JENKINS-34427

Re: Sonar user password is stored in plain text in every job configuration

Hi Ivana,
I see two problems Stefan mentioned:

Security: When you configure the sonar instance globally and configure a job to use this sonar instance, then the CURRENT password of the sonar instance (that one, that's configured globally) get's also stored in the job configuration. All users (also those without admin rights) can see that password. It's not just the default password!

(Not sure about that) When the admin configures a sonar instance globally, and a job get's configured to use that instance (how discribed above), the vurrent password get's stored in the job configuration. When the admin changes to password for one this sonar instance, then the old password stays remain in the job config.

Stefan and I noticed another major security issue: When the admin does a global configuration, the credentials (incl. the sonar password) get's logged in plaintext!

Add Comment

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

[JIRA] [kubernetes-plugin] (JENKINS-34380) kubernetes plugin creates an unbounded number of Netty I/O threads

2016-05-03 Thread jenkins...@carlossanchez.eu (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Carlos Sanchez commented on  JENKINS-34380 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: kubernetes plugin creates an unbounded number of Netty I/O threads  
 
 
 
 
 
 
 
 
 
 
I would try upgrading kubernetes-client or the netty lib to see if that fixes it 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [cli] (JENKINS-28346) Inconsistent CLI failiures