[JIRA] [workflow-plugin] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.

2016-06-02 Thread mne...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Neale edited a comment on  JENKINS-34564 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Give the ability to choose how the multibranch subprojects will be named.  
 
 
 
 
 
 
 
 
 
 [~thxmasj] It can be an absolute path - and will be locked. If it  isn't unique  already locked when  it  is needed it  appends @N to the end. So there will be no branch names in the workspace (as far as I understand it) only what you specify, so you can be creative. From the snippet docs: "You can instead specify a path here and that workspace will be locked instead. (The path may be relative to the slave root, or absolute.)If concurrent builds ask for the same workspace, a directory with a suffix such as @2 may be locked instead. Currently there is no option to wait to lock the exact directory requested; if you need to enforce that behavior, you can either fail (error) when pwd indicates that you got a different directory, or you may enforce serial execution of this part of the build by some other means such as stage name: '…', concurrency: 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] [workflow-plugin] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.

2016-06-02 Thread mne...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Neale commented on  JENKINS-34564 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Give the ability to choose how the multibranch subprojects will be named.  
 
 
 
 
 
 
 
 
 
 
Thomas Johansen  
It can be an absolute path - and will be locked. If it isn't unique it appends @N to the end. So there will be no branch names in the workspace (as far as I understand it) only what you specify, so you can be creative.  
From the snippet docs:  
"You can instead specify a path here and that workspace will be locked instead. (The path may be relative to the slave root, or absolute.) 
If concurrent builds ask for the same workspace, a directory with a suffix such as @2 may be locked instead. Currently there is no option to wait to lock the exact directory requested; if you need to enforce that behavior, you can either fail (error) when pwd indicates that you got a different directory, or you may enforce serial execution of this part of the build by some other means such as stage name: '…', concurrency: 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] [amazon-ecr-plugin] (JENKINS-35323) Migrate active-directory-plugin to 2.x parent pom

2016-06-02 Thread fbelz...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Félix Belzunce Arcos started work on  JENKINS-35323 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Félix Belzunce Arcos 
 
 
 

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] [amazon-ecr-plugin] (JENKINS-35323) Migrate amazon-ecr-plugin to 2.x parent pom

2016-06-02 Thread fbelz...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Félix Belzunce Arcos updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35323 
 
 
 
  Migrate amazon-ecr-plugin to 2.x parent pom  
 
 
 
 
 
 
 
 
 

Change By:
 
 Félix Belzunce Arcos 
 
 
 

Summary:
 
 Migrate  active  amazon - directory ecr -plugin to 2.x parent 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] [amazon-ecr-plugin] (JENKINS-35323) Migrate active-directory-plugin to 2.x parent pom

2016-06-02 Thread fbelz...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Félix Belzunce Arcos created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35323 
 
 
 
  Migrate active-directory-plugin to 2.x parent pom  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Félix Belzunce Arcos 
 
 
 

Components:
 

 amazon-ecr-plugin 
 
 
 

Created:
 

 2016/Jun/03 6:36 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Félix Belzunce Arcos 
 
 
 
 
 
 
 
 
 
 
Migrate to 2.x parent pom. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[JIRA] [p4-plugin] (JENKINS-32761) support multiple unshelve changelists in one build step

2016-06-02 Thread dant...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 dan tran commented on  JENKINS-32761 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: support multiple unshelve changelists in one build step  
 
 
 
 
 
 
 
 
 
 
perforce shelves are working very well for us. We have sandbox builds that have a real need to accept multiple unshelves in one entry. Did not know about the review feature. Could you place some inline help for each field? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [multi-branch-project-plugin] (JENKINS-32253) Want an option to encode slashes in branch names differently

2016-06-02 Thread 4uva...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Smith edited a comment on  JENKINS-32253 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Want an option to encode slashes in branch names differently  
 
 
 
 
 
 
 
 
 
 Affect Affects  me to.   Running jenkins on  *  windows7-x64 machine *  an using Git Worflow (generates branches like ' * release/v1.0.0 * ' and ' * feature/test * ') will encode slash in branch name into "%2F" which will then broke Msbuild build cause of those encoded slash will not be resolved correctly.Need an option to replace symbols in branch name to something safe instead of encoding them. Something like: replace "/" with "_" or similiar as option entry (or regexp match pattern). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [multi-branch-project-plugin] (JENKINS-32253) Want an option to encode slashes in branch names differently

2016-06-02 Thread 4uva...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Smith edited a comment on  JENKINS-32253 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Want an option to encode slashes in branch names differently  
 
 
 
 
 
 
 
 
 
 Affects me to.Running jenkins on *windows7-x64 machine* an using Git Worflow (generates branches like '*release/v1.0.0*' and '*feature/test*') will encode slash in branch name into " * %2F * " which will then  *  broke Msbuild  build * builds  cause of those encoded slash will not be resolved correctly.Need an option to replace symbols in branch name to something safe instead of encoding them. Something like:  *  replace "/" with "_" or similiar as option entry *  (or regexp match pattern). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [multi-branch-project-plugin] (JENKINS-32253) Want an option to encode slashes in branch names differently

2016-06-02 Thread 4uva...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Smith commented on  JENKINS-32253 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Want an option to encode slashes in branch names differently  
 
 
 
 
 
 
 
 
 
 
Affect me to. Running jenkins on windows7-x64 machine an using Git Worflow (generates branches like 'release/v1.0.0' and 'feature/test') will encode slash in branch name into "%2F" which will then broke Msbuild build cause of those encoded slash will not be resolved correctly. 
Need an option to replace symbols in branch name to something safe instead of encoding them. Something like: replace "/" with "_" or similiar as option entry (or regexp match pattern). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-27251) windows slaves disconnect during build

2016-06-02 Thread sm...@netgear.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sharan Math commented on  JENKINS-27251 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: windows slaves disconnect during build  
 
 
 
 
 
 
 
 
 
 
I'm also hit the with same, Can someone suggest a workaround for now: 
Slave went offline during the build ERROR: Connection was broken: java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@693ec9f0[name=automation-pc] at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:208) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:628) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: java.io.IOException: No route to host at sun.nio.ch.FileDispatcherImpl.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) at sun.nio.ch.IOUtil.read(IOUtil.java:197) at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:379) at org.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:136) at org.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:306) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:561) ... 6 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] [ssh2easy-plugin] (JENKINS-34102) Add support for enviroment variable

2016-06-02 Thread n...@qq.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jerry Cai resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Thanks Nikolas Falco a lot for implementation of this new feature , Now it is resolved on ssh2easy-1.4  
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-34102 
 
 
 
  Add support for enviroment variable  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jerry Cai 
 
 
 

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] [matrix-project-plugin] (JENKINS-33230) Jenkins creates lots of warning message for creating matrix project root directory

2016-06-02 Thread totoroliu1...@hotmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rick Liu commented on  JENKINS-33230 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins creates lots of warning message for creating matrix project root directory  
 
 
 
 
 
 
 
 
 
 
i never tried downgrade Jenkins-master before, but it should be straightforward either using OS's package management or just replace Jenkins WAR file. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [matrix-project-plugin] (JENKINS-33230) Jenkins creates lots of warning message for creating matrix project root directory

2016-06-02 Thread maruthi.inuko...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maruthi Inukonda commented on  JENKINS-33230 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins creates lots of warning message for creating matrix project root directory  
 
 
 
 
 
 
 
 
 
 
Thanks Rick. 
In general, does jenkins downgrade work. I would like to go back to previous release 1.619. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [timestamper-plugin] (JENKINS-35315) Timestamper panel is not displayed because of mixed content block

2016-06-02 Thread jenkin...@caspowa.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pavel Jozef edited a comment on  JENKINS-35315 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Timestamper panel is not displayed because of mixed content block  
 
 
 
 
 
 
 
 
 
 So the browser is trying to make the following request:{noformat}https://my.jenkins.host/extensionList/hudson.console.ConsoleAnnotatorFactory/hudson.plugins.timestamper.annotator.TimestampAnnotatorFactory2/script.js{noformat}Jenkins responds with a temporary redirect:{noformat}location:http://my.jenkins.host/static/1.8.2/plugin/timestamper/annotator.jsstatus:302{noformat}It looks like `doScriptJs` generates an absolute HTTP URL. - What does req.getContextPath() return? - Most likely this issue is caused by sendRedirect2. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [matrix-project-plugin] (JENKINS-33230) Jenkins creates lots of warning message for creating matrix project root directory

2016-06-02 Thread totoroliu1...@hotmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rick Liu commented on  JENKINS-33230 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins creates lots of warning message for creating matrix project root directory  
 
 
 
 
 
 
 
 
 
 
The fix is not merged yet. I did the github pull-request, but nobody approved yet. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [timestamper-plugin] (JENKINS-35315) Timestamper panel is not displayed because of mixed content block

2016-06-02 Thread jenkin...@caspowa.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pavel Jozef commented on  JENKINS-35315 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Timestamper panel is not displayed because of mixed content block  
 
 
 
 
 
 
 
 
 
 
So the browser is trying to make the following request: 

 
https://my.jenkins.host/extensionList/hudson.console.ConsoleAnnotatorFactory/hudson.plugins.timestamper.annotator.TimestampAnnotatorFactory2/script.js
 

 
Jenkins responds with a temporary redirect: 

 
location:http://my.jenkins.host/static/1.8.2/plugin/timestamper/annotator.js
status:302
 

 
It looks like `doScriptJs` generates an absolute HTTP URL. 
What does req.getContextPath() return? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [matrix-project-plugin] (JENKINS-33230) Jenkins creates lots of warning message for creating matrix project root directory

2016-06-02 Thread maruthi.seshid...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maruthi Seshidhar Inukonda commented on  JENKINS-33230 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins creates lots of warning message for creating matrix project root directory  
 
 
 
 
 
 
 
 
 
 
After I upgraded jenkins to 1.6.651 LTS, I started seeing this issue. I even tried 1.6.658, issue persists. My matrix job's child configuration is stuck for hours due to this (which normally takes about 2 mins). The log is spammed with this message ever one sec. 
Jun 03, 2016 8:27:58 AM hudson.matrix.MatrixProject getRootDirFor WARNING: Cannot create directory /var/lib/jenkins/jobs/lfi-capilano-presub-bld/configurations/axis-DISTRO/el/axis-REL/6/axis-UPDT/5/axis-label/aidel60 for the combination DISTRO=el,REL=6,UPDT=5,label=aidel60 Jun 03, 2016 8:27:59 AM hudson.matrix.MatrixProject getRootDirFor WARNING: Cannot create directory /var/lib/jenkins/jobs/lfi-capilano-presub-bld/configurations/axis-DISTRO/el/axis-REL/6/axis-UPDT/5/axis-label/aidel60 for the combination DISTRO=el,REL=6,UPDT=5,label=aidel60 
In which build is this fix available? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [hp-application-automation-tools-plugin] (JENKINS-35165) Jenkins plugin cannot work with ALM over SSL

2016-06-02 Thread soni...@163.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Leon Xue resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35165 
 
 
 
  Jenkins plugin cannot work with ALM over SSL  
 
 
 
 
 
 
 
 
 

Change By:
 
 Leon Xue 
 
 
 

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] [hp-application-automation-tools-plugin] (JENKINS-35165) Jenkins plugin cannot work with ALM over SSL

2016-06-02 Thread soni...@163.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Leon Xue commented on  JENKINS-35165 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins plugin cannot work with ALM over SSL  
 
 
 
 
 
 
 
 
 
 
Fixed in the plugin4.5 release 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [project-inheritance-plugin] (JENKINS-22885) Creation of Inheritance Project throws Exception

2016-06-02 Thread ca...@rtzassociates.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 carlo tuazon commented on  JENKINS-22885 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Creation of Inheritance Project throws Exception  
 
 
 
 
 
 
 
 
 
 
When creating new Inheritance Project still error occurs java.lang.RuntimeException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.651.2.jar!/lib/layout/layout.jelly:248:25:  org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.651.2.jar!/lib/layout/main-panel.jelly:36:21:  org.apache.commons.jelly.JellyTagException: jar:file:/var/lib/jenkins/plugins/project-inheritance/WEB-INF/lib/classes.jar!/form/form.jelly:58:22:  org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.651.2.jar!/lib/form/entry.jelly:73:23:  No such property: codeMirrorConfig for class: hudson.markup.EscapedMarkupFormatter at org.kohsuke.stapler.jelly.groovy.JellyBuilder.doInvokeMethod(JellyBuilder.java:280) at org.kohsuke.stapler.jelly.groovy.Namespace$ProxyImpl.invoke(Namespace.java:92) at com.sun.proxy.$Proxy45.layout(Unknown Source) at lib.LayoutTagLib$layout.call(Unknown Source) at configure-version-aware.run(configure-version-aware.groovy:34) at org.kohsuke.stapler.jelly.groovy.GroovierJellyScript.run(GroovierJellyScript.java:74) at org.kohsuke.stapler.jelly.groovy.GroovierJellyScript.run(GroovierJellyScript.java:62) at org.kohsuke.stapler.jelly.groovy.JellyBuilder._include(JellyBuilder.java:165) at org.kohsuke.stapler.jelly.groovy.JellyBuilder.include(JellyBuilder.java:140) at sun.reflect.GeneratedMethodAccessor192.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1079) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:903) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:723) at groovy.lang.GroovyObjectSupport.invokeMethod(GroovyObjectSupport.java:44) at org.kohsuke.stapler.jelly.groovy.GroovyClosureScript.invokeMethod(GroovyClosureScript.java:87) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.callCurrent(PogoMetaClassSite.java:72) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:145) at configure.run(configure.groovy:28) at org.kohsuke.stapler.jelly.groovy.GroovierJellyScript.run(GroovierJellyScript.java:74) at org.kohsuke.stapler.jelly.groovy.GroovierJellyScript.run(GroovierJellyScript.java:62) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at org.kohsuke.stapler.jelly.groovy.GroovyFacet$1.dispatch(GroovyFacet.java:80) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)

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

2016-06-02 Thread nick...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nicholas Bencriscutto commented on  JENKINS-34177 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Pipeline Multibranch Not Cleaning Workspaces  
 
 
 
 
 
 
 
 
 
 
We are also experiencing this. It seems to cause issues at the most inconvenient time. (Of course when would it ever be convenient). We have temporarily set up a very conservative cron style jenkins job to clean out the jobs in the wee hours of the morning, but that could potentially cause problems down the line. Would like to keep the cleanup in house on a per job basis.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [timestamper-plugin] (JENKINS-35315) Timestamper panel is not displayed because of mixed content block

2016-06-02 Thread stevengbr...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steven G Brown commented on  JENKINS-35315 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Timestamper panel is not displayed because of mixed content block  
 
 
 
 
 
 
 
 
 
 
Annotator.js is being served here: https://github.com/jenkinsci/timestamper-plugin/blob/timestamper-1.8.2/src/main/java/hudson/plugins/timestamper/annotator/TimestampAnnotatorFactory2.java#L131 
Any idea what the problem is or how it should be fixed? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [workflow-plugin] (JENKINS-35309) Missing command/property suggestion

2016-06-02 Thread mne...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Neale commented on  JENKINS-35309 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Missing command/property suggestion  
 
 
 
 
 
 
 
 
 
 
If there was some global feed published, even hand maintained at first (for common globals and steps) would that be useful?  
This hugely increases the easy in which people can share Jenkinsfiles around 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-34177) Pipeline Multibranch Not Cleaning Workspaces

2016-06-02 Thread shak...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jake Alheid commented on  JENKINS-34177 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Pipeline Multibranch Not Cleaning Workspaces  
 
 
 
 
 
 
 
 
 
 
We have a large, multi-gigabyte repository, and this bug is repeatedly causing us to either have to go in and manually clean out old branches, or giving test failures because hundreds of gigabytes of space are being taken up in a short time due to the multiple checkouts. 
Please fix! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [workflow-plugin] (JENKINS-35308) Improve display of non-AbortException stack traces such as MissingPropertyException

2016-06-02 Thread mne...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Neale commented on  JENKINS-35308 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Improve display of non-AbortException stack traces such as MissingPropertyException  
 
 
 
 
 
 
 
 
 
 
I think even if the line number wasn't easy just having a shorter message with the undefined/missing variable would be enough of a hint for most pipelines (line numbers awesome, but perhaps one thing at a time).  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [assembla-auth] (JENKINS-34948) UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken

2016-06-02 Thread pa...@assembla.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pavel Dotsulenko assigned an issue to Pavel Dotsulenko 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34948 
 
 
 
  UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken  
 
 
 
 
 
 
 
 
 

Change By:
 
 Pavel Dotsulenko 
 
 
 

Assignee:
 
 Jakub Czaplicki Pavel Dotsulenko 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [assembla-auth] (JENKINS-34948) UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken

2016-06-02 Thread pa...@assembla.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pavel Dotsulenko started work on  JENKINS-34948 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Pavel Dotsulenko 
 
 
 

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] [ghprb-plugin] (JENKINS-35170) GHPRB latest version incorrectly identifying the base branch for merge

2016-06-02 Thread dantl...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Antliff commented on  JENKINS-35170 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: GHPRB latest version incorrectly identifying the base branch for merge  
 
 
 
 
 
 
 
 
 
 
Seen here with Jenkins 2.7 and GHPRB 1.32.2 - wrong commit is used for the job. Reverted to 1.31.3 for now. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [git-plugin] (JENKINS-35230) The environment variables of git plugin not working in pipeline script.

2016-06-02 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35230 
 
 
 
  The environment variables of git plugin not working in pipeline script.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mark Waite 
 
 
 

Assignee:
 
 Mark Waite 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [docker-build-step-plugin] (JENKINS-35322) NPE when trying to pull Docker image as first build step

2016-06-02 Thread stephen.don...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stephen Donner updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35322 
 
 
 
  NPE when trying to pull Docker image as first build step  
 
 
 
 
 
 
 
 
 
 
Pertinent (hopefully) part of job config 
 
 
 
 
 
 
 
 
 

Change By:
 
 Stephen Donner 
 
 
 

Attachment:
 
 Screen Shot 2016-06-02 at 4.01.54 PM.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [docker-build-step-plugin] (JENKINS-35322) NPE when trying to pull Docker image as first build step

2016-06-02 Thread stephen.don...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stephen Donner updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35322 
 
 
 
  NPE when trying to pull Docker image as first build step  
 
 
 
 
 
 
 
 
 
 
Error output from Build Now 
 
 
 
 
 
 
 
 
 

Change By:
 
 Stephen Donner 
 
 
 

Attachment:
 
 Screen Shot 2016-06-02 at 3.48.59 PM.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [docker-build-step-plugin] (JENKINS-35322) NPE when trying to pull Docker image as first build step

2016-06-02 Thread stephen.don...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stephen Donner created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35322 
 
 
 
  NPE when trying to pull Docker image as first build step  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 vjuranek 
 
 
 

Components:
 

 docker-build-step-plugin 
 
 
 

Created:
 

 2016/Jun/02 10:55 PM 
 
 
 

Environment:
 

 Linux localhost.localdomain 4.5.4-300.fc24.x86_64 #1 SMP Wed May 11 17:57:16 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux   I should note this is a Fedora install running inside VMWare Fusion, on OS X 10.11.6 Beta (15G7b)   openjdk version "1.8.0_91"  OpenJDK Runtime Environment (build 1.8.0_91-b14)  OpenJDK 64-Bit Server VM (build 25.91-b14, mixed mode)   Jenkins: 1.651.2 (LTS)  Docker-build-step: 1.35  Docker Commons Plugin: 1.31 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Stephen Donner 
 
 
 
 
 
 
 
 
 
 
Steps to Reproduce: 
1. With the above installed, create a job with "Execute Docker command" which does: 
Pull Image 
Name: owasp/zap2docker-weekly Tag: latest Registry: [blank[ or Docker Docker Registry URL; https://hub.docker.r/owasp/zap2docker-weekly/ Registry Credentials: [none] 
2. In Jenkins, click "Build Now" 
Actual Results: 
I get the following stack trace/exception: 
 

[JIRA] [blueocean-plugin] (JENKINS-35312) Log line numbers stop rendering at screen height

2016-06-02 Thread mne...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Neale commented on  JENKINS-35312 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Log line numbers stop rendering at screen height  
 
 
 
 
 
 
 
 
 
 
Hi Antonio Muñiz - there is a LOT of work going on on the log side of things, (some ticket to be migrated over hopefully today after JIRA upgrade).  
So expect this to totally change (hopefully for the better!) very soon (there is a PR in progress by thorsten for one).  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [blueocean-plugin] (JENKINS-35312) Log line numbers stop rendering at screen height

2016-06-02 Thread mne...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Neale assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35312 
 
 
 
  Log line numbers stop rendering at screen height  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Neale 
 
 
 

Assignee:
 
 Michael Neale 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-35277) ssh executable not found

2016-06-02 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35277 
 
 
 
  ssh executable not found  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mark Waite 
 
 
 

Assignee:
 
 Mark Waite 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated

2016-06-02 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite commented on  JENKINS-20941 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Stored git credentials not used when submodule is updated  
 
 
 
 
 
 
 
 
 
 
Peter van Dijk the beta version of the plugin supports https (username/password) parent repositories referencing https (username/password) submodules and it supports ssh (private key) parent repositories referencing ssh (private key) submodules. I've recently checked that it works with a github ssh (private key) parent repository and github ssh (private key) submodules. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-33546) Regression with build parameters in XML API

2016-06-02 Thread locopelo...@hotmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Astro Ashtar closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33546 
 
 
 
  Regression with build parameters in XML API  
 
 
 
 
 
 
 
 
 

Change By:
 
 Astro Ashtar 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated

2016-06-02 Thread pvan...@salesforce.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Van Dyk commented on  JENKINS-20941 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Stored git credentials not used when submodule is updated  
 
 
 
 
 
 
 
 
 
 
We are having this issue using SSH for the primary project and the submodules. I have not tried the beta plugin as the description above indicates that the issue is related to http git links. Does this fix include a fix for refreshing the submodules for SSH connections? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-35087) Old data not upgrading from 1.653 to 1.651.2

2016-06-02 Thread t...@us.ibm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tammy Parker commented on  JENKINS-35087 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Old data not upgrading from 1.653 to 1.651.2  
 
 
 
 
 
 
 
 
 
 
It was not solved. The Manage Old Data shows up intermittently after my plugin updates. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-31095) 2.0: Jenkins terminology sweep

2016-06-02 Thread bitwise...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Liam Newman commented on  JENKINS-31095 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: 2.0: Jenkins terminology sweep  
 
 
 
 
 
 
 
 
 
 
Kohsuke Kawaguchi Would you object to us doing as Patrick suggested?  Tracking high level stories linked to this as an epic, with tasks and issues linked to the appropriate stories, will be easier to understand and summarize. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-35309) Missing command/property suggestion

2016-06-02 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick commented on  JENKINS-35309 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Missing command/property suggestion  
 
 
 
 
 
 
 
 
 
 
Would be useful. Tricky because it cannot be done purely as a plugin code change; need a backend job indexing StepDescriptor and GlobalVariable from all plugins in the update center, and then somehow publishing this metadata on the update center for eventual download. We do something similar for ToolInstaller but the infrastructure is tied to that use case and would need to be duplicated or generalized. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-35308) Improve display of non-AbortException stack traces such as MissingPropertyException

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35308 
 
 
 
  Improve display of non-AbortException stack traces such as MissingPropertyException  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Summary:
 
 Error reporting from pipeline script has to be much better Improve display of non-AbortException stack traces such as MissingPropertyException 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-35308) Error reporting from pipeline script has to be much better

2016-06-02 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick commented on  JENKINS-35308 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Error reporting from pipeline script has to be much better  
 
 
 
 
 
 
 
 
 
 
Not sure how straightforward this is. Catching MissingPropertyException and specially printing it (when it is the cause for build termination) is easy enough, at least assuming it has not been wrapped in another exception, which I think is not an issue in this case. (Cf. 

JENKINS-25894
.) Getting the property name is also easy. 
Finding the source and line number is another matter. We could look for synthetic stack trace elements and print only those, but we might inadvertently wind up hiding relevant parts. Needs some study to make sure that the simplification would actually work reliably. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-32761) support multiple unshelve changelists in one build step

2016-06-02 Thread pal...@perforce.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul Allen commented on  JENKINS-32761 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: support multiple unshelve changelists in one build step  
 
 
 
 
 
 
 
 
 
 
That could work if the changes were passed as some kind of list (space or comer separated). 
There are two places to unshelve, once during the SCM checkout stage (as a Review) or the other as a Build Step. The build step allows other things to happen first, but has the disadvantage that the unshelved changes are not reported in the build summary. 
A third option, is to hack MultiBranch support (https://jenkins.io/doc/pipeline/) for use with shelves. I'm looking to add support for multi branch in the near future. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-33629) `checkout scm` surprisingly fails when multibranch plugin is not installed

2016-06-02 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick commented on  JENKINS-33629 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: `checkout scm` surprisingly fails when multibranch plugin is not installed  
 
 
 
 
 
 
 
 
 
 

I think Jesse misunderstood this ticket to be
 
Not sure what that means. I just meant, do not uninstall workflow-multibranch. It is in the default set of Pipeline plugins. 
Will look at linked tickets to see if they are feasible. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-oauth-plugin] (JENKINS-34792) Bitbucket plugin broken after Jenkins upgrade to 2.3

2016-06-02 Thread kristof...@codedivision.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristoffer Peterhänsel commented on  JENKINS-34792 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Bitbucket plugin broken after Jenkins upgrade to 2.3  
 
 
 
 
 
 
 
 
 
 
It has to be set as a system property at start (JVM -D option). Not sure if there is another way to do 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] [bitbucket-oauth-plugin] (JENKINS-34792) Bitbucket plugin broken after Jenkins upgrade to 2.3

2016-06-02 Thread chris.a.giddi...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chris Giddings commented on  JENKINS-34792 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Bitbucket plugin broken after Jenkins upgrade to 2.3  
 
 
 
 
 
 
 
 
 
 
Kristoffer Peterhänsel 
Where do I make that config change? 
My builds and SSH file copy of those builds suceed, but when releasing the workflow afterward, it fails. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [maven-plugin] (JENKINS-35321) MavenModuleSetBuild swallows InterruptedIOException on doRun

2016-06-02 Thread ow...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Owen Wood started work on  JENKINS-35321 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Owen Wood 
 
 
 

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] [acceptance-test-harness] (JENKINS-35134) Large numbers of ATH tests failing against 2.6

2016-06-02 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Bayer commented on  JENKINS-35134 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Large numbers of ATH tests failing against 2.6  
 
 
 
 
 
 
 
 
 
 
Oh, me too. =) But given that http://seleniumhq.github.io/selenium/docs/api/java/org/openqa/selenium/firefox/FirefoxProfile.html#setAlwaysLoadNoFocusLib-boolean- only is relevant on Linux, it looks like fixing it elsewhere would either mean getting Selenium's no focus library to work elsewhere or rewriting the new job UX to not depend on blur. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [acceptance-test-harness] (JENKINS-35134) Large numbers of ATH tests failing against 2.6

2016-06-02 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ulli Hafner commented on  JENKINS-35134 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Large numbers of ATH tests failing against 2.6  
 
 
 
 
 
 
 
 
 
 
Well, I'm biased but we should fix it on OS X, too! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [maven-plugin] (JENKINS-35321) MavenModuleSetBuild swallows InterruptedIOException on doRun

2016-06-02 Thread ow...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Owen Wood assigned an issue to Owen Wood 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35321 
 
 
 
  MavenModuleSetBuild swallows InterruptedIOException on doRun  
 
 
 
 
 
 
 
 
 

Change By:
 
 Owen Wood 
 
 
 

Assignee:
 
 Owen Wood 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [maven-plugin] (JENKINS-35321) MavenModuleSetBuild swallows InterruptedIOException on doRun

2016-06-02 Thread ow...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Owen Wood created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35321 
 
 
 
  MavenModuleSetBuild swallows InterruptedIOException on doRun  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 maven-plugin 
 
 
 

Created:
 

 2016/Jun/02 8:25 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Owen Wood 
 
 
 
 
 
 
 
 
 
 
Definitely not a deal breaker. Just makes debugging hard 
https://github.com/jenkinsci/maven-plugin/blob/master/src/main/java/hudson/maven/MavenModuleSetBuild.java#L898 

 

catch (InterruptedIOException e) {
e.printStackTrace(listener.error("Aborted Maven execution for InterruptedIOException"));
return Executor.currentExecutor().abortResult();
}
 

 
Propose adding message to printStackTrace. Something like: 

 

catch (InterruptedIOException e) {
e.printStackTrace(listener.error("Aborted Maven execution for InterruptedIOException: " + e.getMessage()));
return Executor.currentExecutor().abortResult();
}
 

 
 
 
 
 

[JIRA] [core] (JENKINS-35320) External Jobs cannot be Configured or Deleted unless user is Admin

2016-06-02 Thread josh.sh...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Joshua Shinn created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35320 
 
 
 
  External Jobs cannot be Configured or Deleted unless user is Admin  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 2016/Jun/02 8:20 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Joshua Shinn 
 
 
 
 
 
 
 
 
 
 
External Jobs cannot be Configured or Deleted unless user is Admin at the root level. The links do not appear even if the user has ``Job/Create`` and ``Job/Configure`` permissions. It looks like the offending code is here: https://github.com/jenkinsci/external-monitor-job-plugin/blob/master/src/main/resources/hudson/model/ExternalJob/sidepanel.jelly#L37-L38 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 

[JIRA] [jacoco-plugin] (JENKINS-35319) Hide code coverage report links when user lacks "workspace" permission

2016-06-02 Thread josh.sh...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Joshua Shinn created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35319 
 
 
 
  Hide code coverage report links when user lacks "workspace" permission  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Ognjen Bubalo 
 
 
 

Components:
 

 jacoco-plugin 
 
 
 

Created:
 

 2016/Jun/02 8:05 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Joshua Shinn 
 
 
 
 
 
 
 
 
 
 
Code coverage reports should not be accessible when a user does not have "workspace" permission. Currently, the user may not have the permission but can still access the workspace via links in the code coverage report. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

[JIRA] [core] (JENKINS-35318) Make workspace cleanup configurable per slave

2016-06-02 Thread ajbarbe...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Barber created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35318 
 
 
 
  Make workspace cleanup configurable per slave  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 2016/Jun/02 7:52 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Andrew Barber 
 
 
 
 
 
 
 
 
 
 
It would be helpful if the cleanup thread could be configurable by slave. Each slave should have an option to enable/disable cleanup and another option to specify how many days old a workspace needs to be to be considered for cleanup. 
This will help solve issues where slaves may share a slave root or jobs are using custom workspaces and run on multiple slaves.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


[JIRA] [core] (JENKINS-35087) Old data not upgrading from 1.653 to 1.651.2

2016-06-02 Thread t...@us.ibm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tammy Parker edited a comment on  JENKINS-35087 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Old data not upgrading from 1.653 to 1.651.2  
 
 
 
 
 
 
 
 
 
 I have the same error starting today when I attempted to update all of my plugins.Also, after the update attempt via 'Download now and install after restart', the plugins are still listed as needing an update; I think the update did not occur as I forgot to check each individual plugin before pushing the 'Download now and install after restart' button... I seem to have resolved my issue by going back to the Update Plugins and properly selecting them and then doing the 'Download now and install after restart'.When I saw they were successfully downloaded, I did a http://jenkins_server_url:8080/safeRestartI no longer have the Manage Old Data issue showing up. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-plugin] (JENKINS-35317) Null pointer exception with credentials (GIT)

2016-06-02 Thread sean.riv...@colorado.edu (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Rivera created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35317 
 
 
 
  Null pointer exception with credentials (GIT)   
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 stephenconnolly 
 
 
 

Components:
 

 credentials-plugin, git-plugin, github-plugin 
 
 
 

Created:
 

 2016/Jun/02 7:45 PM 
 
 
 

Environment:
 

 Ubuntu 15.10  Jenkins war org.jenkins-ci.main:jenkins-war:2.7  Git plugin 2.4.4 
 
 
 

Labels:
 

 exception plugin git 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Sean Rivera 
 
 
 
 
 
 
 
 
 
 
 ERROR 
A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace 
javax.servlet.ServletException: java.lang.NullPointerException a

[JIRA] [github-organization-folder-plugin] (JENKINS-34246) Old repos aren't removed

2016-06-02 Thread docw...@gerf.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Höltje commented on  JENKINS-34246 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Old repos aren't removed  
 
 
 
 
 
 
 
 
 
 
Oh, and my orphan strategy was set to "Number to keep" at 0. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [github-organization-folder-plugin] (JENKINS-34246) Old repos aren't removed

2016-06-02 Thread docw...@gerf.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Höltje commented on  JENKINS-34246 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Old repos aren't removed  
 
 
 
 
 
 
 
 
 
 
Okay so: 
 

It looks like it doesn't schedule a re-scan or anything when a new repository is added. I'm not sure that is expected or not.
 

On a manual Re-Scan it picked up the new repository with a Jenkinsfile.
 

Again, it didn't schedule a re-scan on repository deletion. I'm not sure if that is expected or not.
 

On a manual Re-Scan it removed the repository.
 
 
So it looks like my original bug was fixed at some point. Not sure about responding to events... It'd be tricky for the adds – e.g. I could see scheduling a rescan in, say, 5 minutes (to give the user time to add a Jenkinsfile). 
Deletion can probably be scheduled immediately. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [nuget-plugin] (JENKINS-35316) nuget plugin succeeds when nupkg doesn't exist

2016-06-02 Thread rd.m...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russell Mora created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35316 
 
 
 
  nuget plugin succeeds when nupkg doesn't exist  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 nuget-plugin 
 
 
 

Created:
 

 2016/Jun/02 7:40 PM 
 
 
 

Environment:
 

 Jenkins 1.651.2  NuGet 0.5  
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Russell Mora 
 
 
 
 
 
 
 
 
 
 
I have specified the package to publish to my NuGet feed with no wildcards, i.e.  
agsimsetup.$BUILD_ID.nupkg 
This works fine: 
Starting agdev publication [agsimsetup-dev] $ nuget push agsimsetup.2.2.1.0-build-69.nupkg  -Source https://api.bintray.com/nuget/aboutgolf/agdev -NonInteractive Pushing agsimsetup.2.2.1.0-build-69.nupkg to 'https://api.bintray.com/nuget/aboutgolf/agdev'... PUT https://api.bintray.com/nuget/aboutgolf/agdev/ Created https://api.bintray.com/nuget/aboutgolf/agdev/ 2021ms Your package was pushed. Ended agdev publication Finished: SUCCESS 
If, however, I specify a non-existing package no error is generated. For example, if the change the package to publish to: 
agsimbadsetup.$BUILD_ID.nupkg 
Then the publish still succeeds (though of course nothing is published): 

[JIRA] [core] (JENKINS-35087) Old data not upgrading from 1.653 to 1.651.2

2016-06-02 Thread t...@us.ibm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tammy Parker commented on  JENKINS-35087 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Old data not upgrading from 1.653 to 1.651.2  
 
 
 
 
 
 
 
 
 
 
I have the same error starting today when I attempted to update all of my plugins. Also, after the update attempt via 'Download now and install after restart', the plugins are still listed as needing an update; I think the update did not occur as I forgot to check each individual plugin before pushing the 'Download now and install after restart' button... 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [timestamper-plugin] (JENKINS-35315) Timestamper panel is not displayed because of mixed content block

2016-06-02 Thread jenkin...@caspowa.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pavel Jozef created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35315 
 
 
 
  Timestamper panel is not displayed because of mixed content block  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Steven G Brown 
 
 
 

Attachments:
 

 mixed_content.png 
 
 
 

Components:
 

 timestamper-plugin 
 
 
 

Created:
 

 2016/Jun/02 7:37 PM 
 
 
 

Environment:
 

 Jenkins 2.7  Chrome 51.0  Timestamper 1.8.2  
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Pavel Jozef 
 
 
 
 
 
 
 
 
 
 
When Jenkins is running behind HTTPS proxy, some _javascript_ files cannot be loaded. 
Please notice that this issue disappears if I downgrade Timestamper to version 1.7.4. 
 
 
 
 
 
 
 
 
 
 
 
 

[JIRA] [docker-build-publish-plugin] (JENKINS-29932) Docker build publish plugin throws error "Please login prior to push" after build the image

2016-06-02 Thread mrich...@paychex.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark R commented on  JENKINS-29932 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Docker build publish plugin throws error "Please login prior to push" after build the image  
 
 
 
 
 
 
 
 
 
 
I attached a debugger and managed to figure out my issue. My /home/jenkins/.dockercfg file had both a http and https url endpoint for my registry. The https endpoint had the correct password set. The http one did not. This may have something to do with me recently changing my password. To correct it I removed the stale http entry. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-19686) Workspace directory randomly deleted

2016-06-02 Thread ajbarbe...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Barber commented on  JENKINS-19686 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Workspace directory randomly deleted  
 
 
 
 
 
 
 
 
 
 
A follow up on my case. I just realized that what is different for me is that I share a slave root across slaves. This is ok for me, because jobs are only tied to a single node. But by moving the job off a slave to another, it opened up the workspace for reaping (in the context of the old slave) which I don't want. You could argue user error, but then there is no checking in jenkins to ensure slaves have different roots (which implies that it must be allowed to share roots). The cleanup thread could be enhanced to check with all slaves that share a root to make sure none of them own the active workspace.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [docker-build-publish-plugin] (JENKINS-29932) Docker build publish plugin throws error "Please login prior to push" after build the image

2016-06-02 Thread mrich...@paychex.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark R edited a comment on  JENKINS-29932 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Docker build publish plugin throws error "Please login prior to push" after build the image  
 
 
 
 
 
 
 
 
 
 I am having the same issue.  I have the latest version of the 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] [docker-build-publish-plugin] (JENKINS-29932) Docker build publish plugin throws error "Please login prior to push" after build the image

2016-06-02 Thread mrich...@paychex.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark R commented on  JENKINS-29932 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Docker build publish plugin throws error "Please login prior to push" after build the image  
 
 
 
 
 
 
 
 
 
 
I am having the same 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] [p4-plugin] (JENKINS-35314) p4 Plugin does not trigger Pipeline builds

2016-06-02 Thread kyle_m...@dell.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kyle Mott created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35314 
 
 
 
  p4 Plugin does not trigger Pipeline builds  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Jesse Glick 
 
 
 

Components:
 

 p4-plugin, workflow-plugin 
 
 
 

Created:
 

 2016/Jun/02 6:49 PM 
 
 
 

Environment:
 

 Jenkins 1.651.2  p4 Plugin 1.4.0  Pipeline 2.1  Pipeline SCM 2.0 
 
 
 

Labels:
 

 p4-plugin pipeline trigger 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Kyle Mott 
 
 
 
 
 
 
 
 
 
 
I didn't want this to get lost since 

JENKINS-29979
 was closed out. 
The P4 Trigger isn't firing a Pipeline job off when a POST request comes in per the /p4/ help page in Jenkins, or if you do a manual trigger. I do see the request come in, after which P4 probes the Pipeline projects, but then nothing happens: 

 
Jun 02, 2016 11:36:16 AM INFO org.jenkinsci.plugins.p4.trigger

[JIRA] [docker-build-publish-plugin] (JENKINS-33116) Not logging in on new slave agent in kubernetes.

2016-06-02 Thread mrich...@paychex.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark R commented on  JENKINS-33116 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Not logging in on new slave agent in kubernetes.  
 
 
 
 
 
 
 
 
 
 
I am also hitting this issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [security] (JENKINS-7645) Lost administrator rights- I'm the only admin

2016-06-02 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev commented on  JENKINS-7645 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Lost administrator rights- I'm the only admin  
 
 
 
 
 
 
 
 
 
 
Gennadiy Garagulya Please create a new issue for it. If it happens, it's a regression somewhere in the fresh 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] [security] (JENKINS-7645) Lost administrator rights- I'm the only admin

2016-06-02 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev resolved as Cannot Reproduce 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-7645 
 
 
 
  Lost administrator rights- I'm the only admin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Oleg Nenashev 
 
 
 

Status:
 
 Reopened Resolved 
 
 
 

Resolution:
 
 Cannot Reproduce 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [acceptance-test-harness] (JENKINS-35134) Large numbers of ATH tests failing against 2.6

2016-06-02 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Bayer commented on  JENKINS-35134 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Large numbers of ATH tests failing against 2.6  
 
 
 
 
 
 
 
 
 
 
PR opened - https://github.com/jenkinsci/acceptance-test-harness/pull/114 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [acceptance-test-harness] (JENKINS-35134) Large numbers of ATH tests failing against 2.6

2016-06-02 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Bayer commented on  JENKINS-35134 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Large numbers of ATH tests failing against 2.6  
 
 
 
 
 
 
 
 
 
 
Note, this doesn't solve the docker failures, which look like they may actually be credentials related... 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [acceptance-test-harness] (JENKINS-35134) Large numbers of ATH tests failing against 2.6

2016-06-02 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Bayer commented on  JENKINS-35134 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Large numbers of ATH tests failing against 2.6  
 
 
 
 
 
 
 
 
 
 
Yeah, tried a number of different tests that had been failing and they passed with that change, when run on Linux. Not sure whether we care enough about OS X to worry about fixing it there too... 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [docker-custom-build-environment-plugin] (JENKINS-35025) Container command '/bin/cat' not found or does not exist

2016-06-02 Thread ww...@warddevelopment.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wills Ward commented on  JENKINS-35025 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Container command '/bin/cat' not found or does not exist  
 
 
 
 
 
 
 
 
 
 
If you remove the `--workdir` argument, the docker will launch properly. I'm not sure why though. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [acceptance-test-harness] (JENKINS-35134) Large numbers of ATH tests failing against 2.6

2016-06-02 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Bayer commented on  JENKINS-35134 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Large numbers of ATH tests failing against 2.6  
 
 
 
 
 
 
 
 
 
 
https://github.com/abayer/acceptance-test-harness/commit/da74a64fef9edee046e3d31dd405e7ebed85a27b seems to fix it for Linux, but not for OS X. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [java-client-api] (JENKINS-35313) Upgrade maven-site-plugin to 3.5.1 and site generation

2016-06-02 Thread jenk...@soebes.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karl-Heinz Marbaise updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35313 
 
 
 
  Upgrade maven-site-plugin to 3.5.1 and site generation  
 
 
 
 
 
 
 
 
 

Change By:
 
 Karl-Heinz Marbaise 
 
 
 
 
 
 
 
 
 
 Inherit menu for modules, parent etc. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [java-client-api] (JENKINS-35313) Upgrade maven-site-plugin to 3.5.1 and site generation

2016-06-02 Thread jenk...@soebes.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karl-Heinz Marbaise created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35313 
 
 
 
  Upgrade maven-site-plugin to 3.5.1 and site generation  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Karl-Heinz Marbaise 
 
 
 

Components:
 

 java-client-api 
 
 
 

Created:
 

 2016/Jun/02 6:25 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Karl-Heinz Marbaise 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because y

[JIRA] [github-organization-folder-plugin] (JENKINS-34246) Old repos aren't removed

2016-06-02 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Recena Soto commented on  JENKINS-34246 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Old repos aren't removed  
 
 
 
 
 
 
 
 
 
 
Jesse Glick I'm waiting for information from Christian Höltje in order to confirm if there is a bug o not. I can not reproduce 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] [core] (JENKINS-31661) Jenkins.rootUrl too often unset or incorrect

2016-06-02 Thread amu...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonio Muñiz commented on  JENKINS-31661 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins.rootUrl too often unset or incorrect  
 
 
 
 
 
 
 
 
 
 
Yeah, agreed. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-31661) Jenkins.rootUrl too often unset or incorrect

2016-06-02 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Recena Soto commented on  JENKINS-31661 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins.rootUrl too often unset or incorrect  
 
 
 
 
 
 
 
 
 
 
 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] [acceptance-test-harness] (JENKINS-35134) Large numbers of ATH tests failing against 2.6

2016-06-02 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Bayer commented on  JENKINS-35134 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Large numbers of ATH tests failing against 2.6  
 
 
 
 
 
 
 
 
 
 
https://github.com/seleniumhq/selenium/issues/825 seems to be the 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] [workflow-multibranch-plugin] (JENKINS-35310) "Trigger builds remotely" doesn't save authToken

2016-06-02 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Recena Soto assigned an issue to Jesse Glick 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35310 
 
 
 
  "Trigger builds remotely" doesn't save authToken  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Recena Soto 
 
 
 

Assignee:
 
 Manuel Recena Soto 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] [build-pipeline-plugin] (JENKINS-34724) No visible hyphen between displayed builds

2016-06-02 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Recena Soto commented on  JENKINS-34724 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: No visible hyphen between displayed builds  
 
 
 
 
 
 
 
 
 
 
Nico Falk Yes, it is only by design (I'm not a designer). If you have any proposal for that...it will be welcome. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [blueocean-plugin] (JENKINS-35312) Log line numbers stop rendering at screen height

2016-06-02 Thread amu...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonio Muñiz created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35312 
 
 
 
  Log line numbers stop rendering at screen height  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Michael Neale 
 
 
 

Attachments:
 

 line-numbers.png 
 
 
 

Components:
 

 blueocean-plugin 
 
 
 

Created:
 

 2016/Jun/02 6:18 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Antonio Muñiz 
 
 
 
 
 
 
 
 
 
 
As shown is the screenshot. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
  

[JIRA] [external-workspace-manager-plugin] (JENKINS-35279) [EWM] [INFRA] Set-up CI for ewm project

2016-06-02 Thread somai.alexan...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alexandru Somai closed an issue as Duplicate 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35279 
 
 
 
  [EWM] [INFRA] Set-up CI for ewm project  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alexandru Somai 
 
 
 

Status:
 
 Open Closed 
 
 
 

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] [external-workspace-manager-plugin] (JENKINS-35279) [EWM] [INFRA] Set-up CI for ewm project

2016-06-02 Thread somai.alexan...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alexandru Somai updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35279 
 
 
 
  [EWM] [INFRA] Set-up CI for ewm project  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alexandru Somai 
 
 
 
 
 
 
 
 
 
 Set-up CI for the external workspace manager plugin. https://github.com/jenkinsci/external-workspace-manager-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] [external-workspace-manager-plugin] (JENKINS-35192) [EWM] Implement the exwsAllocate step

2016-06-02 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-35192 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: [EWM] Implement the exwsAllocate step  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Alexandru Somai Path: src/main/java/org/jenkinsci/plugins/ewm/definitions/Disk.java src/main/java/org/jenkinsci/plugins/ewm/steps/ExwsAllocateExecution.java src/main/java/org/jenkinsci/plugins/ewm/steps/ExwsAllocateStep.java src/main/java/org/jenkinsci/plugins/ewm/steps/ExwsExecution.java src/main/java/org/jenkinsci/plugins/ewm/steps/ExwsStep.java src/main/java/org/jenkinsci/plugins/ewm/steps/model/ExternalWorkspace.java src/main/java/org/jenkinsci/plugins/ewm/strategies/DiskAllocationStrategy.java src/main/java/org/jenkinsci/plugins/ewm/strategies/MostUsableSpaceStrategy.java src/main/resources/org/jenkinsci/plugins/ewm/definitions/Disk/config.jelly src/main/resources/org/jenkinsci/plugins/ewm/definitions/Disk/help-masterMountPoint.html src/main/resources/org/jenkinsci/plugins/ewm/steps/ExwsAllocateStep/config.jelly src/main/resources/org/jenkinsci/plugins/ewm/steps/ExwsStep/config.jelly http://jenkins-ci.org/commit/external-workspace-manager-plugin/7f24a89f3b3a5cb9385e92899923ce76562b1f10 Log: JENKINS-35192 Implement the exwsAllocate step for the upstream job 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [external-workspace-manager-plugin] (JENKINS-35192) [EWM] Implement the exwsAllocate step

2016-06-02 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-35192 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: [EWM] Implement the exwsAllocate step  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Alexandru Somai Path: src/main/java/org/jenkinsci/plugins/ewm/steps/ExwsAllocateExecution.java src/main/java/org/jenkinsci/plugins/ewm/steps/ExwsAllocateStep.java src/main/java/org/jenkinsci/plugins/ewm/strategies/DiskAllocationStrategy.java src/main/resources/org/jenkinsci/plugins/ewm/steps/ExwsAllocateStep/help-diskPoolId.html src/main/resources/org/jenkinsci/plugins/ewm/steps/ExwsAllocateStep/help-upstream.html src/main/resources/org/jenkinsci/plugins/ewm/steps/ExwsStep/help-externalWorkspace.html http://jenkins-ci.org/commit/external-workspace-manager-plugin/5b8a7a31f0ffbdf5b35103e75298901457e2f0b6 Log: JENKINS-35192 Use AbortException. Add missing help files. 
Compare: https://github.com/jenkinsci/external-workspace-manager-plugin/compare/7f24a89f3b3a^...5b8a7a31f0ff 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [external-workspace-manager-plugin] (JENKINS-35192) [EWM] Implement the exwsAllocate step

2016-06-02 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-35192 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: [EWM] Implement the exwsAllocate step  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Alexandru Somai Path: src/main/java/org/jenkinsci/plugins/ewm/steps/ExwsAllocateExecution.java http://jenkins-ci.org/commit/external-workspace-manager-plugin/6b9633eddfdff3b16c6a73f82eaa599ed0fd7173 Log: JENKINS-35192 Enhance the error messages 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [external-workspace-manager-plugin] (JENKINS-35192) [EWM] Implement the exwsAllocate step

2016-06-02 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-35192 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: [EWM] Implement the exwsAllocate step  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Alexandru Somai Path: src/main/java/org/jenkinsci/plugins/ewm/definitions/Disk.java src/main/java/org/jenkinsci/plugins/ewm/steps/ExwsAllocateExecution.java src/main/java/org/jenkinsci/plugins/ewm/steps/ExwsAllocateStep.java src/main/java/org/jenkinsci/plugins/ewm/steps/model/ExternalWorkspace.java src/main/java/org/jenkinsci/plugins/ewm/strategies/DiskAllocationStrategy.java src/main/java/org/jenkinsci/plugins/ewm/strategies/MostUsableSpaceStrategy.java http://jenkins-ci.org/commit/external-workspace-manager-plugin/357d667ce86f210acb296addfb388279db9907e2 Log: JENKINS-35192 Additional null checks 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [core] (JENKINS-34438) Activate JSHint during the build process

2016-06-02 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Recena Soto resolved as Done 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34438 
 
 
 
  Activate JSHint during the build process  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Recena Soto 
 
 
 

Status:
 
 Reopened Resolved 
 
 
 

Resolution:
 
 Done 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-35178) "Delete build step" button has bad layout in Safari

2016-06-02 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Recena Soto resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35178 
 
 
 
  "Delete build step" button has bad layout in Safari  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Recena Soto 
 
 
 

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] [bitbucket-branch-source-plugin] (JENKINS-33507) Bitbucket Server webhooks and Bitbucket Cloud build status notifications

2016-06-02 Thread mko...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mike Kobit commented on  JENKINS-33507 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Bitbucket Server webhooks and Bitbucket Cloud build status notifications  
 
 
 
 
 
 
 
 
 
 
The plugin that Antonio linked is the one we use, so it would be awesome if that was the supported one. 
I have a feeling that Bitbucket Server is not going to have generic hooks anytime soon, as those have been open for multiple years.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [external-workspace-manager-plugin] (JENKINS-35110) [EWM] Support global/node exws configs

2016-06-02 Thread somai.alexan...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alexandru Somai resolved as Done 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35110 
 
 
 
  [EWM] Support global/node exws configs  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alexandru Somai 
 
 
 

Status:
 
 In Progress Resolved 
 
 
 

Resolution:
 
 Done 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [acceptance-test-harness] (JENKINS-35134) Large numbers of ATH tests failing against 2.6

2016-06-02 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Bayer commented on  JENKINS-35134 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Large numbers of ATH tests failing against 2.6  
 
 
 
 
 
 
 
 
 
 
And even more specifically, Firefox run via Selenium - it works fine when I use Firefox myself. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-31915) Proxy settings in plugins page are ignored

2016-06-02 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-31915 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Proxy settings in plugins page are ignored  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Emilio Escobar Path: core/src/main/java/hudson/ProxyConfiguration.java core/src/main/resources/hudson/Messages.properties core/src/main/resources/hudson/ProxyConfiguration/help-name.html http://jenkins-ci.org/commit/jenkins/81e00cc67957018b0d355740a1eeb2bcd21c0609 Log: [FIXED JENKINS-31915] Proxy settings in plugins page are ignored (#1955) 
[FIXED JENKINS-31915] Proxy settings in plugins page are ignored 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-31915) Proxy settings in plugins page are ignored

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31915 
 
 
 
  Proxy settings in plugins page are ignored  
 
 
 
 
 
 
 
 
 

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] [external-workspace-manager-plugin] (JENKINS-35110) [EWM] Support global/node exws configs

2016-06-02 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-35110 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: [EWM] Support global/node exws configs  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Alexandru Somai Path: pom.xml src/main/java/org/jenkinsci/plugins/ewm/definitions/Disk.java src/main/java/org/jenkinsci/plugins/ewm/definitions/DiskPool.java src/main/java/org/jenkinsci/plugins/ewm/definitions/Template.java src/main/java/org/jenkinsci/plugins/ewm/nodes/DiskNode.java src/main/java/org/jenkinsci/plugins/ewm/nodes/ExternalWorkspaceProperty.java src/main/java/org/jenkinsci/plugins/ewm/steps/ExwsAllocateExecution.java src/main/java/org/jenkinsci/plugins/ewm/steps/ExwsAllocateStep.java src/main/java/org/jenkinsci/plugins/ewm/steps/ExwsExecution.java src/main/java/org/jenkinsci/plugins/ewm/steps/ExwsStep.java src/main/resources/org/jenkinsci/plugins/ewm/Messages.properties src/main/resources/org/jenkinsci/plugins/ewm/definitions/Disk/config.jelly src/main/resources/org/jenkinsci/plugins/ewm/definitions/Disk/help-diskId.html src/main/resources/org/jenkinsci/plugins/ewm/definitions/Disk/help-name.html src/main/resources/org/jenkinsci/plugins/ewm/definitions/Disk/help-physicalPathOnDisk.html src/main/resources/org/jenkinsci/plugins/ewm/definitions/DiskPool/config.jelly src/main/resources/org/jenkinsci/plugins/ewm/definitions/DiskPool/help-description.html src/main/resources/org/jenkinsci/plugins/ewm/definitions/DiskPool/help-diskPoolId.html src/main/resources/org/jenkinsci/plugins/ewm/definitions/DiskPool/help-name.html src/main/resources/org/jenkinsci/plugins/ewm/definitions/Template/config.jelly src/main/resources/org/jenkinsci/plugins/ewm/definitions/Template/help-diskPoolRefId.html src/main/resources/org/jenkinsci/plugins/ewm/definitions/Template/help-label.html src/main/resources/org/jenkinsci/plugins/ewm/index.jelly src/main/resources/org/jenkinsci/plugins/ewm/nodes/DiskNode/config.jelly src/main/resources/org/jenkinsci/plugins/ewm/nodes/DiskNode/help-diskRefId.html src/main/resources/org/jenkinsci/plugins/ewm/nodes/DiskNode/help-localRootPath.html src/main/resources/org/jenkinsci/plugins/ewm/nodes/ExternalWorkspaceProperty/config.jelly src/main/resources/org/jenkinsci/plugins/ewm/nodes/ExternalWorkspaceProperty/help-diskPoolRefId.html src/main/resources/org/jenkinsci/plugins/ewm/steps/ExwsAllocateStep/config.jelly src/main/resources/org/jenkinsci/plugins/ewm/steps/ExwsAllocateStep/global.jelly src/main/resources/org/jenkinsci/plugins/ewm/steps/ExwsStep/config.jelly src/main/resources/org/jenkinsci/plugins/ewm/steps/ExwsStep/global.jelly http://jenkins-ci.org/commit/external-workspace-manager-plugin/fcef9dba3d989c075c76bfac00d1dc0848587d11 Log: JENKINS-35110 Add exws definitions and templates as global Jenkins configs (#1) 
 

JENKINS-35110 Add exws definitions and templates as global Jenkins configs. Add exws node property.
 
 
 

JENKINS-35110 Make available exws global configs and node config for the pipeline steps.
 
 
 

JENKINS-35110 Replace hetero-list with repeatableProperty.
 
 
 

JENKINS-35110 Add help labels.

[JIRA] [core] (JENKINS-35206) NullPointerException on startup after update from 2.5 to 2.6

2016-06-02 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-35206 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: NullPointerException on startup after update from 2.5 to 2.6  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/jenkins/install/InstallState.java test/src/test/java/jenkins/install/InstallStateTest.java http://jenkins-ci.org/commit/jenkins/1b2711c9578f5b34bc452fcc3f2dd055b1c0865c Log: JENKINS-35206 - Make the InstallState object deserialization robust against corrupted files (#2387) 
 

JENKINS-35206 - Add unit tests for the deserialization logic
 
 
 

JENKINS-35206 - Install state should be robust against messed statuses when deserializing objects
 
 
 

JENKINS-35206 - Fix the license header in thre test file
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-34881) InstallationWizard: "Create first account" pops up if SecurityRealm is configured by startup scripts

2016-06-02 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-34881 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: InstallationWizard: "Create first account" pops up if SecurityRealm is configured by startup scripts  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Keith Zantow Path: core/src/main/java/hudson/PluginManager.java core/src/main/java/jenkins/install/InstallState.java core/src/main/java/jenkins/install/InstallUtil.java core/src/main/java/jenkins/install/SetupWizard.java core/src/main/resources/jenkins/install/SetupWizard/authenticate-security-token.jelly http://jenkins-ci.org/commit/jenkins/723dfca37bcf3fecd33c75eaca01ce0d07014d70 Log: [FIXED JENKINS-34881] - Handle pre-configured security settings for new installs (#2364) 
 

[FIXED JENKINS-34881] - handle non-default security settings for new installs
 
 
 

Ensure permissions
 
 
 

Initial security authentication token should still follow redirects
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and 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   3   >