[JIRA] [git-plugin] (JENKINS-34782) Unable to checkout from Git, timeout error

2016-05-12 Thread shruthi_nirvana...@infosys.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shruthi Nirvanappa created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34782 
 
 
 
  Unable to checkout from Git, timeout error  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Mark Waite 
 
 
 

Components:
 

 git-plugin 
 
 
 

Created:
 

 2016/May/13 5:52 AM 
 
 
 

Environment:
 

 windows machine 
 
 
 

Labels:
 

 git 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Shruthi Nirvanappa 
 
 
 
 
 
 
 
 
 
 
Hi, 
While i try to checkout from Git, it is failing because of time out error. PFB the complete log: 
Started by user anonymous Building in workspace C:\Users\nidhish_raj\.jenkins\workspace\Test_ICIP > C:\Program Files (x86)\Git\bin\git.exe rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > C:\Program Files (x86)\Git\bin\git.exe config remote.origin.url http://tbx-blv-ardv-01.ca.boeing.com/tbx_dev/toolbox.git # timeout=10 Fetching upstream changes from http://tbx-blv-ardv-01.ca.boeing.com/tbx_dev/toolbox.git > C:\Program Files (x86)\Git\bin\git.exe --version # timeout=10 using .gitcredentials to set credentials > C:\Program Files 

[JIRA] [export-params-plugin] (JENKINS-34783) Parameters not written to slave after upgrade to latest LTS

2016-05-12 Thread store...@tibco.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stefan Toresson created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34783 
 
 
 
  Parameters not written to slave after upgrade to latest LTS  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 rin_ne 
 
 
 

Components:
 

 export-params-plugin, multijob-plugin 
 
 
 

Created:
 

 2016/May/13 5:52 AM 
 
 
 

Environment:
 

 Centos 6.7 Jenkins LTS 1.651.2 
 
 
 

Priority:
 
  Blocker 
 
 
 

Reporter:
 
 Stefan Toresson 
 
 
 
 
 
 
 
 
 
 
We have Multijobs with parameters that is passed down to the slaves and written to file for consumption. After an automatic upgrade to LTS 1.651.2 the only content in parameters.properties are a time-stamp and effectively failing all jobs as no parameters were found.  
There was an update for the multijob plugin after the upgrade, but that did not fix the problem. I could not see anything useful in the logs. 
After reverting to LTS 1.651.1 it works again. 
 
 
 
 
 
 
 
 
 
 
 
 

  

[JIRA] [remote-terminal-access-plugin] (JENKINS-19218) Interactive Terminal too small

2016-05-12 Thread sreekanth.p...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sreekanth Paku commented on  JENKINS-19218 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Interactive Terminal too small  
 
 
 
 
 
 
 
 
 
 
Hi, 
I too am facing this issue with Jenkins Remote Terminal access plugin. When can this fix be available for updating? 
Sreekanth Paku 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [mstest-plugin] (JENKINS-34777) mstest-plugin durations can overflow test-results-analyzer-plugin

2016-05-12 Thread stefan.dris...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stefan Drissen commented on  JENKINS-34777 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: mstest-plugin durations can overflow test-results-analyzer-plugin  
 
 
 
 
 
 
 
 
 
 
Simple test case is not triggering the JSONException - lowered status to trivial while digging deeper. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [mstest-plugin] (JENKINS-34777) mstest-plugin durations can overflow test-results-analyzer-plugin

2016-05-12 Thread stefan.dris...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stefan Drissen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34777 
 
 
 
  mstest-plugin durations can overflow test-results-analyzer-plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Stefan Drissen 
 
 
 

Priority:
 
 Blocker Trivial 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [cloudbees-folder-plugin] (JENKINS-34781) Cleanup node workspaces on orphan removal

2016-05-12 Thread michael.ne...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Neale created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34781 
 
 
 
  Cleanup node workspaces on orphan removal  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Michael Neale 
 
 
 

Components:
 

 cloudbees-folder-plugin 
 
 
 

Created:
 

 2016/May/13 2:16 AM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Michael Neale 
 
 
 
 
 
 
 
 
 
 
With computed folders, such as you may use with multibranch plugins (like github or bitbucket branch source) and a "git flow" way of working, you tend to create a lot of short lived branch jobs.  
These branch jobs are removed not long after creation (as pull requests are merged) and the job removed, however the workspace on any nodes can live around for up to a month before it is cleaned up by WorkspaceCleanupThread (https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/WorkspaceCleanupThread.java#L115) 
I am proposing that in the removal of orphans a similar scanning and removal of workspaces could take place. This can supplement the cleanup thread and make for less garbage filling up disk.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
   

[JIRA] [s3-plugin] (JENKINS-34780) Files from the entry path are not copied to S3 bucket's root directory relatively

2016-05-12 Thread thai...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thai Pham created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34780 
 
 
 
  Files from the entry path are not copied to S3 bucket's root directory relatively  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Alexander A 
 
 
 

Components:
 

 s3-plugin 
 
 
 

Created:
 

 2016/May/13 2:03 AM 
 
 
 

Environment:
 

 s3-plugin 0.10.1 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Thai Pham 
 
 
 
 
 
 
 
 
 
 
It looks to me that 0.10.1 has changed the behaviour of how files are copied. In previous versions, I configured `source` to be something like `project/dest/**` and files that are inside and beneath `project/dest` directory are copied to the root directory of my bucket. However, after upgrading to version 0.10.1, the plugin duplicated the directory structure in my S3 bucket as well. So my files are copied to `project/dest` directory in the bucket, which is not what I expected. I'm not sure if this is a bug or should I file an improvement request that we can configure the plugin to keep our directory structure in S3 bucket or not? 
 
 
 
 
 
 
 
 
 
 
 
 
  

[JIRA] [github-organization-folder-plugin] (JENKINS-34475) github-org folder is incompatible with git flow implementations - branch names break builds

2016-05-12 Thread michael.ne...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Neale commented on  JENKINS-34475 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: github-org folder is incompatible with git flow implementations - branch names break builds  
 
 
 
 
 
 
 
 
 
 
I have been bitten by this too, only not with python virtualenv, but "npm run" scripts. Same issue (it seems tripped up by the %). 
Technically % is reserved: https://en.wikipedia.org/wiki/Filename  
It is hard to think up an alternative scheme, as people could put anything in branch names right?  Note these branch names are used both in uri's in Jenkins as well as file paths: 
Possibility:  feature/TEST-123 

> /var/lib/jenkins/jobs/apache-org/jobs/apache-project-aaa-api/branches/feature_
_TEST-123 
if it was "special case" for "/" could work, but as other things could appear in branch names, what is the generic encoding to be used for filenames? (as these end up on disk).  
The rules for branch names:  http://stackoverflow.com/questions/3651860/which-characters-are-illegal-within-a-branch-name 
so some kind of encoding is needed, but perhaps something as generic as URL encoding is overkill, and we can have something that works for both URIs and file systems. As long as it looks reasonable when looking at the URI and also the filesystem that would be nice, but it seems a shame this has to come to this because of poor tooling.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [p4-plugin] (JENKINS-34014) p4unshelve task uses the wrong Perforce workspace

2016-05-12 Thread mr...@sjm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Rose edited a comment on  JENKINS-34014 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: p4unshelve task uses the wrong Perforce workspace  
 
 
 
 
 
 
 
 
 
 [~p4paul]: This is just an FYI in you want to look into it. I already have a workaround.{code:java}sh "p4 unshelve ... " {code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [p4-plugin] (JENKINS-34014) p4unshelve task uses the wrong Perforce workspace

2016-05-12 Thread mr...@sjm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Rose updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34014 
 
 
 
  p4unshelve task uses the wrong Perforce workspace  
 
 
 
 
 
 
 
 
 
 
Paul Allen: This is just an FYI in you want to look into it. I already have a workaround. 

 

sh "p4 unshelve ...
 

 
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Rose 
 
 
 

Priority:
 
 Major 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] [p4-plugin] (JENKINS-34014) p4unshelve task uses the wrong Perforce workspace

2016-05-12 Thread mr...@sjm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Rose assigned an issue to Paul Allen 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34014 
 
 
 
  p4unshelve task uses the wrong Perforce workspace  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Rose 
 
 
 

Assignee:
 
 Paul Allen 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34677) Pipeline/Timeout/Xvnc: "timeout" with a ""wrap" inside don't time out.

2016-05-12 Thread de...@ikedam.jp (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ikedam assigned an issue to Jesse Glick 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
timeout step in pipeline is not related to build-timeout-plugin. Removed it from component/s. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-34677 
 
 
 
  Pipeline/Timeout/Xvnc: "timeout" with a ""wrap" inside don't time out.  
 
 
 
 
 
 
 
 
 

Change By:
 
 ikedam 
 
 
 

Component/s:
 
 build-timeout-plugin 
 
 
 

Assignee:
 
 Kohsuke Kawaguchi Jesse Glick 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [delivery-pipeline-plugin] (JENKINS-34616) delivery-pipeline (snippet generator) - fails to create script using Project Based Security

2016-05-12 Thread de...@ikedam.jp (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ikedam updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34616 
 
 
 
  delivery-pipeline (snippet generator) - fails to create script using Project Based Security  
 
 
 
 
 
 
 
 
 

Change By:
 
 ikedam 
 
 
 

Component/s:
 
 matrix-auth-plugin 
 
 
 

Component/s:
 
 authorize-project-plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [github-organization-folder-plugin] (JENKINS-34779) repo polling

2016-05-12 Thread dan...@jasek.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dan Jasek created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34779 
 
 
 
  repo polling  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Kohsuke Kawaguchi 
 
 
 

Components:
 

 github-organization-folder-plugin 
 
 
 

Created:
 

 2016/May/12 11:27 PM 
 
 
 

Priority:
 
  Trivial 
 
 
 

Reporter:
 
 Dan Jasek 
 
 
 
 
 
 
 
 
 
 
I would like to be able to configure my github organization folder to use scm polling for jobs it creates. 
My Jenkins server is behind a firewall and cannot be accessed by Github. The current web hook functionality doesn't work. I need some other way to trigger builds. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
   

[JIRA] [authorize-project-plugin] (JENKINS-34279) Fails with Active Directory

2016-05-12 Thread de...@ikedam.jp (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ikedam commented on  JENKINS-34279 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Fails with Active Directory  
 
 
 
 
 
 
 
 
 
 
Is there any output in the sustem log? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [authorize-project-plugin] (JENKINS-34279) Fails with Active Directory

2016-05-12 Thread de...@ikedam.jp (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ikedam edited a comment on  JENKINS-34279 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Fails with Active Directory  
 
 
 
 
 
 
 
 
 
 Is there any output in the  sustem  system  log? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34778) Unable to Create or Modify List View Section within a Sectioned View

2016-05-12 Thread matthew.kr...@ericsson.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew Kruer created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34778 
 
 
 
  Unable to Create or Modify List View Section within a Sectioned View  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Timothy Bingaman 
 
 
 

Components:
 

 core, dropdown-viewstabbar-plugin, nested-view-plugin, sectioned-view-plugin 
 
 
 

Created:
 

 2016/May/12 11:23 PM 
 
 
 

Environment:
 

 Jenkins ver. 1.642.3  Java ver. 1.7  Nested View Plugin 1.14  Sectioned View Plugin 1.20  DropDown ViewsTabBar Plugin 1.7 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Matthew Kruer 
 
 
 
 
 
 
 
 
 
 
Steps to reproduce 
 

Create a new Sectioned View
 

Add List View Section
 

Save or Apply
 
 
This may be related to this bug as well https://issues.jenkins-ci.org/browse/JENKINS-34535?jql=issuetype%20%3D%20Bug%20AND%20text%20~%20%22is%20not%20a%20Boolean%22  

   

[JIRA] [matrix-project-plugin] (JENKINS-34758) Parameters are not passed to child jobs in multi-configuration projects

2016-05-12 Thread o...@nerdnetworks.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Owen Mehegan commented on  JENKINS-34758 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Parameters are not passed to child jobs in multi-configuration projects  
 
 
 
 
 
 
 
 
 
 
You sunk my battleship! Er, I mean, broke all my matrix jobs!  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [credentials-binding-plugin] (JENKINS-24805) Mask credentials in Build Log

2016-05-12 Thread be_...@sbcglobal.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brian Ray commented on  JENKINS-24805 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Mask credentials in Build Log  
 
 
 
 
 
 
 
 
 
 
Apologies as this may be a mild hijack of this issue, but I want to find out whether this edge masking case warrants a JIRA and whether one already exists (don't think so, I just scanned all with component = credentials-binding-plugin). 
Minimal reproduction script is: 

 

node() {
  withCredentials( [] ) {
  echo 'Test of the credentials binding decorator'
  }
}
 

 
So, passing an empty list of credentials--my concrete use case constructs the list based on upstream factors; some of the times there are no credentials to resolve so the list is empty. The relevant part of the log then winds up like this: 

 
[Pipeline] Bind credentials to variables : Start
[Pipeline] withCredentials {
[Pipeline] echo
Test of the credentials binding decorator

[Pipeline] } //withCredentials
[Pipeline] Bind credentials to variables : End

 

 
I believe it's because BindingStep.Filter::Filter builds a zero-length pattern in this scenario, which matches like crazy. 
Is this a bug? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 

[JIRA] [git-plugin] (JENKINS-33984) Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1)

2016-05-12 Thread petrikvanderve...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Petrik van der Velde commented on  JENKINS-33984 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1)  
 
 
 
 
 
 
 
 
 
 
We're seeing this behaviour as well. Happens fairly frequently because we use GitFlow. For the first build of a release branch both the release branch and develop point to the same commit. Unfortunately we cannot set the local branch name because we don't know in advance what the branch name is going to be, e.g. the user might be building release/1.2.0, but we can't set that configuration in jenkins because that number will be changing. 
Normally this might not be that important but in our case we're using GitVersion (https://github.com/GitTools/GitVersion) which calculates the version number based on the state of the repository and part of that is the branch you're on and, in case of release and hotfix branches, the 'version' of the branch. So we really need jenkins to checkout the correct branch (and ideally into a local branch with the same name) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [collapsing-console-sections-plugin] (JENKINS-34757) NPE while trying to access console in Jenkins 2.0 / 2.3

2016-05-12 Thread fred...@hotmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Fred G commented on  JENKINS-34757 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: NPE while trying to access console in Jenkins 2.0 / 2.3  
 
 
 
 
 
 
 
 
 
 
Probably a duplicate of 

JENKINS-30690
. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [collapsing-console-sections-plugin] (JENKINS-34757) NPE while trying to access console in Jenkins 2.0 / 2.3

2016-05-12 Thread fred...@hotmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Fred G assigned an issue to Dean Yu 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34757 
 
 
 
  NPE while trying to access console in Jenkins 2.0 / 2.3  
 
 
 
 
 
 
 
 
 

Change By:
 
 Fred G 
 
 
 

Assignee:
 
 Fred G Dean Yu 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [collapsing-console-sections-plugin] (JENKINS-34757) NPE while trying to access console in Jenkins 2.0 / 2.3

2016-05-12 Thread fred...@hotmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Fred G updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34757 
 
 
 
  NPE while trying to access console in Jenkins 2.0 / 2.3  
 
 
 
 
 
 
 
 
 
 

 

Caused by: java.lang.NullPointerException
at org.jvnet.hudson.plugins.collapsingconsolesections.CollapsingSectionsConfiguration.getSectionDefinitions(CollapsingSectionsConfiguration.java:56)
at org.jvnet.hudson.plugins.collapsingconsolesections.CollapsingSectionNote$DescriptorImpl.getSectionDefinitions(CollapsingSectionNote.java:103)
at org.jvnet.hudson.plugins.collapsingconsolesections.CollapsingSectionAnnotatorFactory.newInstance(CollapsingSectionAnnotatorFactory.java:40)
 

 
Looks like collapsing-console-sections-plugin is actually causing the NPE. 
 
 
 
 
 
 
 
 
 

Change By:
 
 Fred G 
 
 
 

Component/s:
 
 collapsing-console-sections-plugin 
 
 
 

Component/s:
 
 console-column-plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[JIRA] [config-file-provider-plugin] (JENKINS-14977) Parameter type to select config file

2016-05-12 Thread rs...@teamexos.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Sung commented on  JENKINS-14977 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Parameter type to select config file  
 
 
 
 
 
 
 
 
 
 
Based on the description, I'm looking for the same thing. 
Right now, the configuration file desired needs to be selected at job configuration so there is no way to dynamically select which config file to use. It would be great if file selection could be based on parameters like the ones supplied in parameterized builds. 
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] [parameterized-trigger-plugin] (JENKINS-34319) Cannot trigger multi-configuration from job

2016-05-12 Thread m...@arnoldbechtoldt.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arnold Bechtoldt edited a comment on  JENKINS-34319 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cannot trigger multi-configuration from job  
 
 
 
 
 
 
 
 
 
 I'm seeing a very similar issue. Since updating Jenkins to 2.3, this plugin works for freestyle jobs, but it doesn't for multi-config jobs. The parameter seems to be overridden by an empty string. Even the default will be overridden.Could someone verify this please? Does #JENKINS-34474 address this problem? {noformat}WARNING: Skipped parameter `CLEANUP` as it is undefined on `xyz`. Set `-Dhudson.model.ParametersAction.keepUndefinedParameters`=true to allow undefined parameters to be injected as environment variables or `-Dhudson.model.ParametersAction.safeParameters=[comma-separated list]` to whitelist specific parameter names, even though it represents a security breach{noformat} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ghprb-plugin] (JENKINS-34762) PR status cannot be updated due to filtered parameters

2016-05-12 Thread nickbr...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nicholas Brown commented on  JENKINS-34762 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: PR status cannot be updated due to filtered parameters  
 
 
 
 
 
 
 
 
 
 
I'd guess that https://github.com/jenkinsci/stash-pullrequest-builder-plugin may have the same problem as it appears define extra parameters in a similar way. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [parameterized-trigger-plugin] (JENKINS-34319) Cannot trigger multi-configuration from job

2016-05-12 Thread m...@arnoldbechtoldt.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arnold Bechtoldt commented on  JENKINS-34319 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cannot trigger multi-configuration from job  
 
 
 
 
 
 
 
 
 
 
I'm seeing a very similar issue. Since updating Jenkins to 2.3, this plugin works for freestyle jobs, but it doesn't for multi-config jobs. The parameter seems to be overridden by an empty string. Even the default will be overridden. 
Could someone verify this please? Does #JENKINS-34474 address this problem? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [mstest-plugin] (JENKINS-34777) mstest-plugin durations can overflow test-results-analyzer-plugin

2016-05-12 Thread stefan.dris...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stefan Drissen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34777 
 
 
 
  mstest-plugin durations can overflow test-results-analyzer-plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Stefan Drissen 
 
 
 
 
 
 
 
 
 
 Note: all of the below has not been verified, currently waiting for a free node to test the simple test case.Too many digits are used as duration.src/main/resources/hudson/plugins/mstest/mstest-to-junit.xsl is taking the entire duration from the trx and putting it in the JUnit time:{noformat}      {noformat}However, the totalTimeTaken is 'only' a float and net.sf.json.JSONUtils.testValidity throws a "JSON does not allow non-finite numbers" when the value is too large for a float. Since a float can only have 6-8 digits the duration above fails.So either:# use a double instead of a float# adjust the xsl to keep the time down:{ { noformat}    {noformat } } When starting the test results analyzer, Jenkins sytem log contains:{ { noformat} May 12, 2016 9:52:02 PM WARNING org.kohsuke.stapler.HttpResponseRenderer$Default handleJavaScriptProxyMethodCallcall to /$stapler/bound/37513732-3136-4970-86bb-052ba76502ab/getTreeResult failednet.sf.json.JSONException: JSON does not allow non-finite numbers. at net.sf.json.util.JSONUtils.testValidity(JSONUtils.java:629) at net.sf.json.AbstractJSON._processValue(AbstractJSON.java:245) at net.sf.json.JSONObject._processValue(JSONObject.java:2599) at net.sf.json.JSONObject.processValue(JSONObject.java:2665) at net.sf.json.JSONObject.element(JSONObject.java:1738) at net.sf.json.JSONObject.element(JSONObject.java:1716) at net.sf.json.JSONObject.put(JSONObject.java:2328) at org.jenkinsci.plugins.testresultsanalyzer.result.data.ResultData.getJsonObject(ResultData.java:171) at org.jenkinsci.plugins.testresultsanalyzer.result.info.Info.getBuildJson(Info.java:41) at org.jenkinsci.plugins.testresultsanalyzer.result.info.Info.getJsonObject(Info.java:57) at org.jenkinsci.plugins.testresultsanalyzer.result.info.ResultInfo.getJsonObject(ResultInfo.java:31) at org.jenkinsci.plugins.testresultsanalyzer.JsTreeUtil.getJsTree(JsTreeUtil.java:21) at org.jenkinsci.plugins.testresultsanalyzer.TestResultsAnalyzerAction.getTreeResult(TestResultsAnalyzerAction.java:177) {noformat } } Example testsuites.xml file:{ { noformat}     {noformat } } 
 
 
 
 
 
 
 
 
 
 
 
  

[JIRA] [mstest-plugin] (JENKINS-34777) mstest-plugin durations can overflow test-results-analyzer-plugin

2016-05-12 Thread stefan.dris...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stefan Drissen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34777 
 
 
 
  mstest-plugin durations can overflow test-results-analyzer-plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Stefan Drissen 
 
 
 
 
 
 
 
 
 
 Note: all of the below has not been verified, currently waiting for a free node to test the simple test case.Too many digits are used as duration.src/main/resources/hudson/plugins/mstest/mstest-to-junit.xsl is taking the entire duration from the trx and putting it in the JUnit time:{ { noformat}    {noformat } } However, the totalTimeTaken is 'only' a float and net.sf.json.JSONUtils.testValidity throws a "JSON does not allow non-finite numbers" when the value is too large for a float. Since a float can only have 6-8 digits the duration above fails.So either:# use a double instead of a float# adjust the xsl to keep the time down:{{  }}When starting the test results analyzer, Jenkins sytem log contains:{{May 12, 2016 9:52:02 PM WARNING org.kohsuke.stapler.HttpResponseRenderer$Default handleJavaScriptProxyMethodCallcall to /$stapler/bound/37513732-3136-4970-86bb-052ba76502ab/getTreeResult failednet.sf.json.JSONException: JSON does not allow non-finite numbers. at net.sf.json.util.JSONUtils.testValidity(JSONUtils.java:629) at net.sf.json.AbstractJSON._processValue(AbstractJSON.java:245) at net.sf.json.JSONObject._processValue(JSONObject.java:2599) at net.sf.json.JSONObject.processValue(JSONObject.java:2665) at net.sf.json.JSONObject.element(JSONObject.java:1738) at net.sf.json.JSONObject.element(JSONObject.java:1716) at net.sf.json.JSONObject.put(JSONObject.java:2328) at org.jenkinsci.plugins.testresultsanalyzer.result.data.ResultData.getJsonObject(ResultData.java:171) at org.jenkinsci.plugins.testresultsanalyzer.result.info.Info.getBuildJson(Info.java:41) at org.jenkinsci.plugins.testresultsanalyzer.result.info.Info.getJsonObject(Info.java:57) at org.jenkinsci.plugins.testresultsanalyzer.result.info.ResultInfo.getJsonObject(ResultInfo.java:31) at org.jenkinsci.plugins.testresultsanalyzer.JsTreeUtil.getJsTree(JsTreeUtil.java:21) at org.jenkinsci.plugins.testresultsanalyzer.TestResultsAnalyzerAction.getTreeResult(TestResultsAnalyzerAction.java:177)}}Example testsuites.xml file:{{   }} 
 
 
 
 
 
 
 
 
 
 
 
 
 

[JIRA] [mstest-plugin] (JENKINS-34777) mstest-plugin durations can overflow test-results-analyzer-plugin

2016-05-12 Thread stefan.dris...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stefan Drissen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34777 
 
 
 
  mstest-plugin durations can overflow test-results-analyzer-plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Stefan Drissen 
 
 
 

Summary:
 
 mstest-plugin durations can overflow  testresult plug  test - in results-analyzer-plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [mstest-plugin] (JENKINS-34777) mstest-plugin durations can overflow testresult plug-in

2016-05-12 Thread stefan.dris...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stefan Drissen created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34777 
 
 
 
  mstest-plugin durations can overflow testresult plug-in  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Ivo Bellin Salarin 
 
 
 

Components:
 

 mstest-plugin, test-results-analyzer-plugin 
 
 
 

Created:
 

 2016/May/12 8:56 PM 
 
 
 

Environment:
 

 Windows 8.1 x64  Jenkins 1.630  mstest-plugin 0.19  test-results-analyzer-plugin 0.3.4 
 
 
 

Priority:
 
  Blocker 
 
 
 

Reporter:
 
 Stefan Drissen 
 
 
 
 
 
 
 
 
 
 
Note: all of the below has not been verified, currently waiting for a free node to test the simple test case. 
Too many digits are used as duration. 
src/main/resources/hudson/plugins/mstest/mstest-to-junit.xsl is taking the entire duration from the trx and putting it in the JUnit time: 
{{   }} 
However, the totalTimeTaken is 'only' a float and net.sf.json.JSONUtils.testValidity throws a "JSON does not allow non-finite numbers" when the value is too large for a float. Since a float can only have 6-8 digits the duration above fails. 
So either: 
 

use a double instead of a float
 

[JIRA] [warnings-plugin] (JENKINS-34157) Warnings plugin doesn't allow environment variables in file names

2016-05-12 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ulli Hafner commented on  JENKINS-34157 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Warnings plugin doesn't allow environment variables in file names  
 
 
 
 
 
 
 
 
 
 
I see. I thought both types are expanded by the API. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [core] (JENKINS-11889) Suspended slave do not start accepting tasks when policy changed

2016-05-12 Thread jenk...@mockies.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Vogtländer commented on  JENKINS-11889 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Suspended slave do not start accepting tasks when policy changed  
 
 
 
 
 
 
 
 
 
 
I see this issue on 1.651.1 LTS  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34740) Cannot create new items after upgrade to 2.2 when underscore is present in the hostname

2016-05-12 Thread roytin...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Roy Tinker commented on  JENKINS-34740 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cannot create new items after upgrade to 2.2 when underscore is present in the hostname  
 
 
 
 
 
 
 
 
 
 
I just upgraded the machine to Jenkins 2.3, and the issue is still present. 
Is there a "safe mode" where I can quickly disable all but the core plugins, and then restore them (without losing any settings those plugins defined)? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [pipeline-stage-view-plugin] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage

2016-05-12 Thread danagoye...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dana Goyette commented on  JENKINS-33185 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Visualize parallel steps within a Pipeline Stage  
 
 
 
 
 
 
 
 
 
 
Some of the concepts above (such as the "on click" screenshot) just didn't seem tailored well to that case; hence my comment. That's all. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34740) Cannot create new items after upgrade to 2.2 when underscore is present in the hostname

2016-05-12 Thread roytin...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Roy Tinker edited a comment on  JENKINS-34740 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cannot create new items after upgrade to 2.2 when underscore is present in the hostname  
 
 
 
 
 
 
 
 
 
 A few more details:For the itemCategories XHR, the extra headers disappear and the server returns 200 OK (instead of 403 Not Authorized) if I grant Administer privileges to the Anonymous user and then access as anonymous... but the response itself is still blank and therefore the page is blank.When accessing via a hostname with an underscore, I'm seeing problems in several other places throughout Jenkins -- but the problems all disappear if I access via a hostname without an underscore (which I'm doing by adding an alternate name for the Jenkins server's IP address in my machine's hosts file). Here's a few I could compile in 10 minutes:* At /configureSecurity/: XHR calls to /descriptorByName/hudson.security.GlobalMatrixAuthorizationStrategy/checkName?value=%5Busername%5D return either 403 (if logged in) or 200 but blank response (if anonymous w/anonymous granted Administer)* At /configureSecurity/: clicking Save or Apply results in an error where an ActiveDirectorySecurityRealm failed to instantiate in org.kohsuke.stapler.Stapler.tryInvoke (Stapler.java:796)* At /configure: XHR call to /$stapler/bound/[ long a  GUID]/render returns 404 Not Found* At /configure: all other XHR calls executed on load (/checkAdminAddress, checkDefaultSuffix, checkGitUrl, etc.) return 200 OK but have an empty response. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34740) Cannot create new items after upgrade to 2.2 when underscore is present in the hostname

2016-05-12 Thread roytin...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Roy Tinker edited a comment on  JENKINS-34740 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cannot create new items after upgrade to 2.2 when underscore is present in the hostname  
 
 
 
 
 
 
 
 
 
 A few more details:For the itemCategories XHR, the extra headers disappear and the server returns 200 OK (instead of 403 Not Authorized) if I grant Administer privileges to the Anonymous user and then access as anonymous... but the response itself is still blank and therefore the page is blank.When accessing via a hostname with an underscore, I'm seeing problems in several other places throughout Jenkins -- but the problems all disappear if I access via a hostname without an underscore (which I'm doing by adding an alternate name for the Jenkins server's IP address in my machine's hosts file). Here's a few I could compile in 10 minutes:* At /configureSecurity/: XHR calls to /descriptorByName/hudson.security.GlobalMatrixAuthorizationStrategy/checkName?value=%5Busername%5D return either 403 (if logged in) or 200 but blank response (if anonymous w/anonymous granted Administer)* At /configureSecurity/: clicking Save or Apply results in  a pretty massive  an  error where an ActiveDirectorySecurityRealm failed to instantiate in org.kohsuke.stapler.Stapler.tryInvoke (Stapler.java:796)* At /configure: XHR call to /$stapler/bound/[long GUID]/render returns 404 Not Found* At /configure: all other XHR calls executed on load (/checkAdminAddress, checkDefaultSuffix, checkGitUrl, etc.) return 200 OK but have an empty response. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34740) Cannot create new items after upgrade to 2.2 when underscore is present in the hostname

2016-05-12 Thread roytin...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Roy Tinker commented on  JENKINS-34740 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cannot create new items after upgrade to 2.2 when underscore is present in the hostname  
 
 
 
 
 
 
 
 
 
 
A few more details: 
For the itemCategories XHR, the extra headers disappear and the server returns 200 OK (instead of 403 Not Authorized) if I grant Administer privileges to the Anonymous user and then access as anonymous... but the response itself is still blank and therefore the page is blank. 
When accessing via a hostname with an underscore, I'm seeing problems in several other places throughout Jenkins – but the problems all disappear if I access via a hostname without an underscore (which I'm doing by adding an alternate name for the Jenkins server's IP address in my machine's hosts file). Here's a few I could compile in 10 minutes: 
 

At /configureSecurity/: XHR calls to /descriptorByName/hudson.security.GlobalMatrixAuthorizationStrategy/checkName?value=%5Busername%5D return either 403 (if logged in) or 200 but blank response (if anonymous w/anonymous granted Administer)
 

At /configureSecurity/: clicking Save or Apply results in a pretty massive error where an ActiveDirectorySecurityRealm failed to instantiate in org.kohsuke.stapler.Stapler.tryInvoke (Stapler.java:796)
 

At /configure: XHR call to /$stapler/bound/[long GUID]/render returns 404 Not Found
 

At /configure: all other XHR calls executed on load (/checkAdminAddress, checkDefaultSuffix, checkGitUrl, etc.) return 200 OK but have an empty response.
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[JIRA] [vmware-vrealize-orchestrator-plugin] (JENKINS-34178) There *may* be a problem with the vm@VC:VirtualMachine parameter name.

2016-05-12 Thread agi....@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Agila Govindaraju commented on  JENKINS-34178 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: There *may* be a problem with the vm@VC:VirtualMachine parameter name.   
 
 
 
 
 
 
 
 
 
 
With the information from the core team of vRO, I identified that the VC object has to be identified differently. Here is the format, 
@vcenterUrl@moref-id 
Example: admin@https://10.0.1.1:443/sdk@vm-245678 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [pipeline-stage-view-plugin] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage

2016-05-12 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Bayer commented on  JENKINS-33185 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Visualize parallel steps within a Pipeline Stage  
 
 
 
 
 
 
 
 
 
 
Dana Goyette - that's exactly what this is about. =) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [pipeline-stage-view-plugin] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage

2016-05-12 Thread danagoye...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dana Goyette commented on  JENKINS-33185 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Visualize parallel steps within a Pipeline Stage  
 
 
 
 
 
 
 
 
 
 
I hope you'll also include visualization for steps within a parallel block. 
I'd like to be able to replace Matrix Jobs with equivalent workflows / pipelines, and that requires one big parallel block with a bunch of rows of the same steps (with different parameters). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34776) Jobs are removed if the remote is unavailable

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34776 
 
 
 
  Jobs are removed if the remote is unavailable  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 
 
 
 
 
 
 
 There are some scenarios where is possible to lose the jobs associated to repositories, branches and pull requests  if  whether  Github.com or your GitHub Enterprise instance is unreacheable (or not unavailable). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34776) Jobs are removed if the remote is unavailable

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34776 
 
 
 
  Jobs are removed if the remote is unavailable  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 
 
 
 
 
 
 
 There are  few  some  scenarios where is possible to lose the jobs associated to repositories, branches and pull requests if Github.com or your GitHub Enterprise instance is unreacheable (or not unavailable). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34776) Jobs are removedt if the remote is unavailable

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34776 
 
 
 
  Jobs are removedt if the remote is unavailable  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 
 
 
 
 
 
 
 There are few scenarios where is possible to lose the jobs associated to repositories, branches and pull requests if Github.com or your GitHub Enterprise instance is unreacheable (or not unavailable). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34776) Jobs are removed if the remote is unavailable

2016-05-12 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto started work on  JENKINS-34776 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [github-branch-source-plugin] (JENKINS-34776) Jobs are removed if the remote is unavailable

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34776 
 
 
 
  Jobs are removed if the remote is unavailable  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

Summary:
 
 Jobs are  removedt  removed  if the remote is unavailable 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34776) Jobs are removedt if the remote is unavailable

2016-05-12 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34776 
 
 
 
  Jobs are removedt if the remote is unavailable  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Manuel Jesús Recena Soto 
 
 
 

Components:
 

 github-branch-source-plugin 
 
 
 

Created:
 

 2016/May/12 6:31 PM 
 
 
 

Priority:
 
  Blocker 
 
 
 

Reporter:
 
 Manuel Jesús Recena Soto 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this 

[JIRA] [log-parser-plugin] (JENKINS-32866) Log Parser Plugin does not parse Pipeline console outputs

2016-05-12 Thread jenk...@mockies.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Vogtländer commented on  JENKINS-32866 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Log Parser Plugin does not parse Pipeline console outputs  
 
 
 
 
 
 
 
 
 
 
IMHO this is the expected behavior. The log parser step only has access to the log to the point where it is called. If called in "finally" (as some sort of post build actions in the pipeline build) this works well: 

 

try {
  node {
   echo 'Error: oh no'
  }
} finally {
  node {
   step([$class: 'LogParserPublisher', parsingRulesPath: '/var/lib/jenkins/jenkins-rule-logparser', useProjectRule: false])
  }
}
 

 
In order to fail the build add "failBuildOnError: true" (and maybe you need another try/catch block around the log parser step to catch the error and set the build result to FAILURE explicitly (not tested)). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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)

2016-05-12 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-34573 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Running out of Heap Memory (2048m)  
 
 
 
 
 
 
 
 
 
 
Haven't had time to look further, unfortunately. Giving you these hints is quick enough to sneak in between actual work  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34775) Broken jobs after upgrade to 1.651.2 security update

2016-05-12 Thread leandro.lucare...@sociomantic.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Leandro Lucarella commented on  JENKINS-34775 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Broken jobs after upgrade to 1.651.2 security update  
 
 
 
 
 
 
 
 
 
 
I could find the old version in http://pkg.jenkins-ci.org/debian-stable/ and reverted and all works fine with 1.651.1. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


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

2016-05-12 Thread raymond.acc...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Raymond Accary commented on  JENKINS-34573 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Running out of Heap Memory (2048m)  
 
 
 
 
 
 
 
 
 
 
Hi Daniel, I can try that.  
However, did the heap dump show anything as far as to what's causing this memory 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] [core] (JENKINS-34775) Broken jobs after upgrade to 1.651.2 security update

2016-05-12 Thread leandro.lucare...@sociomantic.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Leandro Lucarella created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34775 
 
 
 
  Broken jobs after upgrade to 1.651.2 security update  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 2016/May/12 6:01 PM 
 
 
 

Environment:
 

 Ubuntu 14.04 
 
 
 

Priority:
 
  Blocker 
 
 
 

Reporter:
 
 Leandro Lucarella 
 
 
 
 
 
 
 
 
 
 
After upgrading to 1.651.2 security update, jobs are getting this error: 

 
FATAL: org.acegisecurity.providers.UsernamePasswordAuthenticationToken cannot be cast to org.jenkinsci.plugins.GithubAuthenticationToken
java.lang.ClassCastException: org.acegisecurity.providers.UsernamePasswordAuthenticationToken cannot be cast to org.jenkinsci.plugins.GithubAuthenticationToken
	at org.jenkinsci.plugins.GithubSecurityRealm.loadUserByUsername(GithubSecurityRealm.java:644)
	at hudson.model.User$UserIDCanonicalIdResolver.resolveCanonicalId(User.java:1049)
	at hudson.model.User.get(User.java:395)
	at hudson.model.User.get(User.java:364)
	at hudson.plugins.git.GitChangeSet.findOrCreateUser(GitChangeSet.java:374)
	at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:435)
	at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:350)
	at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:346)
	at 

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

2016-05-12 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-34573 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Running out of Heap Memory (2048m)  
 
 
 
 
 
 
 
 
 
 
I think old Data is retained in memory as long as the associated records (e.g. build records) are in memory. If they're discarded from memory, old data should follow. 
Install and/or enable the Metrics Plugin to see whether that helps. It adds metadata to every build about its time in the queue: https://github.com/jenkinsci/metrics-plugin/blob/master/src/main/java/jenkins/metrics/impl/TimeInQueueAction.java 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34728) Pull Request pipeline fails to checkout successive commits

2016-05-12 Thread p...@paultyng.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul Tyng commented on  JENKINS-34728 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Pull Request pipeline fails to checkout successive commits  
 
 
 
 
 
 
 
 
 
 
I am getting this continuously on PR builds. I have the latest plugin versions. Not sure if there is something I could do to address it on my end. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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)

2016-05-12 Thread raymond.acc...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Raymond Accary commented on  JENKINS-34573 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Running out of Heap Memory (2048m)  
 
 
 
 
 
 
 
 
 
 
Some more observations I had: -This often coincides with data starting to show up in the manage old data -Running GC clears the old data somehow -I usually see in the old data messages about "jenkins.metrics.impl" and "EnQueueAction or InQueueAction" -Issues in log rotation showing up in the warnings log 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34610) Windows AMI in endless loop

2016-05-12 Thread bstew...@novetta.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brendan Stewart commented on  JENKINS-34610 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Windows AMI in endless loop  
 
 
 
 
 
 
 
 
 
 
One last thing to note, when i got it working with a domain user, i did that by specifying a user in the format: 
svcu...@bla.aws 
instead of BLAAWS\svcUser. There was some issue with the backslashes, i tired double backslash as well. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [_unsorted] (JENKINS-34774) ClosedChannelException in log (excessive)

2016-05-12 Thread r...@vipasolutions.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russ Tennant created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34774 
 
 
 
  ClosedChannelException in log (excessive)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Oleg Nenashev 
 
 
 

Components:
 

 _unsorted 
 
 
 

Created:
 

 2016/May/12 5:24 PM 
 
 
 

Environment:
 

 Jenkins 2.3  java version "1.8.0_40"  Java(TM) SE Runtime Environment (build 1.8.0_40-b26)  Java HotSpot(TM) 64-Bit Server VM (build 25.40-b25, mixed mode)  CentOS release 6.6 (Final)  
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Russ Tennant 
 
 
 
 
 
 
 
 
 
 
I just update to version 2 (2.3) and I am getting this logged every second. Any idea on how I can find out what is triggering this?  

 

May 12, 2016 5:22:53 PM org.apache.http.impl.nio.client.LoggingAsyncRequestExecutor exception
SEVERE: http-outgoing-1 [CLOSED] HTTP protocol exception: null
java.nio.channels.ClosedChannelException
at sun.nio.ch.SocketChannelImpl.ensureReadOpen(SocketChannelImpl.java:257)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:300)
at org.apache.http.nio.reactor.ssl.SSLIOSession.receiveEncryptedData(SSLIOSession.java:346)
at org.apache.http.nio.reactor.ssl.SSLIOSession.isAppInputReady(SSLIOSession.java:377)
at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:118)
at 

[JIRA] [ant-plugin] (JENKINS-33712) Empty parameterized build properties not quoted when passed to ant

2016-05-12 Thread bitbucket...@yahoo.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Keith Currier commented on  JENKINS-33712 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Empty parameterized build properties not quoted when passed to ant  
 
 
 
 
 
 
 
 
 
 
Looks good. I tried Ant Plugin 1.3 with Jenkins 2.1, 2.2, and 2.3. In all cases, the behavior was as expected. 
Thanks for the help! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [bitbucket-pullrequest-builder-plugin] (JENKINS-34773) Bitbucket Pull Request plugin doesn't see Jenkin's credentials

2016-05-12 Thread hou...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Houman Khorasani updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34773 
 
 
 
  Bitbucket Pull Request plugin doesn't see Jenkin's credentials  
 
 
 
 
 
 
 
 
 

Change By:
 
 Houman Khorasani 
 
 
 
 
 
 
 
 
 
 We don The plugin isn 't  know how to utilise this plugin  functional ,  if the SSH credential isn't recognised .  (see screenshot) Under normal build this can be easily  be  set and utilised  but not under pull requests .This seems to be a bug (see screenshot)Kindly advice, 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [bitbucket-pullrequest-builder-plugin] (JENKINS-34773) Bitbucket Pull Request plugin doesn't see Jenkin's credentials

2016-05-12 Thread hou...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Houman Khorasani created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34773 
 
 
 
  Bitbucket Pull Request plugin doesn't see Jenkin's credentials  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 Screen Shot 2016-05-12 at 18.13.17.png 
 
 
 

Components:
 

 bitbucket-pullrequest-builder-plugin 
 
 
 

Created:
 

 2016/May/12 5:18 PM 
 
 
 

Labels:
 

 bitbucket plugin 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Houman Khorasani 
 
 
 
 
 
 
 
 
 
 
We don't know how to utilise this plugin, if the SSH credential isn't recognised. Under normal build this can be easily set and utilised. 
This seems to be a bug (see screenshot) 
Kindly advice, 
 
 
 
 
 
 
 
 
 
 
 

[JIRA] [teamconcert-plugin] (JENKINS-34772) Problem in Jenkins RTC Plugin

2016-05-12 Thread jhcruvi...@yahoo.com.br (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 José Humberto Cruvinel created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34772 
 
 
 
  Problem in Jenkins RTC Plugin  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 teamconcert-plugin 
 
 
 

Created:
 

 2016/May/12 5:06 PM 
 
 
 

Environment:
 

 Jenkins version: 2.1  Team Concert Plugin: 1.2.0.0  RTC version: 5.0.2 iFix 14 
 
 
 

Labels:
 

 plugin jenkins 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 José Humberto Cruvinel 
 
 
 
 
 
 
 
 
 
 
Logs: 
RTC : checkout... FATAL: RTC : checkout failure: null com.ibm.team.repository.common.TeamRepositoryException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at com.ibm.team.repository.transport.client.RemoteTeamService.getAppropriateException(RemoteTeamService.java:704) at 

[JIRA] [p4-plugin] (JENKINS-32814) Add "Only poll using master" option

2016-05-12 Thread mohamed_bad...@mentor.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 mohamed badran commented on  JENKINS-32814 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add "Only poll using master" option  
 
 
 
 
 
 
 
 
 
 
If i override $NODE to the correct slave and it was offline, will it bring that slave online then do the polling? Btw, the old perforce plugin will automatically use the master node if the slave node is offline. If it is possible to get the node online then do the polling that would be great. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [teamconcert-plugin] (JENKINS-34771) Problem in Jenkins RTC Plugin

2016-05-12 Thread jhcruvi...@yahoo.com.br (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 José Humberto Cruvinel created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34771 
 
 
 
  Problem in Jenkins RTC Plugin  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 teamconcert-plugin 
 
 
 

Created:
 

 2016/May/12 5:04 PM 
 
 
 

Environment:
 

 Jenkins version: 2.1  Team Concert Plugin: 1.2.0.0  RTC version: 5.0.2 iFix 14 
 
 
 

Labels:
 

 plugin jenkins 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 José Humberto Cruvinel 
 
 
 
 
 
 
 
 
 
 
I'm facing the following problem in Jenkins RTC Plugin, using the option "Build Stream" for Build Configuration. 
Logs: 
RTC : checkout... FATAL: RTC : checkout failure: null com.ibm.team.repository.common.TeamRepositoryException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at 

[JIRA] [git-plugin] (JENKINS-34698) Allow picking a Browser for Git

2016-05-12 Thread nolang...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Norbert Lange commented on  JENKINS-34698 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Allow picking a Browser for Git  
 
 
 
 
 
 
 
 
 
 
Dunno about the implementation cost, but this sound like a rather in-transparent scheme, and not really reflecting the usage. Typically you want to configure a server (and update/change) independent of the jobs using it 
Wouldn`t it be easiest to add a section in the Jenkins preferences, mapping clone url prefixes to properties than solving the issue on multiple endpoints? Eg. a configuration would look like: 'github.com' = [browser: [$class: 'GitHub', repoUrl: 'http://github.com'] 'localhost:10022' = [browser: [$class: 'GogsGit', repoUrl: 'http://localhost:10080', credentialsId = 'blah' ] '10.99.10.4' = [browser: [$class: 'Gitlab', repoUrl: 'http://10.99.10.4:8080/gitlab, version: '8.7'', credentialsId = 'blah2' ] 
That would make migrations and upgrades of local servers very easy, while the predefined stuff like Github would be visible (and edible, like adding credentials?) to the user and not some magic in the plugin. Maybe you could even use a second table, to map names to servers or repositories, that way jobs are completely ignorant of the source repository - quite similar to how users only deal with "origin" in most local git repositories 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-25995) Cannot find function querySelectorAll while running HtmlUnit tests

2016-05-12 Thread kwhetst...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone commented on  JENKINS-25995 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cannot find function querySelectorAll while running HtmlUnit tests  
 
 
 
 
 
 
 
 
 
 
There have been a lot of changes around the test harness. Check out the jenkins-test-harness which has been updated and split from Jenkins core, and the plugin-pom which gives you granular control over your Jenkins dependencies. If you change the dependency of your plugin(s) to the plugin-pom, you can vary what version your tests will run from the command line, as well as in your pom. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [pipeline-stage-view-plugin] (JENKINS-34754) Pipeline stage view 1.4 not available from Jenkins Maven repo

2016-05-12 Thread jimmidy...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jimmi Dyson commented on  JENKINS-34754 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Pipeline stage view 1.4 not available from Jenkins Maven repo  
 
 
 
 
 
 
 
 
 
 
Thanks Sam Van Oort! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [pipeline-stage-view-plugin] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage

2016-05-12 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 James Dumay edited a comment on  JENKINS-33185 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Visualize parallel steps within a Pipeline Stage  
 
 
 
 
 
 
 
 
 
 We will be releasing a new pipeline visualisation  that handles parallel  this month into open source. Its not related to the stage view plugin but we could look at improving it to fit here too. Ill update this ticket when we can show more. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [p4-plugin] (JENKINS-34770) Report failure to Jenkins when a p4 submit fails so that the build can be marked Failed

2016-05-12 Thread reg.sm...@talk21.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Reg Smith created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34770 
 
 
 
  Report failure to Jenkins when a p4 submit fails so that the build can be marked Failed  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Paul Allen 
 
 
 

Components:
 

 p4-plugin 
 
 
 

Created:
 

 2016/May/12 3:57 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Reg Smith 
 
 
 
 
 
 
 
 
 
 
Add a setting so that the P4 plugin "Perforce: Publish Assets" and "Perforce: Label Build" can mark the build as failed if those operations fail for any reason. 
As an example, a build was successful but the the publish step failed because the user account could not write to the depot. However, as the build was marked "Success" no one noticed. This resulted in a deployed build which was not linked to a build in the Perforce helix depot. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

[JIRA] [pipeline-stage-view-plugin] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage

2016-05-12 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 James Dumay commented on  JENKINS-33185 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Visualize parallel steps within a Pipeline Stage  
 
 
 
 
 
 
 
 
 
 
We will be releasing a new pipeline visualisation this month into open source. Its not related to the stage view plugin but we could look at improving it to fit here too. Ill update this ticket when we can show more. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ghprb-plugin] (JENKINS-34762) PR status cannot be updated due to filtered parameters

2016-05-12 Thread tubaguy50...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Walke commented on  JENKINS-34762 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: PR status cannot be updated due to filtered parameters  
 
 
 
 
 
 
 
 
 
 
Just ran into this. Thanks for finding the cause. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [security] (JENKINS-31612) Stack trace shown with suppress-stack-trace plugin installed

2016-05-12 Thread jenkins...@blinkinglights.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cook commented on  JENKINS-31612 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Stack trace shown with suppress-stack-trace plugin installed  
 
 
 
 
 
 
 
 
 
 
Hi Daniel, yes we do have the reverse proxy auth plugin installed in order to implement corporate single-signon. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [git-plugin] (JENKINS-34698) Allow picking a Browser for Git

2016-05-12 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick assigned an issue to Mark Waite 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
GitSCM.guessBrowser already supports GitHub. It could be expanded to cover other cases, but there would still be cases where the browser is unguessable, mainly for locally hosted browsers (as opposed to public services). 
AbstractGitSCMSource could have a GitRepositoryBrowser field which it would pass on to GitSCM in build. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-34698 
 
 
 
  Allow picking a Browser for Git  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Component/s:
 
 git-plugin 
 
 
 

Component/s:
 
 workflow-multibranch-plugin 
 
 
 

Labels:
 
 multibranch workflow 
 
 
 

Assignee:
 
 Jesse Glick Mark Waite 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[JIRA] [remoting] (JENKINS-34121) IBM Java doesn't support AES/CTR/PKCS5Padding, required for JNLP3

2016-05-12 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-34121 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: IBM Java doesn't support AES/CTR/PKCS5Padding, required for JNLP3  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Stephen Connolly Path: src/main/java/hudson/remoting/Engine.java src/main/java/org/jenkinsci/remoting/engine/JnlpProtocol.java http://jenkins-ci.org/commit/remoting/43793e5b46f223c57f0a7b137cd983903fd63446 Log: [Related to JENKINS-34121] Allow disabling the protocols individually (#83) 
 

Also ensure that a fatal unexpected error in one protocol does not prevent a fall-back
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32396) Option to suppress automatic SCM trigger

2016-05-12 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32396 
 
 
 
  Option to suppress automatic SCM trigger  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Component/s:
 
 branch-api-plugin 
 
 
 

Labels:
 
 2.0 multibranch 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [vmware-vrealize-codestream-plugin] (JENKINS-34769) Need commit access to Code stream plugin

2016-05-12 Thread agi....@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Agila Govindaraju created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34769 
 
 
 
  Need commit access to Code stream plugin  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Rishi Saraf 
 
 
 

Components:
 

 vmware-vrealize-codestream-plugin 
 
 
 

Created:
 

 2016/May/12 3:41 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Agila Govindaraju 
 
 
 
 
 
 
 
 
 
 
Need commit access to the vRealize Codestream plugin ( https://github.com/jenkinsci/vmware-vrealize-codestream-plugin/) as the author has left VMware and I need to take care of future updates to the plugin. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 
 

[JIRA] [sonar-gerrit-plugin] (JENKINS-32851) Gerrit Connection Breaks on Jenkins 1.609.2 LTS

2016-05-12 Thread sebast...@bronek.eu (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sebastian Broniszewski commented on  JENKINS-32851 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Gerrit Connection Breaks on Jenkins 1.609.2 LTS  
 
 
 
 
 
 
 
 
 
 
We have the same problem. I add some extra logging to this plugin. We discover that communication to gerrit goes to the proxy. After remove proxy from tomcat catalinia container and from Jenkins plugin manager page everything works OK. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34720) Add LastCompletedBuildSelector support in DSL for copy artifact plugin

2016-05-12 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-34720 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add LastCompletedBuildSelector support in DSL for copy artifact plugin  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Daniel Spilker Path: docs/Home.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/CopyArtifactContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/CopyArtifactSelectorContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/StepContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/step/StepContextSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/17d2a6767eb1a37873f9e6cc76377ccda1631631 Log: Merge pull request #848 from daspilker/

JENKINS-34720
 


JENKINS-34720
 made CopyArtifactSelectorContext extensible 
Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/ec97987325d3...17d2a6767eb1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34720) Add LastCompletedBuildSelector support in DSL for copy artifact plugin

2016-05-12 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-34720 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add LastCompletedBuildSelector support in DSL for copy artifact plugin  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Daniel Spilker Path: docs/Home.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/CopyArtifactContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/CopyArtifactSelectorContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/StepContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/step/StepContextSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/cc04ef278d258470d94820b44caeab89b1065589 Log: made CopyArtifactSelectorContext extensible 
[FIXES JENKINS-34720] 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34720) Add LastCompletedBuildSelector support in DSL for copy artifact plugin

2016-05-12 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34720 
 
 
 
  Add LastCompletedBuildSelector support in DSL for copy artifact plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 SCM/JIRA link daemon 
 
 
 

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] [p4-plugin] (JENKINS-32523) P4 plugin keeps triggering builds on the same Perforce changelist, even if no new changelist was submitted to Perforce.

2016-05-12 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-32523 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: P4 plugin keeps triggering builds on the same Perforce changelist, even if no new changelist was submitted to Perforce.  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/changes/P4Revision.java src/main/java/org/jenkinsci/plugins/p4/client/ClientHelper.java src/main/java/org/jenkinsci/plugins/p4/tasks/PollTask.java http://jenkins-ci.org/commit/p4-plugin/cad43ac74895c7569ada4c3306731c044d75ce7b Log: Track syncs with a 'Change' field in the Workspace Description. 
Polling used ‘p4 cstat’ to determine the last sync’ed change in a workspace. However, if the have list is empty (such as in the Force Clean Populate mode) it would appear as if no changes have been synced. 
JENKINS-32518 JENKINS-32523 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [p4-plugin] (JENKINS-32518) Populate option "Forced clean and sync" causes continual rebuilds

2016-05-12 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-32518 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Populate option "Forced clean and sync" causes continual rebuilds  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/changes/P4Revision.java src/main/java/org/jenkinsci/plugins/p4/client/ClientHelper.java src/main/java/org/jenkinsci/plugins/p4/tasks/PollTask.java http://jenkins-ci.org/commit/p4-plugin/cad43ac74895c7569ada4c3306731c044d75ce7b Log: Track syncs with a 'Change' field in the Workspace Description. 
Polling used ‘p4 cstat’ to determine the last sync’ed change in a workspace. However, if the have list is empty (such as in the Force Clean Populate mode) it would appear as if no changes have been synced. 
JENKINS-32518 JENKINS-32523 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34767) RSS ID duplication for items with same name in different folders

2016-05-12 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34767 
 
 
 
  RSS ID duplication for items with same name in different folders  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 2016/May/12 2:36 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Oleg Nenashev 
 
 
 
 
 
 
 
 
 
 
Placeholder bug for https://github.com/jenkinsci/jenkins/pull/1965 
(Dec 2015) If you have two or more builds with the same name in different folders they end up with the same RSS id, which breaks feed readers. 
For example folderA/a and folderB/a would both have the following in the RSS 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
   

[JIRA] [bitbucket-branch-source-plugin] (JENKINS-34262) Support for OAuth credentials

2016-05-12 Thread jake.bis...@netdudes.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jake bishop commented on  JENKINS-34262 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Support for OAuth credentials  
 
 
 
 
 
 
 
 
 
 
Would it be possible to increase the prority of this issue? Our company will not allow it's use unless we can use secure authentication methods, and this plugin looks great and just what we need. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34768) Smarter worker selection needed

2016-05-12 Thread jo.shie...@xamarin.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jo Shields created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34768 
 
 
 
  Smarter worker selection needed  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 2016/May/12 2:42 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Jo Shields 
 
 
 
 
 
 
 
 
 
 
I have six machines, 2 executors each, capable of running 32-bit ARM jobs (i.e. have labels identifying as such) 
I have five machines, 3 executors each, capable of running either 32-bit or 64-bit ARM jobs (i.e. have labels identifying as such 
Which means a total of 27 executor slots for label debian-8-armel and 15 for debian-8-arm64 
Jenkins needs to consider the number of labels serviced by a slot, and prioritise more scarce resources - right now I have 4 queued jobs which want debian-8-arm64 machines, but they're 100% full running debian-8-armel jobs. Meanwhile I have empty debian-8-armel executors on the 32-bit machines. That's dumb and it should be less dumb. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 

[JIRA] [p4-plugin] (JENKINS-32814) Add "Only poll using master" option

2016-05-12 Thread pal...@perforce.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul Allen commented on  JENKINS-32814 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add "Only poll using master" option  
 
 
 
 
 
 
 
 
 
 
I could override the environment variable for $NODE during the polling, this would use the correct Perforce Client Workspace, but may still execute on the slave.  
Not sure how to actually force Jenkins to poll on the master, seems to be out of the scope of the 'p4' plugin, as the decision where to poll has already been made. I'll read up on 

JENKINS-9067
 and see how they fixed 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] [p4-plugin] (JENKINS-34051) Polling of Jenkinsfile always finds changes

2016-05-12 Thread pal...@perforce.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul Allen resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Slated for next release 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-34051 
 
 
 
  Polling of Jenkinsfile always finds changes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Paul Allen 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Assignee:
 
 Paul Allen 
 
 
 

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] [p4-plugin] (JENKINS-32518) Populate option "Forced clean and sync" causes continual rebuilds

2016-05-12 Thread pal...@perforce.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul Allen resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Slated for next release 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-32518 
 
 
 
  Populate option "Forced clean and sync" causes continual rebuilds  
 
 
 
 
 
 
 
 
 

Change By:
 
 Paul Allen 
 
 
 

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-25164) Provide a short $JOB_NAME inside a folder

2016-05-12 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-25164 
 
 
 
  Provide a short $JOB_NAME inside a folder  
 
 
 
 
 
 
 
 
 

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] [p4-plugin] (JENKINS-32523) P4 plugin keeps triggering builds on the same Perforce changelist, even if no new changelist was submitted to Perforce.

2016-05-12 Thread pal...@perforce.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul Allen resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Slated for next release 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-32523 
 
 
 
  P4 plugin keeps triggering builds on the same Perforce changelist, even if no new changelist was submitted to Perforce.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Paul Allen 
 
 
 

Status:
 
 In Progress Resolved 
 
 
 

Assignee:
 
 Paul Allen 
 
 
 

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-34767) RSS ID duplication for items with same name in different folders

2016-05-12 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-34767 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: RSS ID duplication for items with same name in different folders  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Carlos Rendon Path: core/src/main/java/hudson/model/Run.java http://jenkins-ci.org/commit/jenkins/d8076e9654a4be6cd0792ea954363b209c44313b Log: Fix RSS id for builds in folders (#1965) 
JENKINS-34767 - Prevent RSS ID collisions for items with same name in different folders 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [bitbucket-branch-source-plugin] (JENKINS-34262) Support for OAuth credentials

2016-05-12 Thread jake.bis...@netdudes.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jake bishop updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34262 
 
 
 
  Support for OAuth credentials  
 
 
 
 
 
 
 
 
 

Change By:
 
 jake bishop 
 
 
 

Comment:
 
 Is it true that this does not work at the moment? I have been trying to use OAuth credentials an i just get:{code}StartedConsulting Bitbucket Team/ProjectConnecting to https://bitbucket.org using /** (x)FATAL: Failed to recompute children of my-jobcom.cloudbees.jenkins.plugins.bitbucket.api.BitbucketRequestException: HTTP request error. Status: 401: UNAUTHORIZED. at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getRequest(BitbucketCloudApiClient.java:416) at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getTeam(BitbucketCloudApiClient.java:328) at com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMNavigator.visitSources(BitbucketSCMNavigator.java:164) at jenkins.branch.OrganizationFolder.computeChildren(OrganizationFolder.java:125) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:154) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:122) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Finished: FAILURE{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 

[JIRA] [core] (JENKINS-25164) Provide a short $JOB_NAME inside a folder

2016-05-12 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-25164 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Provide a short $JOB_NAME inside a folder  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Felix Belzunce Arcos Path: core/src/main/java/hudson/model/Job.java core/src/main/resources/jenkins/model/CoreEnvironmentContributor/buildEnv.groovy core/src/main/resources/jenkins/model/CoreEnvironmentContributor/buildEnv.properties http://jenkins-ci.org/commit/jenkins/4bab3630efcc2fa331db2989e321d9af1b8cdc1c Log: [FIXED JENKINS-25164] Add JOB_BASE_NAME env var (#2321) 
 



JENKINS-25164
 Add SHORT_JOB_NAME env var
 
 
 

Delete strip off
 
 
 



JENKINS-25164
 Change SHORT_JOB_NAME for LEAF_JOB_NAME
 
 
 



JENKINS-25164
 Change LEAF_JOB_NAME for JOB_BASE_NAME
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[JIRA] [pipeline-stage-view-plugin] (JENKINS-34696) Fix the representation of Parallel Stage in pipeline build (as it is delivery pipeline view)

2016-05-12 Thread svano...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sam Van Oort commented on  JENKINS-34696 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Fix the representation of Parallel Stage in pipeline build (as it is delivery pipeline view)  
 
 
 
 
 
 
 
 
 
 
alexandre_navarro I can understand the confusion, but parallel blocks may not contain stage steps within them: due to how stages are implemented within the pipeline, this is not a valid case. However, the labelled step enhancement will allow for naming chunks of code within blocks, and JENKINS-33185 can (and will) scan for the labels used to define each parallel branch.  
I am going to close this one out, since it's not possible with stages and the intended goal is already covered by the other enhancement. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [pipeline-stage-view-plugin] (JENKINS-33109) Log window appear at top of the page

2016-05-12 Thread svano...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sam Van Oort resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Verified and merged: the log window now appears centered at the top of the visible area.  
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-33109 
 
 
 
  Log window appear at top of the page  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sam Van Oort 
 
 
 

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] [pipeline-stage-view-plugin] (JENKINS-33714) Stage view displays large artifact sizes incorrectly

2016-05-12 Thread svano...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sam Van Oort resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Verified and fixed 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-33714 
 
 
 
  Stage view displays large artifact sizes incorrectly  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sam Van Oort 
 
 
 

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] [pipeline-stage-view-plugin] (JENKINS-34696) Fix the representation of Parallel Stage in pipeline build (as it is delivery pipeline view)

2016-05-12 Thread svano...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sam Van Oort resolved as Duplicate 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34696 
 
 
 
  Fix the representation of Parallel Stage in pipeline build (as it is delivery pipeline view)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sam Van Oort 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Duplicate 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [bitbucket-branch-source-plugin] (JENKINS-34262) Support for OAuth credentials

2016-05-12 Thread amu...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonio Muñiz commented on  JENKINS-34262 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Support for OAuth credentials  
 
 
 
 
 
 
 
 
 
 
Yes, this issue would not be open other wise. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [bitbucket-branch-source-plugin] (JENKINS-34262) Support for OAuth credentials

2016-05-12 Thread jake.bis...@netdudes.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jake bishop commented on  JENKINS-34262 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Support for OAuth credentials  
 
 
 
 
 
 
 
 
 
 
Is it true that this does not work at the moment? I have been trying to use OAuth credentials an i just get: 

 

Started
Consulting Bitbucket Team/Project
Connecting to https://bitbucket.org using /** (x)
FATAL: Failed to recompute children of my-job
com.cloudbees.jenkins.plugins.bitbucket.api.BitbucketRequestException: HTTP request error. Status: 401: UNAUTHORIZED.

	at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getRequest(BitbucketCloudApiClient.java:416)
	at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getTeam(BitbucketCloudApiClient.java:328)
	at com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMNavigator.visitSources(BitbucketSCMNavigator.java:164)
	at jenkins.branch.OrganizationFolder.computeChildren(OrganizationFolder.java:125)
	at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:154)
	at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:122)
	at hudson.model.ResourceController.execute(ResourceController.java:98)
	at hudson.model.Executor.run(Executor.java:410)
Finished: FAILURE
 

 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34740) Cannot create new items after upgrade to 2.2 when underscore is present in the hostname

2016-05-12 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-34740 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cannot create new items after upgrade to 2.2 when underscore is present in the hostname  
 
 
 
 
 
 
 
 
 
 
Cannot reproduce. Would help if you could localize the plugin or configuration option that causes this issue. 
Jenkins 2.3, Chrome 50, works. 
FWIW my browser doesn't send these request headers. 
Could this be related to the URL configured for Jenkins in the global configuration? I tried setting a different one than what I use to access Jenkins, but still works for me. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [pipeline-stage-view-plugin] (JENKINS-33351) Missing artifact names in popover

2016-05-12 Thread svano...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sam Van Oort closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Fix released in v1.4 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-33351 
 
 
 
  Missing artifact names in popover  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sam Van Oort 
 
 
 

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.


  1   2   >