date:20160824

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-37666  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Proceeding step is sometimes erroneously expanded   
 

  
 
 
 
 

 
 Ben Walding yeah its slow due to the intersection of JENKINS-35788 and JENKINS-37024  
 

  
 
 
 
 

 
 
 

 
 
 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-33980) Document (List) Pipeline features of email-ext-plugin

2016-08-24 Thread jwarbur...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 John Warburton commented on  JENKINS-33980  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Document (List) Pipeline features of email-ext-plugin   
 

  
 
 
 
 

 
 Actual examples are still sparse. I found this excellent blog on feeding email-ext variables: https://jenkins.io/blog/2016/07/18/pipline-notifications/  
 

  
 
 
 
 

 
 
 

 
 
 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-37666) Proceeding step is sometimes erroneously expanded

2016-08-24 Thread bwald...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ben Walding edited a comment on  JENKINS-37666  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Proceeding step is sometimes erroneously expanded   
 

  
 
 
 
 

 
 The link in the report is gone now but I can reproduce this - https://ci.blueocean.io/blue/organizations/jenkins/scratch%2Ftst-log-opening/detail/tst-log-opening/1/pipeline/5 (I lied - the original link is fine - it's just uber slow for me) 1. Expand "Shell script" line 1 2. Close "Shell script" line 13. Expand "Shell script" line 2"Shell script" line 1 reopens.  
 

  
 
 
 
 

 
 
 

 
 
 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-37612) Cleanup pom(s) and prepare for beta

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37612  
 
 
  Cleanup pom(s) and prepare for beta   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 

  
 
 
 
 

 
 For the beta, we need to agree on a version naming convention, as well as the discription (artifact names remain unchanged). Current proposal after talking with Vivek: 1) All version strings should be changed from: {noformat}1.0-alpha-9-SNAPSHOT{noformat}to{noformat}1.0-b-9-SNAPSHOT{noformat}Maven will auto increment the last digit. 2) We should set  tag of https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-plugin/pom.xml#L14 to " BlueOcean :: UX Beta Blue Ocean beta "3) All other modules should have their  tag set to: Module :: BlueOcean :: Config... whateverIn theory by having this prefix, we make it clear people just install the BlueOcean :: UX component, and that it is beta. The rest are just libraries. Also if listed alphabetically in a search, the main UX plugin will show up first. In theory. How does this look [~jamesdumay]?Some additional cleanup to consider: *  The parent pom file refers to "blueocean-plugin" as a dependency, when it should be just "blueocean" (the aggregator): https://github.com/jenkinsci/blueocean-plugin/blob/master/pom.xml#L184 (I think)* Config plugin still calls itself Aggregator - perhaps a rename to config? https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-config/pom.xml  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-37658) Github-branch-source plugin should support git plugin extensions

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37658  
 
 
  Github-branch-source plugin should support git plugin extensions   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Summary: 
 Github-branch-source plugin should support   support  git plugin extensions  
 

  
 
 
 
 

 
 
 

 
 
 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-37658) Github-branch-source plugin should support support git plugin extensions

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37658  
 
 
  Github-branch-source plugin should support support git plugin extensions   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Summary: 
 Github-branch-source plugin should support  support git  client  plugin  extensions  
 

  
 
 
 
 

 
 
 

 
 
 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-37658) Github-branch-source plugin should support git plugin extensions

2016-08-24 Thread jonathan.wilfredo.fuen...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37658  
 
 
  Github-branch-source plugin should support git plugin extensions   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 

  
 
 
 
 

 
 Github branch source should support all the same extensions as the git client plugin ("Clean Before Checkout", "Clean After Checkout ", etc).   it currently does not provide a way to add them , while other pipeline plugins do support them .See "Additional Behaviors" in the attached screenshot.  
 

  
 
 
 
 

 
 
 

 
 
 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-33916) Property Strategy isn't displayed for Pipeline Multibranch jobs

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Fuentes edited a comment on  JENKINS-33916  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Property Strategy isn't displayed for Pipeline Multibranch jobs   
 

  
 
 
 
 

 
 I'd like to take a  show  shot  at fixing this bug. 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-33916) Property Strategy isn't displayed for Pipeline Multibranch jobs

2016-08-24 Thread jonathan.wilfredo.fuen...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Fuentes commented on  JENKINS-33916  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Property Strategy isn't displayed for Pipeline Multibranch jobs   
 

  
 
 
 
 

 
 I'd like to take a show at fixing this bug. 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-33916) Property Strategy isn't displayed for Pipeline Multibranch jobs

2016-08-24 Thread jonathan.wilfredo.fuen...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Fuentes assigned an issue to Jonathan Fuentes  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-33916  
 
 
  Property Strategy isn't displayed for Pipeline Multibranch jobs   
 

  
 
 
 
 

 
Change By: 
 Jonathan Fuentes  
 
 
Assignee: 
 Jonathan Fuentes  
 

  
 
 
 
 

 
 
 

 
 
 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-37612) Cleanup pom(s) and prepare for beta

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-37612  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cleanup pom(s) and prepare for beta   
 

  
 
 
 
 

 
 I'd like the plugin to be called "Blue Ocean beta" in the update center if possible  
 

  
 
 
 
 

 
 
 

 
 
 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-37612) Cleanup pom(s) and prepare for beta

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale edited a comment on  JENKINS-37612  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cleanup pom(s) and prepare for beta   
 

  
 
 
 
 

 
 [~jamesdumay] I am ok with that as long as it works the way we expect with versioning in the repositories (Vivek was going to look into it)  and the release 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-37666) Proceeding step is sometimes erroneously expanded

2016-08-24 Thread bwald...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ben Walding commented on  JENKINS-37666  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Proceeding step is sometimes erroneously expanded   
 

  
 
 
 
 

 
 The link in the report is gone now but I can reproduce this - https://ci.blueocean.io/blue/organizations/jenkins/scratch%2Ftst-log-opening/detail/tst-log-opening/1/pipeline/5 1. Expand "Shell script" line 1  2. Close "Shell script" line 1 3. Expand "Shell script" line 2 "Shell script" line 1 reopens.  
 

  
 
 
 
 

 
 
 

 
 
 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-37612) Cleanup pom(s) and prepare for beta

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-37612  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cleanup pom(s) and prepare for beta   
 

  
 
 
 
 

 
 James Dumay I am ok with that as long as it works the way we expect with versioning in the repositories (Vivek was going to look into it).   
 

  
 
 
 
 

 
 
 

 
 
 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-37612) Cleanup pom(s) and prepare for beta

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37612  
 
 
  Cleanup pom(s) and prepare for beta   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 

  
 
 
 
 

 
 For the beta, we need to agree on a version naming convention, as well as the discription (artifact names remain unchanged). Current proposal after talking with Vivek:  1) All version strings should be changed from: {noformat}  1.0-alpha-9-SNAPSHOT  {noformat}to{noformat}1.0-b-9-SNAPSHOT{noformat}Maven will auto increment the last digit. 2) We should set  tag of https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-plugin/pom.xml#L14 to "BlueOcean :: UX Beta"3) All other modules should have their  tag set to: Module :: BlueOcean :: Config... whateverIn theory by having this prefix, we make it clear people just install the BlueOcean :: UX component, and that it is beta. The rest are just libraries. How does this look [~jamesdumay]?Some additional cleanup to consider:  *  The parent pom file refers to "blueocean-plugin" as a dependency, when it should be just "blueocean" (the aggregator): https://github.com/jenkinsci/blueocean-plugin/blob/master/pom.xml#L184 (I think)* Config plugin still calls itself Aggregator - perhaps a rename to config? https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-config/pom.xml  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-37612) Cleanup pom(s) and prepare for beta

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37612  
 
 
  Cleanup pom(s) and prepare for beta   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 

  
 
 
 
 

 
 For the beta, we need to agree on a version naming convention, as well as the discription (artifact names remain unchanged). Current proposal after talking with Vivek: 1) All version strings should be changed from: {noformat}1.0-alpha-9-SNAPSHOT{noformat}to{noformat}1.0-b-9-SNAPSHOT{noformat}Maven will auto increment the last digit. 2) We should set  tag of https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-plugin/pom.xml#L14 to "BlueOcean :: UX Beta"3) All other modules should have their  tag set to: Module :: BlueOcean :: Config... whateverIn theory by having this prefix, we make it clear people just install the BlueOcean :: UX component, and that it is beta. The rest are just libraries.  Also if listed alphabetically in a search, the main UX plugin will show up first. In theory.  How does this look [~jamesdumay]?Some additional cleanup to consider: *  The parent pom file refers to "blueocean-plugin" as a dependency, when it should be just "blueocean" (the aggregator): https://github.com/jenkinsci/blueocean-plugin/blob/master/pom.xml#L184 (I think)* Config plugin still calls itself Aggregator - perhaps a rename to config? https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-config/pom.xml  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-37612) Cleanup pom(s) and prepare for beta

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37612  
 
 
  Cleanup pom(s) and prepare for beta   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 

  
 
 
 
 

 
 1 For the beta, we need to agree on a version naming convention, as well as the discription (artifact names remain unchanged ) . Current proposal after talking with Vivek: *  The parent pom file refers to "blueocean-plugin" as a dependency, when it should be just "blueocean" (the aggregator): https://github.com/jenkinsci/blueocean-plugin/blob/master/pom.xml#L184 (I think) 2) *  Config plugin still calls itself Aggregator - perhaps a rename to config? https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-config/pom.xml   
 

  
 
 
 
 

 
 
 

 
 
 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-37612) Cleanup pom(s) and prepare for beta

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-37612  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cleanup pom(s) and prepare for beta   
 

  
 
 
 
 

 
 Vivek Pandey I'd like to use the naming scheme 1.0.0-bX where X increments weekly   
 

  
 
 
 
 

 
 
 

 
 
 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.

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-34564  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
 Jesse Glick ahh sorry for misattributing that to you!  
 

  
 
 
 
 

 
 
 

 
 
 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-37602) Branches tab does not showed queued runs

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-37602  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Branches tab does not showed queued runs   
 

  
 
 
 
 

 
 Tom FENNELLY if you've got more bandwidth would you be comfortable assigning this one to yourself?  
 

  
 
 
 
 

 
 
 

 
 
 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-37670) RemoteClassLoader: ClassFormatError c.f. UnsupportedClassVersionError

2016-08-24 Thread thomas.mpp.mas...@gmail.com (JIRA)

Title: Message Title

Thomas Maslen created an issue

Jenkins / JENKINS-37670

RemoteClassLoader: ClassFormatError c.f. UnsupportedClassVersionError

Issue Type:
Bug

Assignee:
Unassigned

Components:
remoting

Created:
2016/Aug/25 2:06 AM

Priority:
Minor

Reporter:
Thomas Maslen

When the RemoteClassLoader encounters a Java class file whose version is too high, it ends up throwing ClassFormatError. This comes as a nasty surprise to software packages that expect to receive (and trap, and recover from) UnsupportedClassVersionError. In particular, this breaks the JGit functionality in the git-client-plugin (versions 1.19.1 to 1.19.7) if it executes on a slave that's running JDK 1.6. (Yes, I realize that JDK 1.6 is ancient history so this particular example may be moot now, but the same general problem may reappear in the long march from 1.7 to 1.8 or 1.8 to 1.9). jgit-client-plugin 1.9.0 and below don't experience this problem because they didn't include the dependency that triggers this, org.eclipse.jgit:org.eclipse.jgit.java7. That dependency was added in git-client-plugin 1.19.1 with this checkin comment: JENKINS-30371 Distribute JGit java7 jar to allow JGit symlink support JGit symlink support is optional with JGit 3.7.1. It requires a copy of the JGit java7 jar, a Java 7 VM, and a file system which supports symbolic links. Including the jar file in a Java 6 environment is safe because the JGit code won't load the additional jar when running on Java 6. That last sentence is probably true in an environment where the RemoteClassLoader isn't involved (e.g. on master?) but definitely not on JDK 1.6 slaves. There's nothing that the git-client-plugin can (or should) do to fix this; the code that's expecting to receive and handle UnsupportedClassVersionError is in org.eclipse.jgit:org.eclipse.jgit. (I should probably say "was in" because newer versions of org.eclipse.jgit have made JDK 1.7 required rather than optional). My (quite likely clueless) 0.02 re the code in

[JIRA] (JENKINS-36660) Acceptance tests for nested project and funky branch name regressions

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-36660  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Acceptance tests for nested project and funky branch name regressions   
 

  
 
 
 
 

 
 IBERIAN SAMURAI!  
 

  
 
 
 
 

 
 
 

 
 
 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-37669) Upgrade Automatically fails

2016-08-24 Thread andrew.paul.g...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Gray created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37669  
 
 
  Upgrade Automatically fails   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2016/Aug/25 1:28 AM  
 
 
Environment: 
 Windows 2012, Jenkins 2.18  
 
 
Labels: 
 jenkins regression  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Andrew Gray  
 

  
 
 
 
 

 
 I am continually getting this stacktrace trying to upgrade from 2.18 to 2.19 hudson.util.IOException2: Failed to download from http://updates.jenkins-ci.org/download/war/2.19/jenkins.war at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1169) at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1666) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1640) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) at java.lang.Thread.run(Unknown Source) Caused by: java.net.SocketTimeoutException: Read timed out at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection$10.run(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection$10.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at sun.net.www.protocol.http.HttpURLConnection.getChainedException(Unknown Source) at

[JIRA] (JENKINS-35367) EMail-Ext Extended Pipeline Support - Templates

2016-08-24 Thread da...@vanlaatum.id.au (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 David van Laatum commented on  JENKINS-35367  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: EMail-Ext Extended Pipeline Support - Templates   
 

  
 
 
 
 

 
 No I don't you can send emails using this just can't use the template functionality. ie you have to build the contents of the email in the groovy script  
 

  
 
 
 
 

 
 
 

 
 
 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-35796) Developer can stop the run of an executing pipeline

Title: Message Title

Michael Neale commented on JENKINS-35796

Re: Developer can stop the run of an executing pipeline

Cliff Meyers Some answers: Permissions: yes another ticket. I believe it would be predicated on JWT (there is a backend api for it, so it can be done at some point). On blocking call: yes many cases it would be fast, but pipeline is infamous for taking it's sweet time, hence hte timeout, which make it to a hard stop (ie 10 seconds to do it politely, then kill it). Of course, it isn't guaranteed to kill it, so in the case where you have used blocking with a timeout, and it doesn't actually stop, the stop button can rever to the enabled state and let them try again (there is nothing else we can do other than that). so yes, like you said. Most of the time it will be good, but some steps take time to kill. I think the approach you have suggested is good, and if people don't like it, we review in the future.

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-36980) intermittent NPE/500 errors after leaving blue ocean open for a while

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated  JENKINS-36980  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36980  
 
 
  intermittent NPE/500 errors after leaving blue ocean open for a while
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Status: 
 In Review 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-37320) SAML SSO plugin change - Enable Unified Jenkins profile config for SSO

2016-08-24 Thread anita_dong...@intuit.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Anita Dongare edited a comment on  JENKINS-37320  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SAML SSO plugin change - Enable Unified Jenkins profile config for SSO
 

  
 
 
 
 

 
 [~chengas123] Hi Ben,  When will the next version of plugin be released?  Can we get this change in for the next scheduled release? This is required for our Jenkins production roll out.   
 

  
 
 
 
 

 
 
 

 
 
 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-37320) SAML SSO plugin change - Enable Unified Jenkins profile config for SSO

2016-08-24 Thread anita_dong...@intuit.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Anita Dongare commented on  JENKINS-37320  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SAML SSO plugin change - Enable Unified Jenkins profile config for SSO
 

  
 
 
 
 

 
 Ben McCann Hi Ben, Can we get this change in for the next scheduled release? This is required for our Jenkins production roll out.   
 

  
 
 
 
 

 
 
 

 
 
 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-37612) Cleanup pom(s) and prepare for beta

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37612  
 
 
  Cleanup pom(s) and prepare for beta   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 
 
Priority: 
 Minor Major  
 

  
 
 
 
 

 
 
 

 
 
 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-37612) Cleanup pom(s) and prepare for beta

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37612  
 
 
  Cleanup pom(s) and prepare for beta   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 
 
Summary: 
 Cleanup pom(s)  and prepare for beta  
 

  
 
 
 
 

 
 
 

 
 
 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-37668) Parent job wait for the downstream job to finish. although the downstream job is Finished.

2016-08-24 Thread manoj.thak...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Manoj Thakkar commented on  JENKINS-37668  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Parent job wait for the downstream job to finish. although the downstream job is Finished.   
 

  
 
 
 
 

 
 Andrew Bayer You know this scenario for sure :0). Please see if you can help us fix it or point us to the right direction and we can try to patch it ourself
 

  
 
 
 
 

 
 
 

 
 
 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-37668) Parent job wait for the downstream job to finish. although the downstream job is Finished.

2016-08-24 Thread manoj.thak...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Manoj Thakkar created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37668  
 
 
  Parent job wait for the downstream job to finish. although the downstream job is Finished.   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 huybrechts  
 
 
Components: 
 parameterized-trigger-plugin  
 
 
Created: 
 2016/Aug/24 11:45 PM  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Manoj Thakkar  
 

  
 
 
 
 

 
 We start a job which has 5-6 downstream jobs using the parameterized plugin( the parent job is blocked on downstream jobs). Every now and then the parent job keep waiting for the downstream job result even though the downstream job has finished successfully. Example Scenario Project A started B,C & D and is waiting for it to finish Project A1,A2A10 also triggers B,C,D and is waiting for it to finish.  One of the Projects say A5 will be waiting forever for say a project C#10 which has already finished.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-37323) Ensure that Pipeline Graph can handle stage blocks

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey commented on  JENKINS-37323  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ensure that Pipeline Graph can handle stage blocks   
 

  
 
 
 
 

 
 Opened https://issues.jenkins-ci.org/browse/JENKINS-37667  
 

  
 
 
 
 

 
 
 

 
 
 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-37667) Use ForkScanner to build DAG

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37667  
 
 
  Use ForkScanner to build DAG   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Vivek Pandey  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2016/Aug/24 11:38 PM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Vivek Pandey  
 

  
 
 
 
 

 
 BlueOcean /nodes and /steps API use FlowGraphWalker to build it's DAG. This is not very efficient. It should be replaced with ForkScanner (WIP, soon to be released), it brings in optimizations (SAX style parser etc.).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by

[JIRA] (JENKINS-37531) Uncaught TypeError: Cannot read property 'getNativeNode' of null on Changes/Tests/Artifacts tabs

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay resolved as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Lets close this out then   
 

  
 
 
 
 

 
 Jenkins /  JENKINS-37531  
 
 
  Uncaught TypeError: Cannot read property 'getNativeNode' of null on Changes/Tests/Artifacts tabs   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Status: 
 In Progress Resolved  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 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

[JIRA] (JENKINS-37532) Uncaught TypeError: Cannot read property 'componentWillReceiveProps' of null

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay resolved as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Lets close this out then   
 

  
 
 
 
 

 
 Jenkins /  JENKINS-37532  
 
 
  Uncaught TypeError: Cannot read property 'componentWillReceiveProps' of null   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Status: 
 In Progress Resolved  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 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-37666) Proceeding step is sometimes erroneously expanded

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37666  
 
 
  Proceeding step is sometimes erroneously expanded   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 1.0-beta-1  
 

  
 
 
 
 

 
 
 

 
 
 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-37666) Proceeding step is sometimes erroneously expanded

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37666  
 
 
  Proceeding step is sometimes erroneously expanded   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 

  
 
 
 
 

 
 *Steps to reproduce*# Open [this result|https://ci.blueocean.io/blue/organizations/jenkins/blueocean/detail/story%2FJENKINS-35783/33/pipeline] in Chrome# Scroll to the top and close the failing step# Open the  successful  shell script immediately above  it  the failing step # BUG: Both the successful step and the failing step will open at the same time. Only the step we asked to expand should open.It would be good to add a regression test for 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-37323) Ensure that Pipeline Graph can handle stage blocks

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey commented on  JENKINS-37323  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ensure that Pipeline Graph can handle stage blocks   
 

  
 
 
 
 

 
 I have some more update. Instead of making one big change to support both block scoped stage as well as replace FlowGraphWalker by Fork scanner - it brings optimization to scanning process. Later is considerable amount of work as it requires complete re-write. Basically this ticket only adds support for block scoped stages. task/JENKINS-37323 is ready with this support as soon as pipeline-stage-step gets released.  I am going to open another ticket to replace FlowGraphWalker by ForkedScanner.   
 

  
 
 
 
 

 
 
 

 
 
 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-37666) Proceeding step is sometimes erroneously expanded

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37666  
 
 
  Proceeding step is sometimes erroneously expanded   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Thorsten Scherler  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2016/Aug/24 11:33 PM  
 
 
Environment: 
 Google Chrome  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 James Dumay  
 

  
 
 
 
 

 
 Steps to reproduce 
 
Open this result in Chrome 
Scroll to the top and close the failing step 
Open the shell script immediately above it 
BUG: Both the successful step and the failing step will open at the same time. Only the step we asked to expand should open. 
 It would be good to add a regression test for this.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-10191) JDK selection is hidden even when a JDK is configured

2016-08-24 Thread db...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-10191  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JDK selection is hidden even when a JDK is configured
 

  
 
 
 
 

 
 How many JDKs are configured globally?  
 

  
 
 
 
 

 
 
 

 
 
 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-36235) Add optional 'timeout' parameter to 'input' step

2016-08-24 Thread jason.mil...@readytalk.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jason Miller commented on  JENKINS-36235  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add optional 'timeout' parameter to 'input' step   
 

  
 
 
 
 

 
 Joost: Does this still work for you? I'm unable to get it working on my instance, using 2.7.2 and the latest pipeline plugins: 

 

timeout(5) {
  input "waiting..."
}
 

 The timeout block doesn't seem to work - it just hangs on the input step indefinitely until it's either approved or aborted, just as if it weren't in a timeout block at all. If I remove the input step, the timeout works as expected, so it seems like timeout isn't being allowed to abort the input step correctly.  
 

  
 
 
 
 

 
 
 

 
 
 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-36748) Jobs with syntactically incorrect config missing the cron spec for a trigger produces NullPointerException

2016-08-24 Thread scm_issue_l...@java.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-36748  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jobs with syntactically incorrect config missing the cron spec for a trigger produces NullPointerException   
 

  
 
 
 
 

 
 Code changed in jenkins User: Felix Belzunce Arcos Path: core/src/main/java/hudson/triggers/Trigger.java test/src/test/java/hudson/triggers/TriggerTest.java http://jenkins-ci.org/commit/jenkins/4278804582b34f123414bde521bd91b009d8e353 Log: JENKINS-36748 Do not process null specs in triggers (#2482) 
 
JENKINS-36748 Add a test case and not process null specs 
 
 
JENKINS-36748 Correct license and add a minor comment 
 
 
JENKINS-36748 Add a Waning logger when spec is null 
  
 

  
 
 
 
 

 
 
 

 
 
 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-37598) Inaccurate aggregation of multiple xmls containing case information about the same testsuite

2016-08-24 Thread k...@rxd.hu (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Zoltán Haindrich commented on  JENKINS-37598  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Inaccurate aggregation of multiple xmls containing case information about the same testsuite   
 

  
 
 
 
 

 
 I'm not sure which stats should I leave this ticket in...i've looked into a few...and haven't seen any in IN REVIEW I think the code in the pull request should take care of the issue   
 

  
 
 
 
 

 
 
 

 
 
 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-37525) parameterized job with string having default 0 breaks groovy postbuild reading property

2016-08-24 Thread de...@ikedam.jp (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 ikedam assigned an issue to Zach Auclair  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Cannot reproduce in my environment. Please describe more exact steps to reproduce the problem. Anyway, you use a so old version of groovy-postbuild, and I don't support old versions. I want you also to see whether the problem is reproduced even with the latest groovy-postbuild. My environment is Windows 10 64bits, Java 1.8.0_92, Jenkins 1.625.3, groovy-postbuild 1.8. Steps I tested: 
 
Install Jenkins 1.625.3. 
Install groovy-postbuild 1.8. 
Create a new freestyle project named "test". 
Check "This build is parameterized" 
Add a String Parameter: 
 
Name: some-param 
Default Value: 0 
  
Add "Groovy Postbuild" to "Post-build Actions" 
Add the following code: 

 

def varName = "some-param";
def tempVal = manager.build.buildVariables.get(varName )
if(tempVal == null || tempVal.equals("")){
   manager.listener.logger.println("${varName} not found: '${tempVal}'")
}
 

 
Run a build with default values. 
 Result: 
 
The log output is: 

 
Started by user anonymous
Building in workspace C:\Users\ikedam\.jenkins\jobs\test\workspace
Finished: SUCCESS
 

 
  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-37525  
 
 
  parameterized job with string having default 0 breaks groovy postbuild reading property   
 

  
 
 
 
 

 
Change By: 
 ikedam

[JIRA] (JENKINS-37098) file leak with slave.log

2016-08-24 Thread jn...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Nord commented on  JENKINS-37098  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: file leak with slave.log   
 

  
 
 
 
 

 
 Nicolas De Loof Is this closed - or is there related work on this to prevent the attempted re-open by something (or does that deserve a separate JIRA?)  
 

  
 
 
 
 

 
 
 

 
 
 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-37664) Endless loop in LargeText.BufferSession.skip

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-37664  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37664  
 
 
  Endless loop in LargeText.BufferSession.skip   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
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-37664) Endless loop in LargeText.BufferSession.skip

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-37664  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Endless loop in LargeText.BufferSession.skip   
 

  
 
 
 
 

 
 Do not know exactly why this is happening, but can at least make it not be as much of a problem.  
 

  
 
 
 
 

 
 
 

 
 
 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-31605) Plugin manager allows uninstalling bundled plugins

2016-08-24 Thread jn...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Nord commented on  JENKINS-31605  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Plugin manager allows uninstalling bundled plugins   
 

  
 
 
 
 

 
 I beleive this is now working in 2.x as there are no bundled plugins in OSS - only custom derivatives...  
 

  
 
 
 
 

 
 
 

 
 
 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-37315) Make JNLP3 opt-in for all

2016-08-24 Thread o.v.nenas...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-37315  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Make JNLP3 opt-in for all   
 

  
 
 
 
 

 
 It has been backported to the 2.7.3 branch. The fix is available in the release candidate. https://github.com/jenkinsci/jenkins/commit/97c1cbd753d963e947c085c040667b1b98e06ba1  
 

  
 
 
 
 

 
 
 

 
 
 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-37315) Make JNLP3 opt-in for all

2016-08-24 Thread o.v.nenas...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37315  
 
 
  Make JNLP3 opt-in for all   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Labels: 
 lts 2.7.3 - candidate 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-37664) Endless loop in LargeText.BufferSession.skip

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick started work on  JENKINS-37664  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
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-37664) Endless loop in LargeText.BufferSession.skip

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37664  
 
 
  Endless loop in LargeText.BufferSession.skip   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Jesse Glick  
 
 
Components: 
 core, workflow-plugin  
 
 
Created: 
 2016/Aug/24 10:44 PM  
 
 
Environment: 
 1.642.x  
 
 
Labels: 
 stapler  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Jesse Glick  
 

  
 
 
 
 

 
 A Pipeline build was observed hanging waiting for a lock, which was held by 

 

"jenkins.util.Timer [#1]" id=... state=RUNNABLE cpu=99%
at org.kohsuke.stapler.framework.io.LargeText$BufferSession.skip(LargeText.java:532)
at org.kohsuke.stapler.framework.io.LargeText.writeLogTo(LargeText.java:211)
at hudson.console.AnnotatedLargeText.writeRawLogTo(AnnotatedLargeText.java:162)
at org.jenkinsci.plugins.workflow.job.WorkflowRun.copyLogs(WorkflowRun.java:370)
at org.jenkinsci.plugins.workflow.job.WorkflowRun.access$600(WorkflowRun.java:111)
at org.jenkinsci.plugins.workflow.job.WorkflowRun$3.run(WorkflowRun.java:266)
at ...
 

 Seems that this infinite loop occurs reproducibly when a call to writeLogTo is made with a start position greater than the size of the log file.

[JIRA] (JENKINS-29023) Propagate results from subjobs from MultiJob plugin

2016-08-24 Thread co...@karfau.de (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christian Bewernitz commented on  JENKINS-29023  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Propagate results from subjobs from MultiJob plugin   
 

  
 
 
 
 

 
 Well, very interesting because I'm using it on one installation for abut a week now and couldn't see that happen. Since which version is this supported? Is some kind of setting/ configuration combination required for this to work? E.g. does this only happen if no case was found in the "parent" job? How to track what goes wrong if this is not working as you describe? (I'm going to set up a minimal example to verify that, so it would be helpful to know where to look.) Thx  Christian  
 

  
 
 
 
 

 
 
 

 
 
 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-37663) Build is not marked as UNSTABLE even though failures are found

2016-08-24 Thread m...@joshma.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Joshua Ma created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37663  
 
 
  Build is not marked as UNSTABLE even though failures are found   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 junit-plugin  
 
 
Created: 
 2016/Aug/24 10:03 PM  
 
 
Environment: 
 Jenkins 2.19  junit 1.18  
 
 
Labels: 
 plugins  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Joshua Ma  
 

  
 
 
 
 

 
 I'm using JUnitResultsArchive to record test results, and I'm seeing a weird bug where there are failures reported but the build is not marked unstable. This is via Jenkins pipeline, and immediately after the step, I'm echoing the build result: 

 

step([$class: 'JUnitResultArchiver', testResults: 'build/xunit.xml'])
echo ">>> BUILD RESULT ${currentBuild.result}"
 

 I can confirm that a test failed in that step, and the result printed is ">>> BUILD RESULT null" This doesn't always happen - in some other runs, the result is UNSTABLE as expected.

[JIRA] (JENKINS-37006) Improved importing/requiring of modules across bundles

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-37006  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Improved importing/requiring of modules across bundles   
 

  
 
 
 
 

 
 Tom FENNELLY nice one BTW   
 

  
 
 
 
 

 
 
 

 
 
 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-34563) Github Organization Folder Plugin does not discover new repositories after first Re-scan Organization although Webhook is working fine

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-34563  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Github Organization Folder Plugin does not discover new repositories after first Re-scan Organization although Webhook is working fine   
 

  
 
 
 
 

 
 The implementation of JENKINS-32155 probably needs to be redone anyway, in github-branch-source using an addition TBD to scm-api. Should be deleted from github-organization-folder.  
 

  
 
 
 
 

 
 
 

 
 
 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-10191) JDK selection is hidden even when a JDK is configured

2016-08-24 Thread signu...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Matthew Sexton commented on  JENKINS-10191  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JDK selection is hidden even when a JDK is configured
 

  
 
 
 
 

 
 Correct, however I am confirming that the JDK selection from a maven job is not visible even though it is specified in the job's configuration. That was a side-effect I noticed at the same time (may or may not be related).  
 

  
 
 
 
 

 
 
 

 
 
 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-10191) JDK selection is hidden even when a JDK is configured

2016-08-24 Thread db...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-10191  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JDK selection is hidden even when a JDK is configured
 

  
 
 
 
 

 
 

of my JDK tool installations were gone, and that the UI selection for the JDK for all maven jobs was no longer visible
 Moved to /configureTools  
 

  
 
 
 
 

 
 
 

 
 
 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-37608) Configurability of GitHub Branch Source to use Scan User with only Read permission

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-37608  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Configurability of GitHub Branch Source to use Scan User with only Read permission   
 

  
 
 
 
 

 
 So this would be quite problematic. If the user associated with the scan access token has no permissions to check whether other users would be able to push to repositories, then to be on the safe side it would need to assume that all users are untrusted, which would prevent any forked pull request from modifying Jenkinsfile, even if it is coming from an authorized user.  
 

  
 
 
 
 

 
 
 

 
 
 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-37608) Configurability of GitHub Branch Source to use Scan User with only Read permission

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-37608  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Configurability of GitHub Branch Source to use Scan User with only Read permission   
 

  
 
 
 
 

 
 Status notifications is a separate permission, repo:status. You should not need write access AFAIK. Checking for trusted PRs is another matter. As noted in JENKINS-36240, the current implementation is just a heuristic, since GitHub offers no official API for this. But whatever it offers, it is unlikely to work with permissions lower than organizational administrator.  
 

  
 
 
 
 

 
 
 

 
 
 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-37662) Pass Jenkins System logs to logstash

2016-08-24 Thread edwin....@rbc.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Edwin Lum created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37662  
 
 
  Pass Jenkins System logs to logstash   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Edwin Lum  
 
 
Components: 
 logstash-plugin  
 
 
Created: 
 2016/Aug/24 9:29 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Edwin Lum  
 

  
 
 
 
 

 
 It appears this plugin forwards the console logs to a variety of outputs. Is there a functionality to forward the system log instead?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-37538) classloading issue with xerces lib

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-37538  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: classloading issue with xerces lib   
 

  
 
 
 
 

 
 In principle SubversionChangeLogParser etc. could also resolve this by setting the desired context loader explicitly, but it is hard to know how many more such cases there might be. Anyway in this case it is not clear the Subversion plugin would even know what to use, since the design of JAXP is such that it is just asking for an XML parser from the system and hoping for the best.  
 

  
 
 
 
 

 
 
 

 
 
 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-37538) classloading issue with xerces lib

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37538  
 
 
  classloading issue with xerces lib   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Component/s: 
 workflow-plugin  
 
 
Component/s: 
 subversion-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-37538) classloading issue with xerces lib

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37538  
 
 
  classloading issue with xerces lib   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Labels: 
 classloading-hell regression  
 

  
 
 
 
 

 
 
 

 
 
 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-37538) classloading issue with xerces lib

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-37538  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: classloading issue with xerces lib   
 

  
 
 
 
 

 
 Patch to workflow-cps might resolve 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-37538) classloading issue with xerces lib

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick started work on  JENKINS-37538  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
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-37538) classloading issue with xerces lib

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-37538  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37538  
 
 
  classloading issue with xerces lib   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
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-37653) Git fetch fails. Returns "Reference directory conflict: refs/heads/" with status code 128

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Nauda commented on  JENKINS-37653  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git fetch fails. Returns "Reference directory conflict: refs/heads/" with status code 128
 

  
 
 
 
 

 
 I asked this question on the git mailing list. Mark Waite I agree that this looks like it's not a Jenkins bug, but the article you linked does not apply to our use case (a filesystem mounted to a single client over a reliable network). As EFS adoption grows, I expect this use case to become more popular, as it seems like a nice option to manage the growth of the /var/lib/jenkins filesystem.  
 

  
 
 
 
 

 
 
 

 
 
 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-35796) Developer can stop the run of an executing pipeline

Title: Message Title


 
 
 
 

 
 
 

 
   
 Cliff Meyers commented on  JENKINS-35796  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Developer can stop the run of an executing pipeline   
 

  
 
 
 
 

 
 Michael Neale just tested the blocking approach now, in most cases it's very fast (under a second) but I did see a run against a multibranch (JDL) that took about 10s. So I think the question still stands but it's probably more of an edge case.  
 

  
 
 
 
 

 
 
 

 
 
 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-37653) Git fetch fails. Returns "Reference directory conflict: refs/heads/" with status code 128

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37653  
 
 
  Git fetch fails. Returns "Reference directory conflict: refs/heads/" with status code 128
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 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-37653) Git fetch fails. Returns "Reference directory conflict: refs/heads/" with status code 128

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-37653  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git fetch fails. Returns "Reference directory conflict: refs/heads/" with status code 128
 

  
 
 
 
 

 
 There is a wandisco article which describes reasons why a git directory should not be used over an NFS mount. There are also references to poor performance with git repositories hosted over NFS.  
 

  
 
 
 
 

 
 
 

 
 
 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-36054) Reload page after hibernate

2016-08-24 Thread tom.fenne...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom FENNELLY updated  JENKINS-36054  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36054  
 
 
  Reload page after hibernate   
 

  
 
 
 
 

 
Change By: 
 Tom FENNELLY  
 
 
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-36980) intermittent NPE/500 errors after leaving blue ocean open for a while

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated  JENKINS-36980  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36980  
 
 
  intermittent NPE/500 errors after leaving blue ocean open for a while
 

  
 
 
 
 

 
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-37538) classloading issue with xerces lib

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-37538  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: classloading issue with xerces lib   
 

  
 
 
 
 

 
 I suspect the root cause is a mismatch of defining vs. initiating class loader as described in JDK-6865375.  
 

  
 
 
 
 

 
 
 

 
 
 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-35796) Developer can stop the run of an executing pipeline

Title: Message Title


 
 
 
 

 
 
 

 
   
 Cliff Meyers commented on  JENKINS-35796  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Developer can stop the run of an executing pipeline   
 

  
 
 
 
 

 
 Michael Neale: I was testing this integration for JENKINS-36973 but had started using the simpler /stop API that was not blocking. I noticed that in some cases it stopped almost immediately (perhaps for freestyle?) but in certain pipeline cases it would take a very long time (well over 10s) to stop. I assume that using a blocking call should fix that for the most part, using this style: ../stop/?blocking=true=10 If it works as expected, a SSE should come through that should update the job and cause the "stop" button to disappear and be replaced with a "run" button. If that doesn't happen, after 10s, what should the stop button do? Revert from disabled to enabled state so the user can try again?  
 

  
 
 
 
 

 
 
 

 
 
 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-37635) Git Tags with "/" in their name are not displayed

2016-08-24 Thread klim...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Boguslaw Klimas closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37635  
 
 
  Git Tags with "/" in their name are not displayed   
 

  
 
 
 
 

 
Change By: 
 Boguslaw Klimas  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 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-37661) executor.interupt(Result.ABORTED, ...) doesn't actually stop a pipeline/workflow job

2016-08-24 Thread kbrow...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin Browder created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37661  
 
 
  executor.interupt(Result.ABORTED, ...) doesn't actually stop a pipeline/workflow job   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Jesse Glick  
 
 
Components: 
 workflow-plugin  
 
 
Created: 
 2016/Aug/24 8:06 PM  
 
 
Environment: 
 Using Jenkins with run:hpi with 1.642.3 with pipeline/workflow 2.1 though I'm pretty sure this is still an issue with the latest jenkins plugin running in normal mode.  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Kevin Browder  
 

  
 
 
 
 

 
 So I want to delete a slave and abort any job that's running on it. One way that appears to work with freestyle projects is to iterate over the slaves executors and do an  

 

ex.interrupt(Result.ABORTED, new CauseOfInterruption.UserInteruption("Killing job because we're removing this slave"))
 

  before terminating the slave. What's nice is that you'd typically get a message in the build logs with the CauseOfInterruption and the job stops. However with Pipelines it says "Aborted by anonymous" (or whatever user has perms to do this) with no cause, then it says "Click here to forcibly terminate running steps". The button works but I want the script (or in this case a plugin, but this is useful on the groovy console as well) to actually abort the job, not prompt me.

[JIRA] (JENKINS-37660) Fix link to Groovy in /scriptler/scriptsettings

2016-08-24 Thread imoutsat...@msn.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ioannis Moutsatsos created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37660  
 
 
  Fix link to Groovy in /scriptler/scriptsettings   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Dominik Bartholdi  
 
 
Components: 
 scriptler-plugin  
 
 
Created: 
 2016/Aug/24 8:03 PM  
 
 
Environment: 
 jenkins-ci 2.19, scriptler 2.9  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Ioannis Moutsatsos  
 

  
 
 
 
 

 
 The 'Groovy script' link is pointing to an old URL at: groovy.codehaus.org. replace with http://groovy-lang.org/  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-37635) Git Tags with "/" in their name are not displayed

2016-08-24 Thread klim...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Boguslaw Klimas commented on  JENKINS-37635  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git Tags with "/" in their name are not displayed   
 

  
 
 
 
 

 
 Hi, Git parameter plugin using method 

 

public Set getTagNames(String tagPattern) throws GitException {
 

 in JGitAPIImpl this method, is implemented as JGitAPIImpl The character '/' is excluded from tag name. I don't know why   

 

public Set getTagNames(String tagPattern) throws GitException {
if (tagPattern == null) tagPattern = "*";

Repository repo = null;
try {
Set tags = new HashSet();
FileNameMatcher matcher = new FileNameMatcher(tagPattern, '/');
repo = getRepository();
Map refList = repo.getRefDatabase().getRefs(R_TAGS);
for (Ref ref : refList.values()) {
String name = ref.getName().substring(R_TAGS.length());
matcher.reset();
matcher.append(name);
if (matcher.isMatch()) tags.add(name);
}
return tags;
} catch (IOException e) {
throw new GitException(e);
} catch (InvalidPatternException e) {
throw new GitException(e);
} finally {
if (repo != null) repo.close();
}
}
 

 I always use this git definition   Regards Boguslaw  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-37635) Git Tags with "/" in their name are not displayed

2016-08-24 Thread klim...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Boguslaw Klimas updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37635  
 
 
  Git Tags with "/" in their name are not displayed   
 

  
 
 
 
 

 
Change By: 
 Boguslaw Klimas  
 
 
Attachment: 
 screenshot-5.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-36687) Refactor RunPipeline to use HAL hrefs in internal logic

Title: Message Title


 
 
 
 

 
 
 

 
   
 Cliff Meyers started work on  JENKINS-36687  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Cliff Meyers  
 
 
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-36687) Refactor RunPipeline to use HAL hrefs in internal logic

Title: Message Title


 
 
 
 

 
 
 

 
   
 Cliff Meyers updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36687  
 
 
  Refactor RunPipeline to use HAL hrefs in internal logic   
 

  
 
 
 
 

 
 It makes sense to do this work now as I am working on other tickets related to the "Run" button and need to do some refactoring anyways.  
 

  
 
 
 
 

 
Change By: 
 Cliff Meyers  
 
 
Sprint: 
 1.0-beta-1  
 

  
 
 
 
 

 
 
 

 
 
 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-37653) Git fetch fails. Returns "Reference directory conflict: refs/heads/" with status code 128

2016-08-24 Thread sya...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Stav Yagev commented on  JENKINS-37653  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git fetch fails. Returns "Reference directory conflict: refs/heads/" with status code 128
 

  
 
 
 
 

 
 My issue is identical but not Jenkins related. I'm posting here since this is the first hit in Google for the above error message. I also have a repo hosted on an EFS share mounted via NFS on a regular Ubuntu EC2 instance. For some reason I cannot fetch any more although working directory clean. 

 

fatal: Reference directory conflict: refs/remotes/origin/
 

  
 

  
 
 
 
 

 
 
 

 
 
 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-37538) classloading issue with xerces lib

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-37538  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: classloading issue with xerces lib   
 

  
 
 
 
 

 
 

might fix this problem as a side effect
 Filed a PR for that just in case it does (desirable anyway).  
 

  
 
 
 
 

 
 
 

 
 
 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-34958) Getting "Your Authorization Token has expired" when using ECR credentials

2016-08-24 Thread and...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Drew Halloran commented on  JENKINS-34958  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Getting "Your Authorization Token has expired" when using ECR credentials   
 

  
 
 
 
 

 
 Adding my voice to the chorus clamoring for a release; this is holding me up from deploying an otherwise fantastically useful little 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-37653) Git fetch fails. Returns "Reference directory conflict: refs/heads/" with status code 128

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Nauda commented on  JENKINS-37653  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git fetch fails. Returns "Reference directory conflict: refs/heads/" with status code 128
 

  
 
 
 
 

 
 Our build doesn't change any tracked files, and the directory is clean: 

 

$ git status
HEAD detached at 9b39969
nothing to commit, working directory clean
 

 Also, the error message and comment imply that something has gone wrong internally in the git repo, doesn't it?  
 

  
 
 
 
 

 
 
 

 
 
 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-36973) Developer can stop the build on a running card

Title: Message Title


 
 
 
 

 
 
 

 
   
 Cliff Meyers commented on  JENKINS-36973  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Developer can stop the build on a running card   
 

  
 
 
 
 

 
 James Dumay would the permissions part of this ticket be out of scope? I don't believe the mechanism to get them exists yet?  
 

  
 
 
 
 

 
 
 

 
 
 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-34815) NodeJS plugin unable to install global NPM packages

2016-08-24 Thread signu...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Matthew Sexton closed an issue as Won't Do  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Closing due to it not being a issue with Jenkins itself, but that the NodeJS plugin has a newer version that is not automatically upgraded by the plugin manager, requiring a manual build of the plugin.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-34815  
 
 
  NodeJS plugin unable to install global NPM packages   
 

  
 
 
 
 

 
Change By: 
 Matthew Sexton  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Won't Do  
 

  
 
 
 
 

 
 
 

 
 
 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

[JIRA] (JENKINS-36974) Developer can stop a run from the activity tab

Title: Message Title


 
 
 
 

 
 
 

 
   
 Cliff Meyers commented on  JENKINS-36974  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Developer can stop a run from the activity tab   
 

  
 
 
 
 

 
 James Dumay would the permissions part of this ticket be out of scope? I don't believe the mechanism to get them exists yet?  
 

  
 
 
 
 

 
 
 

 
 
 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-35796) Developer can stop the run of an executing pipeline

Title: Message Title


 
 
 
 

 
 
 

 
   
 Cliff Meyers commented on  JENKINS-35796  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Developer can stop the run of an executing pipeline   
 

  
 
 
 
 

 
 James Dumay would the permissions part of this ticket be out of scope? I don't believe the mechanism to get them exists yet?  
 

  
 
 
 
 

 
 
 

 
 
 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-37653) Git fetch fails. Returns "Reference directory conflict: refs/heads/" with status code 128

2016-08-24 Thread emmanuel.esparz...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Emmanuel Esparza edited a comment on  JENKINS-37653  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git fetch fails. Returns "Reference directory conflict: refs/heads/" with status code 128
 

  
 
 
 
 

 
 Yes, we  also saw that and  suspect that is caused by a conflicting file left behind from a previous build.  
 

  
 
 
 
 

 
 
 

 
 
 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-37653) Git fetch fails. Returns "Reference directory conflict: refs/heads/" with status code 128

2016-08-24 Thread emmanuel.esparz...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Emmanuel Esparza commented on  JENKINS-37653  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git fetch fails. Returns "Reference directory conflict: refs/heads/" with status code 128
 

  
 
 
 
 

 
 Yes, we suspect that is caused by a conflicting file left behind from a previous build.  
 

  
 
 
 
 

 
 
 

 
 
 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-37653) Git fetch fails. Returns "Reference directory conflict: refs/heads/" with status code 128

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Nauda edited a comment on  JENKINS-37653  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git fetch fails. Returns "Reference directory conflict: refs/heads/" with status code 128
 

  
 
 
 
 

 
 Git source code location of this error message:https://github.com/git/git/blob/master/refs/files-backend.c#L479 {code}  if ((ref1->flag & REF_DIR) || (ref2->flag & REF_DIR))  /* This is impossible by construction */  die("Reference directory conflict: %s", ref1->name); {code}  
 

  
 
 
 
 

 
 
 

 
 
 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-37538) classloading issue with xerces lib

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-37538  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: classloading issue with xerces lib   
 

  
 
 
 
 

 
 To that end I also tried running 1.642.x with up-to-date Subversion and Pipeline plugins, creating a local Subversion repository with trunk/Jenkinsfile set to 

 

def c = readTrusted 'Jenkinsfile'
node {
echo c
}
 

 running svnserve -r … -d, creating a multibranch Pipeline with SCM source set to Subversion using svn://localhost/, and running a build, then also editing Jenkinsfile trivially and triggering a new build via branch indexing. No errors.  
 

  
 
 
 
 

 
 
 

 
 
 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-37653) Git fetch fails. Returns "Reference directory conflict: refs/heads/" with status code 128

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Nauda edited a comment on  JENKINS-37653  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git fetch fails. Returns "Reference directory conflict: refs/heads/" with status code 128
 

  
 
 
 
 

 
 Git source code location of this error message:https://github.com/git/git/blob/master/refs/files-backend.c#L479 {{  if ((ref1->flag & REF_DIR) || (ref2->flag & REF_DIR))  /* This is impossible by construction */  die("Reference directory conflict: %s", ref1->name); }}  
 

  
 
 
 
 

 
 
 

 
 
 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-37653) Git fetch fails. Returns "Reference directory conflict: refs/heads/" with status code 128