[JIRA] (JENKINS-17228) Fail build when subversion workspace is locked

2016-11-09 Thread ruben.st...@mevis.fraunhofer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ruben Stein commented on  JENKINS-17228  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Fail build when subversion workspace is locked   
 

  
 
 
 
 

 
 The link to the fix is broken, if someone could point to these two lines again, one could try to rebuild a patched version.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39376) StackOverflowError involving CpsTransformer$_visitWithSafepoint_closure6.doCall

2016-11-09 Thread erik.hakans...@wirelesscar.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Erik Hakansson commented on  JENKINS-39376  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: StackOverflowError involving CpsTransformer$_visitWithSafepoint_closure6.doCall   
 

  
 
 
 
 

 
 Perhaps. I wonder, however if this is a general groovy issue, rather than specific for this plugin. I know next to nothing about groovy's inner workings, but perhaps there is some recursion happening when parsing scripts. And if so, I suppose this issue is unavoidable. At any rate, it should be a rare issue since I assume most people don't run Jenkins with an ancient configuration   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39010) Comment Added event does not work

2016-11-09 Thread af...@plumgrid.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 fahd arshad updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39010  
 
 
  Comment Added event does not work   
 

  
 
 
 
 

 
Change By: 
 fahd arshad  
 

  
 
 
 
 

 
 We recently upgraded our jenkins server from  1  version 2 . 67 28  to 2. 25 30 . Gerrit trigger (v2.22.0)  on *comments added Contains Regex* does not seem to work ever since the upgrade. Other gerrit triggers seems to be working flawlessly.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39010) Comment Added event does not work

2016-11-09 Thread af...@plumgrid.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 fahd arshad commented on  JENKINS-39010  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Comment Added event does not work   
 

  
 
 
 
 

 
 Any update on this ? gerrit-trigger 2.22.0 version does not seem to work with Jenkins version 2.30   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39621) Pipeline job loop after polling always find changes

2016-11-09 Thread assafl1...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Leibo commented on  JENKINS-39621  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline job loop after polling always find changes   
 

  
 
 
 
 

 
 Hi Mark, I configured the same pipeline job on a new server, 2.7.3 with Git plugin version 3.0.0 and the problem doesn't occur... The pipeline job is a basic pool SCB (every 5 minutes), pipeline script from SCM --> Git, branch origin/develop and path pipeline/pipeline for the script. The polling log is smaller than the one and is not repeated 3 times like the ones we see. Perhaps some Git cache issues on the server? 

 

Started on Nov 10, 2016 9:42:00 AM
Using strategy: Default
[poll] Last Built Revision: Revision 9b3f801b5ce8d6649c25ddd4a573801c9a6b5a23 (refs/remotes/origin/develop)
using GIT_SSH to set credentials 
 > git ls-remote -h ssh://my.git.server/git/tests.git # timeout=10
Found 3 remote heads on ssh://my.git.server/git/tests.git
[poll] Latest remote head revision on refs/heads/develop is: 9b3f801b5ce8d6649c25ddd4a573801c9a6b5a23 - already built by 1
Done. Took 0.15 sec
No changes
 

 Any hint on how to debug this better?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For 

[JIRA] (JENKINS-39534) When Jenkins restarts, the groovy scripts are lost

2016-11-09 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita commented on  JENKINS-39534  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: When Jenkins restarts, the groovy scripts are lost   
 

  
 
 
 
 

 
 Hi Kiruahxh, could you take a look at the jar attached to JENKINS-39620, if you have the time, please? It contains the fix that should be release in the next days after Ioannis and I finish testing it. Cheers, Bruno  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39620) Saving a job with Active Choice 1.4 parameters after upgrade to v1.5 resets scriptlet parameters

2016-11-09 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39620  
 
 
  Saving a job with Active Choice 1.4 parameters after upgrade to v1.5 resets scriptlet parameters   
 

  
 
 
 
 

 
Change By: 
 Bruno P. Kinoshita  
 
 
Attachment: 
 uno-choice.hpi  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-27299) Refactor Disable Build feature out of AbstractProject for Pipeline Compatibility

2016-11-09 Thread claus...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 clausfod commented on  JENKINS-27299  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Refactor Disable Build feature out of AbstractProject for Pipeline Compatibility   
 

  
 
 
 
 

 
 Jesse Glick: Any news  ? We need this functionality to be able to disable or enable release jobs from criterias in other jobs.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38624) MSBuild Projects no longer work after upgrading to 1.8.0

2016-11-09 Thread para...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Parag Thakur commented on  JENKINS-38624  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: MSBuild Projects no longer work after upgrading to 1.8.0   
 

  
 
 
 
 

 
 any workaround?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39636) Could not initialize class org.jfree.chart.JFreeChart

2016-11-09 Thread sites+jenk...@dan.cx (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Lo Nigro updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39636  
 
 
  Could not initialize class org.jfree.chart.JFreeChart   
 

  
 
 
 
 

 
Change By: 
 Daniel Lo Nigro  
 

  
 
 
 
 

 
 All graphs in Jenkins (eg. /buildTimeGraph/png) result in this error: "javax.servlet.ServletException: java.lang.NoClassDefFoundError: Could not initialize class org.jfree.chart.JFreeChart"JENKINS-21839 looked similar, but I've confirmed that -Djava.awt.headless=true is already being passed to the Java process. Full stack trace: https://gist.github.com/Daniel15/a4efd1d55ef37239e0fde397b62153bf  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39636) Could not initialize class org.jfree.chart.JFreeChart

2016-11-09 Thread sites+jenk...@dan.cx (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Lo Nigro created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39636  
 
 
  Could not initialize class org.jfree.chart.JFreeChart   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2016/Nov/10 6:08 AM  
 
 
Environment: 
 Debian Testing  Jenkins 2.19.2  Java 1.8.0_111  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Daniel Lo Nigro  
 

  
 
 
 
 

 
 All graphs in Jenkins (eg. /buildTimeGraph/png) result in this error: "javax.servlet.ServletException: java.lang.NoClassDefFoundError: Could not initialize class org.jfree.chart.JFreeChart" JENKINS-21839 looked similar, but I've confirmed that -Djava.awt.headless=true is already being passed to the Java process.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 

[JIRA] (JENKINS-39596) JNLPSlave fails to connect with Java WebStart call

2016-11-09 Thread matthew.ad...@arria.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Adams commented on  JENKINS-39596  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JNLPSlave fails to connect with Java WebStart call   
 

  
 
 
 
 

 
 We are unable to use our Windows slaves as a consequence of this. Is there a workaround or imminent fix please?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38913) DSL for choiceParam not working

2016-11-09 Thread kstew...@ea.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristan Stewart updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38913  
 
 
  DSL for choiceParam not working   
 

  
 
 
 
 

 
Change By: 
 Kristan Stewart  
 
 
Component/s: 
 job-dsl-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39635) Right click on expander should not open the test result

2016-11-09 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39635  
 
 
  Right click on expander should not open the test result   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2016/Nov/10 4:50 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 James Dumay  
 

  
 
 
 
 

 
 Not being able to right click on the expander makes it difficult to copy the test name In Scope 
 
Right click on expander should not open the test result 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 

[JIRA] (JENKINS-39634) Support downloading of attachments for tests

2016-11-09 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39634  
 
 
  Support downloading of attachments for tests   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2016/Nov/10 4:49 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 James Dumay  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins 

[JIRA] (JENKINS-39620) Saving a job with Active Choice 1.4 parameters after upgrade to v1.5 resets scriptlet parameters

2016-11-09 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-39620  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Saving a job with Active Choice 1.4 parameters after upgrade to v1.5 resets scriptlet parameters   
 

  
 
 
 
 

 
 Code changed in jenkins User: Bruno P. Kinoshita Path: src/findbugs/excludesFilter.xml src/main/java/org/biouno/unochoice/model/GroovyScript.java http://jenkins-ci.org/commit/active-choices-plugin/44c21fc6bab67a538d785712d2a3aa302d20ea1a Log: [FIXED JENKINS-39620] and JENKINS-39534 Revert change that marked fields as transient, and add FindBugs exclusion filters  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39534) When Jenkins restarts, the groovy scripts are lost

2016-11-09 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-39534  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: When Jenkins restarts, the groovy scripts are lost   
 

  
 
 
 
 

 
 Code changed in jenkins User: Bruno P. Kinoshita Path: src/findbugs/excludesFilter.xml src/main/java/org/biouno/unochoice/model/GroovyScript.java http://jenkins-ci.org/commit/active-choices-plugin/44c21fc6bab67a538d785712d2a3aa302d20ea1a Log: [FIXED JENKINS-39620] and JENKINS-39534 Revert change that marked fields as transient, and add FindBugs exclusion filters  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39620) Saving a job with Active Choice 1.4 parameters after upgrade to v1.5 resets scriptlet parameters

2016-11-09 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-39620  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Saving a job with Active Choice 1.4 parameters after upgrade to v1.5 resets scriptlet parameters   
 

  
 
 
 
 

 
 Code changed in jenkins User: Bruno P. Kinoshita Path: src/findbugs/excludesFilter.xml src/main/java/org/biouno/unochoice/model/GroovyScript.java http://jenkins-ci.org/commit/active-choices-plugin/cac73ce953ce6419e14ad2ad7a12b0982fb8652b Log: [FIXED JENKINS-39620] and JENKINS-39534 Revert change that marked fields as transient, and add FindBugs exclusion filters  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39534) When Jenkins restarts, the groovy scripts are lost

2016-11-09 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-39534  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: When Jenkins restarts, the groovy scripts are lost   
 

  
 
 
 
 

 
 Code changed in jenkins User: Bruno P. Kinoshita Path: src/findbugs/excludesFilter.xml src/main/java/org/biouno/unochoice/model/GroovyScript.java http://jenkins-ci.org/commit/active-choices-plugin/cac73ce953ce6419e14ad2ad7a12b0982fb8652b Log: [FIXED JENKINS-39620] and JENKINS-39534 Revert change that marked fields as transient, and add FindBugs exclusion filters  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-5242) Does not set contentType to html, renders as text

2016-11-09 Thread node...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Coggburn updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-5242  
 
 
  Does not set contentType to html, renders as text   
 

  
 
 
 
 

 
Change By: 
 Chris Coggburn  
 
 
Comment: 
 Same bug  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-5242) Does not set contentType to html, renders as text

2016-11-09 Thread node...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Coggburn updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-5242  
 
 
  Does not set contentType to html, renders as text   
 

  
 
 
 
 

 
Change By: 
 Chris Coggburn  
 
 
Comment: 
 Same bug  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-5242) Does not set contentType to html, renders as text

2016-11-09 Thread node...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Coggburn commented on  JENKINS-5242  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Does not set contentType to html, renders as text   
 

  
 
 
 
 

 
 Same bug  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-5242) Does not set contentType to html, renders as text

2016-11-09 Thread node...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Coggburn commented on  JENKINS-5242  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Does not set contentType to html, renders as text   
 

  
 
 
 
 

 
 Same bug  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38516) "Parsing cucumber.json" blocked by parallel job executions

2016-11-09 Thread mid...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 noob alot commented on  JENKINS-38516  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Parsing cucumber.json" blocked by parallel job executions   
 

  
 
 
 
 

 
 Forgive my ignorance w Jenkins: What if the updating part was done in a separate thread so the build itself can complete?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39620) Saving a job with Active Choice 1.4 parameters after upgrade to v1.5 resets scriptlet parameters

2016-11-09 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita commented on  JENKINS-39620  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Saving a job with Active Choice 1.4 parameters after upgrade to v1.5 resets scriptlet parameters   
 

  
 
 
 
 

 
 Oh! Fixing a FindBugs warning that was preventing the last release, I marked the secureScript and fallbackSecureScript, both as "transient". So these fields were not being persisted after you restarted Jenkins. I believe I know how to fix it, and once I've tested it, will cut a new release. Sorry for the trouble.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39620) Saving a job with Active Choice 1.4 parameters after upgrade to v1.5 resets scriptlet parameters

2016-11-09 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita started work on  JENKINS-39620  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Bruno P. Kinoshita  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39633) Jenkins Failed To start After Pipeline Plugin Update

2016-11-09 Thread evan.prat...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Evan Pratama created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39633  
 
 
  Jenkins Failed To start After Pipeline Plugin Update   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 jenkins.log, Screen Shot 2016-11-10 at 14.10.40.png  
 
 
Components: 
 core, pipeline  
 
 
Created: 
 2016/Nov/10 3:19 AM  
 
 
Environment: 
 Jenkins 2.30  OS: CentOS release 6.8 (Final)  
 
 
Labels: 
 pipeline jenkins jenkins2.3  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Evan Pratama  
 

  
 
 
 
 

 
 Just updated the outdated plugins (pipeline) and ticked on restart. It shows a stacktrace on the main screen:   startup log: jenkins.log   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
   

[JIRA] (JENKINS-39620) Saving a job with Active Choice 1.4 parameters after upgrade to v1.5 resets scriptlet parameters

2016-11-09 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita commented on  JENKINS-39620  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Saving a job with Active Choice 1.4 parameters after upgrade to v1.5 resets scriptlet parameters   
 

  
 
 
 
 

 
 At least related, if not duplicated.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39632) Unselecting "Build when a change is pushed to GitHub" results in NullPointerException and breaks all builds in Jenkins

2016-11-09 Thread node...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Coggburn updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39632  
 
 
  Unselecting "Build when a change is pushed to GitHub" results in NullPointerException and breaks all builds in Jenkins   
 

  
 
 
 
 

 
Change By: 
 Chris Coggburn  
 

  
 
 
 
 

 
 Deselecting the "Build when a change is pushed to GitHub" checkbox for an existing project, causes a full page NullPointerException stack trace to appear and results in every job that uses GitHub webhooks on the same instance of Jenkins to fail.This change also causes the full page stack trace to be thrown every time the job's configuration is saved, only reverting the change with the Job Configuration History plugin allows Jenkins to be put back to normal.Additionally, it appears this causes a number of other core Jenkins tasks to fail with NullPointerExceptions. I hope to provide a ZIP from the Support plugin tomorrow that'll provide additional details.Here's what's removed from the job config.xml that causes the failure:{code}< triggers>  < com.cloudbees.jenkins.GitHubPushTrigger plugin="github@1.22.4">  {code}Here's the stack trace that happens when trying to save any edit to that job.{code}javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:236) 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.MetaClass$5.doDispatch(MetaClass.java:236) 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.MetaClass$5.doDispatch(MetaClass.java:236) 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:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) 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:1652) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at 

[JIRA] (JENKINS-39632) Unselecting "Build when a change is pushed to GitHub" results in NullPointerException and breaks all builds in Jenkins

2016-11-09 Thread node...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Coggburn updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39632  
 
 
  Unselecting "Build when a change is pushed to GitHub" results in NullPointerException and breaks all builds in Jenkins   
 

  
 
 
 
 

 
Change By: 
 Chris Coggburn  
 

  
 
 
 
 

 
 Deselecting the "Build when a change is pushed to GitHub" checkbox for an existing project, causes a full page NullPointerException stack trace to appear and results in every job that uses GitHub webhooks on the same instance of Jenkins to fail.This change also causes the full page stack trace to be thrown every time the job's configuration is saved, only reverting the change with the Job Configuration History plugin allows Jenkins to be put back to normal.Additionally, it appears this causes a number of other core Jenkins tasks to fail with NullPointerExceptions. I hope to provide a ZIP from the Support plugin tomorrow that'll provide additional details.Here's  what's removed from  the  job config.xml that causes the failure:{code}{code}Here's the  stack trace that happens when trying to save any edit to that job.{code}javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:236) 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.MetaClass$5.doDispatch(MetaClass.java:236) 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.MetaClass$5.doDispatch(MetaClass.java:236) 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:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) 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:1652) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at 

[JIRA] (JENKINS-39632) Unselecting "Build when a change is pushed to GitHub" results in NullPointerException and breaks all builds in Jenkins

2016-11-09 Thread node...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Coggburn updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39632  
 
 
  Unselecting "Build when a change is pushed to GitHub" results in NullPointerException and breaks all builds in Jenkins   
 

  
 
 
 
 

 
Change By: 
 Chris Coggburn  
 
 
Environment: 
 Jenkins 2.30Debian 8.6, 64-bit, 3.16.36-1+deb8u2Jenkins is run directly, not through docker or tomcat.nginx is used as revert proxy, but webhooks are exposed directly to JenkinsJenkins was installed from the pkg.jenkins-ci.org apt repoFrom /systemInfo: {code} awt.toolkit sun.awt.X11.XToolkitexecutable-war /usr/share/jenkins/jenkins.warfile.encoding UTF-8file.encoding.pkg sun.iofile.separator /hudson.DNSMultiCast.disabled truejava.awt.graphicsenv sun.awt.X11GraphicsEnvironmentjava.awt.headless truejava.awt.printerjob sun.print.PSPrinterJobjava.class.path /usr/share/jenkins/jenkins.warjava.class.version 51.0java.endorsed.dirs /usr/lib/jvm/java-7-oracle/jre/lib/endorsedjava.ext.dirs /usr/lib/jvm/java-7-oracle/jre/lib/ext:/usr/java/packages/lib/extjava.home /usr/lib/jvm/java-7-oracle/jrejava.io.tmpdir /tmpjava.library.path /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/libjava.runtime.name Java(TM) SE Runtime Environmentjava.runtime.version 1.7.0_80-b15java.specification.name Java Platform API Specificationjava.specification.vendor Oracle Corporationjava.specification.version 1.7java.vendor Oracle Corporationjava.vendor.url http://java.oracle.com/java.vendor.url.bug http://bugreport.sun.com/bugreport/java.version 1.7.0_80java.vm.info mixed modejava.vm.name Java HotSpot(TM) 64-Bit Server VMjava.vm.specification.name Java Virtual Machine Specificationjava.vm.specification.vendor Oracle Corporationjava.vm.specification.version 1.7java.vm.vendor Oracle Corporationjava.vm.version 24.80-b11jna.loaded truejna.platform.library.path /usr/lib/x86_64-linux-gnu:/lib/x86_64-linux-gnu:/lib64:/usr/lib:/lib:/lib/i386-linux-gnu:/lib/i386-linux-gnu/i686/cmov:/usr/lib/i386-linux-gnu:/usr/lib/x86_64-linux-gnu/libfakerootjnidispatch.path /tmp/jna--1712433994/jna2257273014292489378.tmpline.separator mail.smtp.sendpartial truemail.smtps.sendpartial trueos.arch amd64os.name Linuxos.version 3.16.0-4-amd64path.separator :sessionTimeout 480sun.arch.data.model 64sun.boot.class.path /usr/lib/jvm/java-7-oracle/jre/lib/resources.jar:/usr/lib/jvm/java-7-oracle/jre/lib/rt.jar:/usr/lib/jvm/java-7-oracle/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-7-oracle/jre/lib/jsse.jar:/usr/lib/jvm/java-7-oracle/jre/lib/jce.jar:/usr/lib/jvm/java-7-oracle/jre/lib/charsets.jar:/usr/lib/jvm/java-7-oracle/jre/lib/jfr.jar:/usr/lib/jvm/java-7-oracle/jre/classessun.boot.library.path /usr/lib/jvm/java-7-oracle/jre/lib/amd64sun.cpu.endian littlesun.cpu.isalist sun.font.fontmanager sun.awt.X11FontManagersun.io.unicode.encoding UnicodeLittlesun.java.command /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080 --ajp13Port=-1sun.java.launcher SUN_STANDARDsun.jnu.encoding UTF-8sun.management.compiler HotSpot 64-Bit Tiered Compilerssun.os.patch.level unknownuser.country USuser.dir /user.home /data/jenkinsuser.language enuser.name jenkinsuser.timezone America/Denver {code}  {code} _ /usr/bin/daemonANDROID_HOME /data/android-sdk-linuxDERBY_HOME /usr/lib/jvm/java-7-oracle/dbGRADLE_HOME /data/gradleHOME 

[JIRA] (JENKINS-39632) Unselecting "Build when a change is pushed to GitHub" results in NullPointerException and breaks all builds in Jenkins

2016-11-09 Thread node...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Coggburn updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39632  
 
 
  Unselecting "Build when a change is pushed to GitHub" results in NullPointerException and breaks all builds in Jenkins   
 

  
 
 
 
 

 
Change By: 
 Chris Coggburn  
 
 
Environment: 
 Jenkins 2.30Debian 8.6, 64-bit, 3.16.36-1+deb8u2Jenkins is run directly, not through docker or tomcat.nginx is used as revert proxy, but webhooks are exposed directly to JenkinsJenkins was installed from the pkg.jenkins-ci.org apt repoFrom /systemInfo: {code} awt.toolkit sun.awt.X11.XToolkitexecutable-war /usr/share/jenkins/jenkins.warfile.encoding UTF-8file.encoding.pkg sun.iofile.separator /hudson.DNSMultiCast.disabled truejava.awt.graphicsenv sun.awt.X11GraphicsEnvironmentjava.awt.headless truejava.awt.printerjob sun.print.PSPrinterJobjava.class.path /usr/share/jenkins/jenkins.warjava.class.version 51.0java.endorsed.dirs /usr/lib/jvm/java-7-oracle/jre/lib/endorsedjava.ext.dirs /usr/lib/jvm/java-7-oracle/jre/lib/ext:/usr/java/packages/lib/extjava.home /usr/lib/jvm/java-7-oracle/jrejava.io.tmpdir /tmpjava.library.path /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/libjava.runtime.name Java(TM) SE Runtime Environmentjava.runtime.version 1.7.0_80-b15java.specification.name Java Platform API Specificationjava.specification.vendor Oracle Corporationjava.specification.version 1.7java.vendor Oracle Corporationjava.vendor.url http://java.oracle.com/java.vendor.url.bug http://bugreport.sun.com/bugreport/java.version 1.7.0_80java.vm.info mixed modejava.vm.name Java HotSpot(TM) 64-Bit Server VMjava.vm.specification.name Java Virtual Machine Specificationjava.vm.specification.vendor Oracle Corporationjava.vm.specification.version 1.7java.vm.vendor Oracle Corporationjava.vm.version 24.80-b11jna.loaded truejna.platform.library.path /usr/lib/x86_64-linux-gnu:/lib/x86_64-linux-gnu:/lib64:/usr/lib:/lib:/lib/i386-linux-gnu:/lib/i386-linux-gnu/i686/cmov:/usr/lib/i386-linux-gnu:/usr/lib/x86_64-linux-gnu/libfakerootjnidispatch.path /tmp/jna--1712433994/jna2257273014292489378.tmpline.separator mail.smtp.sendpartial truemail.smtps.sendpartial trueos.arch amd64os.name Linuxos.version 3.16.0-4-amd64path.separator :sessionTimeout 480sun.arch.data.model 64sun.boot.class.path /usr/lib/jvm/java-7-oracle/jre/lib/resources.jar:/usr/lib/jvm/java-7-oracle/jre/lib/rt.jar:/usr/lib/jvm/java-7-oracle/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-7-oracle/jre/lib/jsse.jar:/usr/lib/jvm/java-7-oracle/jre/lib/jce.jar:/usr/lib/jvm/java-7-oracle/jre/lib/charsets.jar:/usr/lib/jvm/java-7-oracle/jre/lib/jfr.jar:/usr/lib/jvm/java-7-oracle/jre/classessun.boot.library.path /usr/lib/jvm/java-7-oracle/jre/lib/amd64sun.cpu.endian littlesun.cpu.isalist sun.font.fontmanager sun.awt.X11FontManagersun.io.unicode.encoding UnicodeLittlesun.java.command /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080 --ajp13Port=-1sun.java.launcher SUN_STANDARDsun.jnu.encoding UTF-8sun.management.compiler HotSpot 64-Bit Tiered Compilerssun.os.patch.level unknownuser.country USuser.dir /user.home /data/jenkinsuser.language enuser.name jenkinsuser.timezone America/Denver {code}  {code} _ /usr/bin/daemonANDROID_HOME /data/android-sdk-linuxDERBY_HOME /usr/lib/jvm/java-7-oracle/dbGRADLE_HOME /data/gradleHOME 

[JIRA] (JENKINS-39632) Unselecting "Build when a change is pushed to GitHub" results in NullPointerException and breaks all builds in Jenkins

2016-11-09 Thread node...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Coggburn created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39632  
 
 
  Unselecting "Build when a change is pushed to GitHub" results in NullPointerException and breaks all builds in Jenkins   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Kirill Merkushev  
 
 
Components: 
 github-plugin  
 
 
Created: 
 2016/Nov/10 3:00 AM  
 
 
Environment: 
 Jenkins 2.30  Debian 8.6, 64-bit, 3.16.36-1+deb8u2  Jenkins is run directly, not through docker or tomcat.  nginx is used as revert proxy, but webhooks are exposed directly to Jenkins  Jenkins was installed from the pkg.jenkins-ci.org apt repo   From /systemInfo:awt.toolkit sun.awt.X11.XToolkit  executable-war /usr/share/jenkins/jenkins.war  file.encoding UTF-8  file.encoding.pkg sun.io  file.separator /  hudson.DNSMultiCast.disabled true  java.awt.graphicsenv sun.awt.X11GraphicsEnvironment  java.awt.headless true  java.awt.printerjob sun.print.PSPrinterJob  java.class.path /usr/share/jenkins/jenkins.war  java.class.version 51.0  java.endorsed.dirs /usr/lib/jvm/java-7-oracle/jre/lib/endorsed  java.ext.dirs /usr/lib/jvm/java-7-oracle/jre/lib/ext:/usr/java/packages/lib/ext  java.home /usr/lib/jvm/java-7-oracle/jre  java.io.tmpdir /tmp  java.library.path /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib  java.runtime.name Java(TM) SE Runtime Environment  java.runtime.version 1.7.0_80-b15  java.specification.name Java Platform API Specification  java.specification.vendor Oracle Corporation  java.specification.version 1.7  java.vendor Oracle Corporation  java.vendor.url http://java.oracle.com/  java.vendor.url.bug http://bugreport.sun.com/bugreport/  java.version 1.7.0_80  java.vm.info mixed mode  java.vm.name Java HotSpot(TM) 64-Bit Server VM  java.vm.specification.name Java Virtual Machine Specification  java.vm.specification.vendor Oracle Corporation  java.vm.specification.version 1.7  java.vm.vendor Oracle Corporation  java.vm.version 24.80-b11  jna.loaded true  jna.platform.library.path /usr/lib/x86_64-linux-gnu:/lib/x86_64-linux-gnu:/lib64:/usr/lib:/lib:/lib/i386-linux-gnu:/lib/i386-linux-gnu/i686/cmov:/usr/lib/i386-linux-gnu:/usr/lib/x86_64-linux-gnu/libfakeroot  jnidispatch.path /tmp/jna--1712433994/jna2257273014292489378.tmp  line.separator  mail.smtp.sendpartial true  mail.smtps.sendpartial true  os.arch amd64  os.name Linux  os.version 3.16.0-4-amd64  path.separator :  sessionTimeout 480  sun.arch.data.model 64  sun.boot.class.path 

[JIRA] (JENKINS-38380) timeout around input does not work with submitter

2016-11-09 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-38380  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: timeout around input does not work with submitter   
 

  
 
 
 
 

 
 I know, already fixed, get 2.5.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


Re: [JIRA] (JENKINS-39631) Declarative plugin adds extra step for failed step but doesn't mark it as error

2016-11-09 Thread Andrew Bayer
Last I looked, there was no way to do that - correct me if I'm wrong, Sam.

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


[JIRA] (JENKINS-39631) Declarative plugin adds extra step for failed step but doesn't mark it as error

2016-11-09 Thread vivek.pan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39631  
 
 
  Declarative plugin adds extra step for failed step but doesn't mark it as error   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 

  
 
 
 
 

 
 Running following code:{code:java}pipeline {agent label: ''stages {stage ('Build') {steps{  sh 'echo1 "Building"'}}stage ('Test') {steps{  sh 'echo "Test"'}}stage ('Deploy') {steps{  sh 'echo "Building"'}}}}{code}Only step in Build stage fails, declarative plugin adds extra print step to print there was failure however this step is not marked as error resulting in failure to mark the stage as error using StatusAndTiming.computeChunkStatus() api, which reports status of stage based on last step. That is if last sep was success, that means all is well. [~svanoort], this also shows up 'Build' stage as success in stage view plugin.Intent of declarative plugin is to report error that running that stage failed, this extra step it injects should have step.getError() return an error  object otherwise , that is FlowNode.getError().getError() returns a well known throwable to identify stage failed to run, StageExecutionFailure or something like that? Otherwise  it defeats the purpose  of marking stage as failure using StatusAndTiming . computeChunkStatus() API.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
  

[JIRA] (JENKINS-39631) Declarative plugin adds extra step for failed step but doesn't mark it as error

2016-11-09 Thread vivek.pan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39631  
 
 
  Declarative plugin adds extra step for failed step but doesn't mark it as error   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Andrew Bayer  
 
 
Components: 
 pipeline-model-definition-plugin  
 
 
Created: 
 2016/Nov/10 2:30 AM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Vivek Pandey  
 

  
 
 
 
 

 
 Running following code: 

 

pipeline {
agent label: ''
stages {
stage ('Build') {
steps{
  sh 'echo1 "Building"'
}
}
stage ('Test') {
steps{
  sh 'echo "Test"'
}
}
stage ('Deploy') {
steps{
  sh 'echo "Building"'
}
}
}
}
 

 Only step in Build stage fails, declarative plugin adds extra print step to print there was failure however this step is not marked as error resulting in failure to mark the stage as error using StatusAndTiming.computeChunkStatus() api, which reports status of stage based on last step. That is if last sep was success, that means all is well. Sam Van Oort, this also shows up 'Build' stage as success in stage view plugin. Intent of declarative plugin is to report error that running that stage failed, this extra step it injects should have step.getError() return an error object otherwise it defeats the purpose.  
 

  
 
 
 
 

 
 

[JIRA] (JENKINS-39629) ATH should run against latest version of Jenkins

2016-11-09 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39629  
 
 
  ATH should run against latest version of Jenkins   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2016/Nov/10 2:17 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 James Dumay  
 

  
 
 
 
 

 
 In Scope 
 
For every commit we should be running the ATH against the latest version of Jenkins weekly 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 


[JIRA] (JENKINS-39630) ATH should run against latest LTS versions of Jenkins

2016-11-09 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39630  
 
 
  ATH should run against latest LTS versions of Jenkins   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2016/Nov/10 2:17 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 James Dumay  
 

  
 
 
 
 

 
 In Scope 
 
For every commit we should be running the ATH against all supported LTS versions. 
 
2.7.4, 2.19.2, etc 
  
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
  

[JIRA] (JENKINS-39599) Pipeline graph not rendering for a simple Pipeline

2016-11-09 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay edited a comment on  JENKINS-39599  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline graph not rendering for a simple Pipeline   
 

  
 
 
 
 

 
 Looks like 2.29 had a major regression where stages wouldn't be displayed (JENKINS-39555)  which has been fixed in 2 . 30. [~noodlesnz] I highly recommend using the Jenkins LTS version as there is a lot of volatility with the weekly releases you are using.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39599) Pipeline graph not rendering for a simple Pipeline

2016-11-09 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Looks like 2.29 had a major regression where stages wouldn't be displayed (JENKINS-39555). Nick Le Mouton I highly recommend using the Jenkins LTS version as there is a lot of volatility with the weekly releases you are using.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-39599  
 
 
  Pipeline graph not rendering for a simple Pipeline   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-22587) JClouds does not honor security group against OpenStack

2016-11-09 Thread fr...@fritz-elfert.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Fritz Elfert closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fixed in v2.9  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-22587  
 
 
  JClouds does not honor security group against OpenStack   
 

  
 
 
 
 

 
Change By: 
 Fritz Elfert  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-22587) JClouds does not honor security group against OpenStack

2016-11-09 Thread fr...@fritz-elfert.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Fritz Elfert stopped work on  JENKINS-22587  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Fritz Elfert  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-25865) Jobs without label are never scheduled, so does most of matrix combinations

2016-11-09 Thread fr...@fritz-elfert.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Fritz Elfert closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fixed in v2.9  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-25865  
 
 
  Jobs without label are never scheduled, so does most of matrix combinations   
 

  
 
 
 
 

 
Change By: 
 Fritz Elfert  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-25865) Jobs without label are never scheduled, so does most of matrix combinations

2016-11-09 Thread fr...@fritz-elfert.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Fritz Elfert stopped work on  JENKINS-25865  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Fritz Elfert  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-26083) Jenkins jcloud pluging fails to get and assign floating ip on openstack

2016-11-09 Thread fr...@fritz-elfert.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Fritz Elfert closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fixed in v2.9  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-26083  
 
 
  Jenkins jcloud pluging fails to get and assign floating ip on openstack   
 

  
 
 
 
 

 
Change By: 
 Fritz Elfert  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-28815) Providing nodes by "Image name" always works as by "Image ID"

2016-11-09 Thread fr...@fritz-elfert.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Fritz Elfert closed an issue as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-28815  
 
 
  Providing nodes by "Image name" always works as by "Image ID"   
 

  
 
 
 
 

 
Change By: 
 Fritz Elfert  
 
 
Status: 
 Resolved Closed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39599) Pipeline graph not rendering for a simple Pipeline

2016-11-09 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-39599  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline graph not rendering for a simple Pipeline   
 

  
 
 
 
 

 
 Hmm, its weird that I can't even get 2.29 to work locally. When I install plugins, one or two fail to load and then the instance is busted.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-29136) NPE in jenkins.plugins.openstack.compute.JCloudsSlave.getRetentionTime(JCloudsSlave.java:109)

2016-11-09 Thread fr...@fritz-elfert.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Fritz Elfert closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fixed in v2.9  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-29136  
 
 
  NPE in jenkins.plugins.openstack.compute.JCloudsSlave.getRetentionTime(JCloudsSlave.java:109)   
 

  
 
 
 
 

 
Change By: 
 Fritz Elfert  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level

2016-11-09 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-38048  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Credentials dropdowns empty when configuring external libraries at the global level   
 

  
 
 
 
 

 
 No, I think it has passed enough of my tests to be released. It should be released before the end of the week.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38866) Multi branch with same commit not getting triggered as expected

2016-11-09 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-38866  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Multi branch with same commit not getting triggered as expected   
 

  
 
 
 
 

 
 As far as I can tell, that is a similar scenario as was described earlier. First branch is a subset of second branch. If the superset branch has been built, then the subset branch is assumed to also have been included in that superset. You could implement an alternative build chooser (refer to the Git Chooser Alternative Plugin for an example) that would choose by different rules than the current implementation.  You could add an empty commit on the subset branch so that it is no longer a subset.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39190) Failure to resolve a PagerDuty incident as a "Post-build Action" marks the Jenkins build itself as a failure

2016-11-09 Thread jenkin...@codeassassin.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jason Stangroome edited a comment on  JENKINS-39190  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failure to resolve a PagerDuty incident as a "Post-build Action" marks the Jenkins build itself as a failure   
 

  
 
 
 
 

 
 This has also been failing for me. The full error output is: {{{ ERROR: Build step failed with exceptionjava.lang.NullPointerException at org.jenkinsci.plugins.pagerduty.PagerDutyTrigger.resolveIncident(PagerDutyTrigger.java:225) at org.jenkinsci.plugins.pagerduty.PagerDutyTrigger.perform(PagerDutyTrigger.java:213) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723) at hudson.model.Build$BuildExecution.post2(Build.java:185) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:668) at hudson.model.Run.execute(Run.java:1763) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) }}} From the source code it seems that the expected object is not coming back from the PagerDuty API:https://github.com/jenkinsci/pagerduty-plugin/blob/pagerduty-0.2.4/src/main/java/org/jenkinsci/plugins/pagerduty/PagerDutyTrigger.java#L224-L225In my instance it was attempting to resolve an incident that had been triggered over a week prior and had probably been resolved externally.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins 

[JIRA] (JENKINS-39621) Pipeline job loop after polling always find changes

2016-11-09 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-39621  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline job loop after polling always find changes   
 

  
 
 
 
 

 
 Can you provide sufficient detail so that the problem can be duplicated in another Jenkins instance? For example, can you provide step by step instructions to configure a job on a newly installed Jenkins which will show the problem? Alternately, could you provide a job in a Docker instance which shows how you can duplicate the problem? Alternately, could you provide a job definition (with a Jenkinsfile) which shows the problem using a public git repository?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39190) Failure to resolve a PagerDuty incident as a "Post-build Action" marks the Jenkins build itself as a failure

2016-11-09 Thread jenkin...@codeassassin.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jason Stangroome edited a comment on  JENKINS-39190  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failure to resolve a PagerDuty incident as a "Post-build Action" marks the Jenkins build itself as a failure   
 

  
 
 
 
 

 
 This has also been failing for me. The full error output is:{{ { ERROR: Build step failed with exceptionjava.lang.NullPointerException at org.jenkinsci.plugins.pagerduty.PagerDutyTrigger.resolveIncident(PagerDutyTrigger.java:225) at org.jenkinsci.plugins.pagerduty.PagerDutyTrigger.perform(PagerDutyTrigger.java:213) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723) at hudson.model.Build$BuildExecution.post2(Build.java:185) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:668) at hudson.model.Run.execute(Run.java:1763) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)}} } From the source code it seems that the expected object is not coming back from the PagerDuty API:https://github.com/jenkinsci/pagerduty-plugin/blob/pagerduty-0.2.4/src/main/java/org/jenkinsci/plugins/pagerduty/PagerDutyTrigger.java#L224-L225In my instance it was attempting to resolve an incident that had been triggered over a week prior and had probably been resolved externally.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins 

[JIRA] (JENKINS-39190) Failure to resolve a PagerDuty incident as a "Post-build Action" marks the Jenkins build itself as a failure

2016-11-09 Thread jenkin...@codeassassin.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jason Stangroome edited a comment on  JENKINS-39190  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failure to resolve a PagerDuty incident as a "Post-build Action" marks the Jenkins build itself as a failure   
 

  
 
 
 
 

 
 This has also been failing for me. The full error output is:{{  ERROR: Build step failed with exceptionjava.lang.NullPointerException at org.jenkinsci.plugins.pagerduty.PagerDutyTrigger.resolveIncident(PagerDutyTrigger.java:225) at org.jenkinsci.plugins.pagerduty.PagerDutyTrigger.perform(PagerDutyTrigger.java:213) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723) at hudson.model.Build$BuildExecution.post2(Build.java:185) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:668) at hudson.model.Run.execute(Run.java:1763) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)  }}From the source code it seems that the expected object is not coming back from the PagerDuty API:https://github.com/jenkinsci/pagerduty-plugin/blob/pagerduty-0.2.4/src/main/java/org/jenkinsci/plugins/pagerduty/PagerDutyTrigger.java#L224-L225In my instance it was attempting to resolve an incident that had been triggered over a week prior and had probably been resolved externally.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins 

[JIRA] (JENKINS-38516) "Parsing cucumber.json" blocked by parallel job executions

2016-11-09 Thread jn...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Nord commented on  JENKINS-38516  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Parsing cucumber.json" blocked by parallel job executions   
 

  
 
 
 
 

 
 See this comment The display of results and failing count etc needs to be updated.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39190) Failure to resolve a PagerDuty incident as a "Post-build Action" marks the Jenkins build itself as a failure

2016-11-09 Thread jenkin...@codeassassin.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jason Stangroome commented on  JENKINS-39190  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failure to resolve a PagerDuty incident as a "Post-build Action" marks the Jenkins build itself as a failure   
 

  
 
 
 
 

 
 This has also been failing for me. The full error output is: {{ERROR: Build step failed with exception java.lang.NullPointerException at org.jenkinsci.plugins.pagerduty.PagerDutyTrigger.resolveIncident(PagerDutyTrigger.java:225) at org.jenkinsci.plugins.pagerduty.PagerDutyTrigger.perform(PagerDutyTrigger.java:213) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723) at hudson.model.Build$BuildExecution.post2(Build.java:185) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:668) at hudson.model.Run.execute(Run.java:1763) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)}} From the source code it seems that the expected object is not coming back from the PagerDuty API: https://github.com/jenkinsci/pagerduty-plugin/blob/pagerduty-0.2.4/src/main/java/org/jenkinsci/plugins/pagerduty/PagerDutyTrigger.java#L224-L225 In my instance it was attempting to resolve an incident that had been triggered over a week prior and had probably been resolved externally.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" 

[JIRA] (JENKINS-39621) Pipeline job loop after polling always find changes

2016-11-09 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39621  
 
 
  Pipeline job loop after polling always find changes   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Assignee: 
 Mark Waite  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39599) Pipeline graph not rendering for a simple Pipeline

2016-11-09 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-39599  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline graph not rendering for a simple Pipeline   
 

  
 
 
 
 

 
 Ill try with that exact version now.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39599) Pipeline graph not rendering for a simple Pipeline

2016-11-09 Thread n...@noodles.net.nz (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Le Mouton commented on  JENKINS-39599  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline graph not rendering for a simple Pipeline   
 

  
 
 
 
 

 
 I was running 2.29, I think 2.30 was released today  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39599) Pipeline graph not rendering for a simple Pipeline

2016-11-09 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-39599  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline graph not rendering for a simple Pipeline   
 

  
 
 
 
 

 
 Nick Le Mouton thats great news. What version of Jenkins were you running prior?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39599) Pipeline graph not rendering for a simple Pipeline

2016-11-09 Thread n...@noodles.net.nz (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Le Mouton commented on  JENKINS-39599  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline graph not rendering for a simple Pipeline   
 

  
 
 
 
 

 
 This seems to be resolved with Jenkins 2.30 and Favorites plugin 2.0.2. I'm not sure how/why, but the graph is showing for builds now.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39463) Integrate pipeline-model-definition 0.5

2016-11-09 Thread vivek.pan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey started work on  JENKINS-39463  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-34395) Support for building tags

2016-11-09 Thread ikop...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Koptiev commented on  JENKINS-34395  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support for building tags   
 

  
 
 
 
 

 
 +1 to this. Without tags support it's impossible to build projects that are using tags as release identifiers.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39599) Pipeline graph not rendering for a simple Pipeline

2016-11-09 Thread vivek.pan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey edited a comment on  JENKINS-39599  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline graph not rendering for a simple Pipeline   
 

  
 
 
 
 

 
 [~noodlesnz] Looked in to you HAR, GEThttp://jenkins.woolshed.com:8080/blue/rest/organizations/jenkins/pipelines/questioncom/branches/master/runs/6/nodes/ HTTP/1.1 indeed is giving empty nodes.Can you check  what version of  if  pipeline-model-definition plugin is installed  and what version it is ?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39599) Pipeline graph not rendering for a simple Pipeline

2016-11-09 Thread vivek.pan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey commented on  JENKINS-39599  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline graph not rendering for a simple Pipeline   
 

  
 
 
 
 

 
 Nick Le Mouton Looked in to you HAR, GEThttp://jenkins.woolshed.com:8080/blue/rest/organizations/jenkins/pipelines/questioncom/branches/master/runs/6/nodes/ HTTP/1.1 indeed is giving empty nodes. Can you check what version of pipeline-model-definition plugin is installed?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38913) DSL for choiceParam not working

2016-11-09 Thread afergu...@ea.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Ferguson commented on  JENKINS-38913  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: DSL for choiceParam not working   
 

  
 
 
 
 

 
 Added my vote, this bug is affecting my teams now as well.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39628) Handle skipped stages and parallels in the Pipeline Graph

2016-11-09 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-39628  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Handle skipped stages and parallels in the Pipeline Graph   
 

  
 
 
 
 

 
 Brody Maclean we've got to come up with a way of demonstrating this.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39628) Handle skipped stages and parallels in the Pipeline Graph

2016-11-09 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39628  
 
 
  Handle skipped stages and parallels in the Pipeline Graph   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Brody Maclean  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2016/Nov/10 12:18 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 James Dumay  
 

  
 
 
 
 

 
 The Pipeline team are adding the ability to "skip" stages in the Pipeline (JENKINS-37781) and we will need some way to show these on the pipeline graph.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA 

[JIRA] (JENKINS-39627) Alignment of cog is off on Result

2016-11-09 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39627  
 
 
  Alignment of cog is off on Result
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 blueocean #2 2016-11-10 10-44-50.png  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2016/Nov/09 11:46 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 James Dumay  
 

  
 
 
 
 

 
 Needs the standard amount of padding around the icon (I think wrapping it in a div is needed?)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 

[JIRA] (JENKINS-39609) Cache /blue/rest/classes calculation

2016-11-09 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-39609  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cache /blue/rest/classes calculation   
 

  
 
 
 
 

 
 Stephen Connolly pointed me to hudson.ExtensionListListener  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38150) Handle declarative pipeline preparatory steps and postBuild stage

2016-11-09 Thread vivek.pan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey started work on  JENKINS-38150  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38848) API to enumerate available credentials

2016-11-09 Thread vivek.pan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated  JENKINS-38848  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38848  
 
 
  API to enumerate available credentials   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-36887) Default JDL full page dialog (modal) style

2016-11-09 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay resolved as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36887  
 
 
  Default JDL full page dialog (modal) style   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Won't Fix  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-22853) SEVERE: Trying to unexport an object that's already unexported

2016-11-09 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-22853  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SEVERE: Trying to unexport an object that's already unexported   
 

  
 
 
 
 

 
 Code changed in jenkins User: Bertrand Roussel Path: client/pom.xml http://jenkins-ci.org/commit/swarm-plugin/8ad209aaafad5ec6256aa547702870da083ff6cd Log: Upgrade remoting API to 2.62 Version 2.62 contains a fix for the following bugs: 
 
https://issues.jenkins-ci.org/browse/JENKINS-22853 
https://issues.jenkins-ci.org/browse/JENKINS-23271 (possibly) 
 This occurs mostly with Java 8. The remoting version matches with Jenkins 2.18/2.19/2.19.1/2.19.2.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-23271) Intermittent Invalid Object ID in remoting module

2016-11-09 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-23271  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Intermittent Invalid Object ID in remoting module   
 

  
 
 
 
 

 
 Code changed in jenkins User: Bertrand Roussel Path: client/pom.xml http://jenkins-ci.org/commit/swarm-plugin/8ad209aaafad5ec6256aa547702870da083ff6cd Log: Upgrade remoting API to 2.62 Version 2.62 contains a fix for the following bugs: 
 
https://issues.jenkins-ci.org/browse/JENKINS-22853 
https://issues.jenkins-ci.org/browse/JENKINS-23271 (possibly) 
 This occurs mostly with Java 8. The remoting version matches with Jenkins 2.18/2.19/2.19.1/2.19.2.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-36887) Default JDL full page dialog (modal) style

2016-11-09 Thread bmacl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Brody Maclean commented on  JENKINS-36887  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Default JDL full page dialog (modal) style   
 

  
 
 
 
 

 
 Josh McDonald A little from column A, a little from column B.  I hadn't had the chance to look at the creation flow. Instead of a full screen modal we'll give the creation flow its own page. zeplin link https://zpl.io/1zxxa9 mockup
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-36887) Default JDL full page dialog (modal) style

2016-11-09 Thread bmacl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Brody Maclean updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36887  
 
 
  Default JDL full page dialog (modal) style   
 

  
 
 
 
 

 
Change By: 
 Brody Maclean  
 
 
Attachment: 
 Step 1.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38380) timeout around input does not work with submitter

2016-11-09 Thread digant.pa...@staples.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Digant Patel commented on  JENKINS-38380  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: timeout around input does not work with submitter   
 

  
 
 
 
 

 
 Hi, When I upgraded to Pipeline: Input Step 2.4, I am getting below error.  It seems Pipeline is not able to find "input" DSL keyword, I checked on Snippet Generator, it is missing there as well. java.lang.NoSuchMethodError: No such DSL method 'input' found among [archive, bat, build, catchError, checkout, deleteDir, dir, echo, emailext, emailextrecipients, error, fileExists, findFiles, getContext, isUnix, load, mail, milestone, node, parallel, properties, pwd, readFile, readManifest, readMavenPom, readProperties, readTrusted, retry, sh, sleep, splitTests, stage, stash, step, svn, timeout, timestamps, tool, touch, unarchive, unstash, unzip, waitUntil, withContext, withEnv, wrap, writeFile, writeMavenPom, ws, zip] at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:109) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:113) at groovy.lang.MetaClassImpl.invokeMethodOnGroovyObject(MetaClassImpl.java:1144) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1038) 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 groovy.lang.MetaClassImpl.invokeMethodOnGroovyObject(MetaClassImpl.java:1144) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1038) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:903) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:39) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:15) at WorkflowScript.run(WorkflowScript:140) at __cps.transform__(Native Method) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:55) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:106) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:79) at sun.reflect.GeneratedMethodAccessor448.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.CollectionLiteralBlock$ContinuationImpl.dispatch(CollectionLiteralBlock.java:55) at com.cloudbees.groovy.cps.impl.CollectionLiteralBlock$ContinuationImpl.item(CollectionLiteralBlock.java:45) at sun.reflect.GeneratedMethodAccessor466.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.CollectionLiteralBlock$ContinuationImpl.dispatch(CollectionLiteralBlock.java:55) at com.cloudbees.groovy.cps.impl.CollectionLiteralBlock$ContinuationImpl.item(CollectionLiteralBlock.java:45) at sun.reflect.GeneratedMethodAccessor466.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at 

[JIRA] (JENKINS-23299) Project building from tag builds at each polling interval

2016-11-09 Thread peter.jo...@autodesk.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Jones commented on  JENKINS-23299  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Project building from tag builds at each polling interval
 

  
 
 
 
 

 
 +1 I have same request and am hitting same limitation where I cannot trigger a build just from a tag change (non-annotated tag).  Will the use of annotated tags get around this limitation ?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39609) Cache /blue/rest/classes calculation

2016-11-09 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39609  
 
 
  Cache /blue/rest/classes calculation   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 tasman  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39609) Cache /blue/rest/classes calculation

2016-11-09 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39609  
 
 
  Cache /blue/rest/classes calculation   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 arctic  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-28417) NullPointerException in hudson.matrix.MatrixProject.createTransientActions

2016-11-09 Thread node...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Coggburn edited a comment on  JENKINS-28417  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: NullPointerException in hudson.matrix.MatrixProject.createTransientActions   
 

  
 
 
 
 

 
 Yeah, I'm getting NullPointerException all over my Jenkins instance now too but while createTransientActions is present in one of my traces I'm getting them all over without as well.{code:java}Nov 09, 2016 2:04:30 PM SEVERE hudson.model.Project createTransientActionsError loading trigger.java.lang.NullPointerException at hudson.model.Project.createTransientActions(Project.java:266) at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:756) at hudson.model.AbstractProject.onLoad(AbstractProject.java:340) at hudson.model.Project.onLoad(Project.java:98) at hudson.model.Items.load(Items.java:333) at hudson.model.ItemGroupMixIn.loadChildren(ItemGroupMixIn.java:116) at com.cloudbees.hudson.plugins.folder.AbstractFolder.onLoad(AbstractFolder.java:283) at com.cloudbees.hudson.plugins.folder.Folder.onLoad(Folder.java:104) at hudson.model.Items.load(Items.java:333) at hudson.model.ItemGroupMixIn.loadChildren(ItemGroupMixIn.java:116) at com.cloudbees.hudson.plugins.folder.AbstractFolder.onLoad(AbstractFolder.java:283) at com.cloudbees.hudson.plugins.folder.Folder.onLoad(Folder.java:104) at hudson.model.Items.load(Items.java:333) at jenkins.model.Jenkins$17.run(Jenkins.java:3053) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:1086) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) 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:745){code} but it's happening without mention of it as well:{code:java}Nov 09, 2016 2:07:00 PM WARNING hudson.triggers.Trigger$Cron doRunCron thread throw an exceptionjava.lang.NullPointerException at hudson.model.Descriptor.toMap(Descriptor.java:989) at hudson.util.DescribableList.toMap(DescribableList.java:151) at hudson.model.AbstractProject.getTriggers(AbstractProject.java:1617) at hudson.triggers.Trigger.checkTriggers(Trigger.java:270) at hudson.triggers.Trigger$Cron.doRun(Trigger.java:226) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:50) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) 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:745){code}  
 

  
 
 
 
 

 
 
 

 
 

[JIRA] (JENKINS-28417) NullPointerException in hudson.matrix.MatrixProject.createTransientActions

2016-11-09 Thread node...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Coggburn commented on  JENKINS-28417  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: NullPointerException in hudson.matrix.MatrixProject.createTransientActions   
 

  
 
 
 
 

 
 Yeah, I'm getting NullPointerException all over my Jenkins instance now too but while createTransientActions is present in one of my traces I'm getting them all over without as well. 

 

Nov 09, 2016 2:04:30 PM SEVERE hudson.model.Project createTransientActions
Error loading trigger.
java.lang.NullPointerException
	at hudson.model.Project.createTransientActions(Project.java:266)
	at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:756)
	at hudson.model.AbstractProject.onLoad(AbstractProject.java:340)
	at hudson.model.Project.onLoad(Project.java:98)
	at hudson.model.Items.load(Items.java:333)
	at hudson.model.ItemGroupMixIn.loadChildren(ItemGroupMixIn.java:116)
	at com.cloudbees.hudson.plugins.folder.AbstractFolder.onLoad(AbstractFolder.java:283)
	at com.cloudbees.hudson.plugins.folder.Folder.onLoad(Folder.java:104)
	at hudson.model.Items.load(Items.java:333)
	at hudson.model.ItemGroupMixIn.loadChildren(ItemGroupMixIn.java:116)
	at com.cloudbees.hudson.plugins.folder.AbstractFolder.onLoad(AbstractFolder.java:283)
	at com.cloudbees.hudson.plugins.folder.Folder.onLoad(Folder.java:104)
	at hudson.model.Items.load(Items.java:333)
	at jenkins.model.Jenkins$17.run(Jenkins.java:3053)
	at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
	at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)
	at jenkins.model.Jenkins$7.runTask(Jenkins.java:1086)
	at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)
	at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
	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:745)
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 

[JIRA] (JENKINS-39607) GC logs should be collected

2016-11-09 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-39607  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: GC logs should be collected   
 

  
 
 
 
 

 
 Code changed in jenkins User: Baptiste Mathus Path: src/main/java/com/cloudbees/jenkins/support/impl/GCLogs.java src/test/java/com/cloudbees/jenkins/support/impl/GCLogsTest.java http://jenkins-ci.org/commit/support-core-plugin/41fcbfd5dbe7ef0be5ae301425f7810ac197df83 Log: [FIX JENKINS-39607] Gather GC logs also with rotation enabled  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39607) GC logs should be collected

2016-11-09 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39607  
 
 
  GC logs should be collected   
 

  
 
 
 
 

 
Change By: 
 SCM/JIRA link daemon  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39607) GC logs should be collected

2016-11-09 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-39607  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: GC logs should be collected   
 

  
 
 
 
 

 
 Code changed in jenkins User: Steven Christou Path: pom.xml src/main/java/com/cloudbees/jenkins/support/impl/GCLogs.java src/test/java/com/cloudbees/jenkins/support/impl/GCLogsTest.java http://jenkins-ci.org/commit/support-core-plugin/c4cea8d7a574d06f79138d4b37c12cc8ee3ddc42 Log: Merge pull request #88 from batmat/gclogs [FIX JENKINS-39607] GC logs should be collected Compare: https://github.com/jenkinsci/support-core-plugin/compare/ab6ef422900d...c4cea8d7a574  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39587) Blue Ocean dashboard is showing no Pipelines

2016-11-09 Thread sheib...@bizstream.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sterling Heibeck edited a comment on  JENKINS-39587  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Blue Ocean dashboard is showing no Pipelines   
 

  
 
 
 
 

 
 I'm having the same issue consistently. Here's a screenshot of my developer tools that's showing a 500 error. Looks like it's an issue with the /blue/rest/  service not being available. Is there a configuration we need to get this working? !screenshot-1.png|thumbnail!Adding some more information after updating to 2.19.2. The /blue/rest/... actually return the following error:{code:java}java.io.IOException: Failed to write defaultParameterValue at org.kohsuke.stapler.export.Property.safeGetValue(Property.java:151) at org.kohsuke.stapler.export.Property.writeTo(Property.java:126) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:223) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:223) at org.kohsuke.stapler.export.Property.writeValue(Property.java:279) at org.kohsuke.stapler.export.Property.writeValue(Property.java:222) at org.kohsuke.stapler.export.Property.writeValue(Property.java:168) at org.kohsuke.stapler.export.Property.writeTo(Property.java:139) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227) at org.kohsuke.stapler.export.Property.writeTo(Property.java:135) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:223) at org.kohsuke.stapler.export.Property.writeValue(Property.java:279) at org.kohsuke.stapler.export.Property.writeValue(Property.java:222) at org.kohsuke.stapler.export.Property.writeValue(Property.java:168) at org.kohsuke.stapler.export.Property.writeTo(Property.java:139) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:223) at org.kohsuke.stapler.export.Model.writeTo(Model.java:198) at org.kohsuke.stapler.ResponseImpl.writeOne(ResponseImpl.java:285) at org.kohsuke.stapler.ResponseImpl.serveExposedBean(ResponseImpl.java:273) at hudson.model.Api.doJson(Api.java:211) at io.jenkins.blueocean.rest.pageable.PagedResponse$Processor$1.generateResponse(PagedResponse.java:63) at org.kohsuke.stapler.HttpResponseRenderer$Default.handleHttpResponse(HttpResponseRenderer.java:124) at org.kohsuke.stapler.HttpResponseRenderer$Default.generateResponse(HttpResponseRenderer.java:69) at org.kohsuke.stapler.Function.renderResponse(Function.java:119) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:102) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) 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.MetaClass$11.dispatch(MetaClass.java:380) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:686) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380) 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:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at 

[JIRA] (JENKINS-39587) Blue Ocean dashboard is showing no Pipelines

2016-11-09 Thread sheib...@bizstream.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sterling Heibeck commented on  JENKINS-39587  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Blue Ocean dashboard is showing no Pipelines   
 

  
 
 
 
 

 
 I'm having the same issue consistently. Here's a screenshot of my developer tools that's showing a 500 error. Looks like it's an issue with the /blue/rest/ service not being available. Is there a configuration we need to get this working? 
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-34262) Support for OAuth credentials

2016-11-09 Thread m...@davidham.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Ham commented on  JENKINS-34262  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support for OAuth credentials   
 

  
 
 
 
 

 
 At the least, could you update the landing page for this plugin to reflect the fact that it doesn't support OAuth? I worked on this for a long time before finding this ticket. As far as the Jenkins credentials page is concerned, OAuth credentials are the same as other username/password. Putting this in the README would help a lot. Thanks.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39587) Blue Ocean dashboard is showing no Pipelines

2016-11-09 Thread sheib...@bizstream.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sterling Heibeck updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39587  
 
 
  Blue Ocean dashboard is showing no Pipelines   
 

  
 
 
 
 

 
Change By: 
 Sterling Heibeck  
 
 
Attachment: 
 screenshot-1.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level

2016-11-09 Thread mko...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mike Kobit commented on  JENKINS-38048  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Credentials dropdowns empty when configuring external libraries at the global level   
 

  
 
 
 
 

 
 Mark Waite - do you need any assistance in testing/releasing this change?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-36887) Default JDL full page dialog (modal) style

2016-11-09 Thread jmcdon...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh McDonald commented on  JENKINS-36887  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Default JDL full page dialog (modal) style   
 

  
 
 
 
 

 
 Are these images out of date, or do we want this component to have a different header to the normal dialog, with the "close" button and (it appears) a different height? /ping Brody Maclean  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39626) Advanced PseudoTTY support is needed.

2016-11-09 Thread avekri...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Artyom Krivoy created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39626  
 
 
  Advanced PseudoTTY support is needed.   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 bap  
 
 
Components: 
 publish-over-ssh-plugin  
 
 
Created: 
 2016/Nov/09 9:07 PM  
 
 
Environment: 
 Debian Jessie, Jenkins 2.19.2, Publish Over SSH 1.14  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Artyom Krivoy  
 

  
 
 
 
 

 
 Despite "Exec in pty" option enabled, "Publish Over SSH" plugin doesn't send signals (INT, HUP) to processes envoked over ssh when Jenkins job interrupted manually or after timeout. Support of "ssh -t" option is needed.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

[JIRA] (JENKINS-39624) OPTIMIZATION: Pre-load user data on page config object

2016-11-09 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39624  
 
 
  OPTIMIZATION: Pre-load user data on page config object   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Summary: 
 OPTIMIZATION: Pre-load user data on page config object  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39625) OPTIMIZATION: Pre-load Run data on fresh load of the Run Details

2016-11-09 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39625  
 
 
  OPTIMIZATION: Pre-load Run data on fresh load of the Run Details   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2016/Nov/09 9:07 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 James Dumay  
 

  
 
 
 
 

 
 On a fresh load of the run details we want to avoid fetching the pipeline's run. In Scope 
 
This data is attached to the $.blueOceanConfig object 
When the page loads the data is injected into the store 
We never have to do a XHR when loading the run details 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
   

[JIRA] (JENKINS-28529) Git polling deletes files in workspace if "clean" and "ignore commits in path" are both enabled

2016-11-09 Thread timothy.br...@dematic.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tim Bradt commented on  JENKINS-28529  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git polling deletes files in workspace if "clean" and "ignore commits in path" are both enabled   
 

  
 
 
 
 

 
 We also had the same behavior if "Clean before checkout" and "Polling ignores commits with certain messages" are both enabled. Fortunately there is a workaround that will work for some. Unless the sequence is critical, switching to "Clean after checkout" eliminates the clean during polling.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38871) Exception caught evaluating condition: [org.jenkinsci.plugins.tokenmacro.MacroEvaluationException: Undefined parameter var in token ENV], action = [Fail the build]

2016-11-09 Thread slide.o....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl commented on  JENKINS-38871  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Exception caught evaluating condition: [org.jenkinsci.plugins.tokenmacro.MacroEvaluationException: Undefined parameter var in token ENV], action = "" the build]   
 

  
 
 
 
 

 
 Some plugins can be loaded dynamically and don't "need" a restart of Jenkins to load.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


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

2016-11-09 Thread tyrel.have...@microfocus.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tyrel Haveman edited a comment on  JENKINS-34564  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Give the ability to choose how the multibranch subprojects will be named.   
 

  
 
 
 
 

 
 Our workaround involves creating workspace paths based on the parent job and  simplieifed  simplified  branch name, with a limit on length, and using a small hash if the length is too long.For example, in the job {{example-core-pipeline}}, we might have a branch named {{feature/adding-something-important}} ends up going into the path {{D:\jenkins\workspace\example-core-pipeline\adding-somB5}}, and a branch named {{feature/goodbye-bugs}} goes to {{D:\jenkins\workspace\example-core-pipeline\goodbye-bugs}}.Trimming off the branch prefix ({{feature/}} in these cases) helps to shorten the path somewhat. We chose to limit the rest of the branch name when used as a folder name to 12 characters. If it is longer, it gets trimmed to 10 characters and the rest of the name is hashed to a simple 2-character hash.We consider it extremely unlikely that we would have two branches with similar enough names that the first 10 characters plus a 2-character hash will create a collision. On our very active 18-member development team we've been using this since just after I reported JENKINS-38706 with high success. Through many dozens of branches there have been no collisions, the paths are human-readable, and they are not too long for our builds.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to 

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

2016-11-09 Thread tyrel.have...@microfocus.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tyrel Haveman commented on  JENKINS-34564  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Give the ability to choose how the multibranch subprojects will be named.   
 

  
 
 
 
 

 
 Our workaround involves creating workspace paths based on the parent job and simplieifed branch name, with a limit on length, and using a small hash if the length is too long. For example, in the job example-core-pipeline, we might have a branch named feature/adding-something-important ends up going into the path D:\jenkins\workspace\example-core-pipeline\adding-somB5, and a branch named feature/goodbye-bugs goes to D:\jenkins\workspace\example-core-pipeline\goodbye-bugs. Trimming off the branch prefix (feature/ in these cases) helps to shorten the path somewhat. We chose to limit the rest of the branch name when used as a folder name to 12 characters. If it is longer, it gets trimmed to 10 characters and the rest of the name is hashed to a simple 2-character hash. We consider it extremely unlikely that we would have two branches with similar enough names that the first 10 characters plus a 2-character hash will create a collision. On our very active 18-member development team we've been using this since just after I reported JENKINS-38706 with high success. Through many dozens of branches there have been no collisions, the paths are human-readable, and they are not too long for our builds.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

  1   2   3   >