[JIRA] (JENKINS-38585) User can add a new step from the list of available steps and edit it

2016-09-28 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38585  
 
 
  User can add a new step from the list of available steps and edit it   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 

  
 
 
 
 

 
 *In Scope** User clicks "Add Step" and the dialog appears showing a list of steps* Clicking "Use Step" adds a the step to the end of the step list* User can see the form for the step in the editor* List of available steps is driven by the API provided by JENKINS-38584* An extension point for a step editor to plug into* Implement for at least 2 different steps (so we know what a step editor form looks like) * User can click on a step after it has been added and edit contents (via its editor, unless it is "unsupported" type see https://issues.jenkins-ci.org/browse/JENKINS-38590)   *Out of Scope** Adding a step which doesn't have an editor (handled in another ticket)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-31567) PROBLEM Report - Jenkins ver. 1.609.3 - org.apache.http.nio.protocol.HttpAsyncRequestExecutor exception

2016-09-28 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-31567  
 
 
  PROBLEM Report - Jenkins ver. 1.609.3 - org.apache.http.nio.protocol.HttpAsyncRequestExecutor exception   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Status: 
 Reopened Resolved  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-31567) PROBLEM Report - Jenkins ver. 1.609.3 - org.apache.http.nio.protocol.HttpAsyncRequestExecutor exception

2016-09-28 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Well, it's actually a real issue. Occasionally noticed it Duplicates JENKINS-34774, where we conduct the discussion  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-31567  
 
 
  PROBLEM Report - Jenkins ver. 1.609.3 - org.apache.http.nio.protocol.HttpAsyncRequestExecutor exception   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Resolution: 
 Not A Defect  
 
 
Status: 
 Resolved Reopened  
 

  
 
 
 
 

 
 
 

 
 
 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 

[JIRA] (JENKINS-38123) Jenkins detected multiple instances after changing URL

2016-09-28 Thread erne...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ernestas Lukoševičius commented on  JENKINS-38123  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins detected multiple instances after changing URL   
 

  
 
 
 
 

 
 Yes, I checked for any PIDs with the numbers in errors, but only found one instance. And even if there would be a separate Jenkins process - still doesn't explain the difference in URLs.  
 

  
 
 
 
 

 
 
 

 
 
 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-38301) Add configuration for admin monitors

2016-09-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck updated  JENKINS-38301  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38301  
 
 
  Add configuration for admin monitors   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
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-38391) Administrative monitors should be more noticeable

2016-09-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck updated  JENKINS-38391  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38391  
 
 
  Administrative monitors should be more noticeable   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
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-38123) Jenkins detected multiple instances after changing URL

2016-09-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-38123  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins detected multiple instances after changing URL   
 

  
 
 
 
 

 
 The number before the 'at' identifies the JVM Jenkins is running on. So it's a different process.  
 

  
 
 
 
 

 
 
 

 
 
 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-38123) Jenkins detected multiple instances after changing URL

2016-09-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck resolved as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 'appears to have resolved by itself'  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-38123  
 
 
  Jenkins detected multiple instances after changing URL   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Status: 
 Open 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 https://groups.google.co

[JIRA] (JENKINS-38438) image.inside { ... } does not create full configured user account

2016-09-28 Thread ogon...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oliver Gondža commented on  JENKINS-38438  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: image.inside { ... } does not create full configured user account   
 

  
 
 
 
 

 
 I just noticed this is the reason why WorkflowPluginTest#sshGitInsideDocker fails in ATH: 

 
[Pipeline] sh
[junit729626358238985] Running shell script
+ mkdir //.ssh
mkdir: cannot create directory '//.ssh': Permission denied
 

 The actual script is sh 'mkdir ~/.ssh && echo StrictHostKeyChecking no > ~/.ssh/config'  
 

  
 
 
 
 

 
 
 

 
 
 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-37499) Triggering builds with the project api token should not be using "anonymous" access rights

2016-09-28 Thread e...@enlightened.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicolai Ehemann edited a comment on  JENKINS-37499  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Triggering builds with the project api token should not be using "anonymous" access rights   
 

  
 
 
 
 

 
 The build token root plugin is only a workaround. I think you should really be interested to fix the underlying problem.Where is the reasoning behind access by the project token to be anonymous? If a user wants anonymous users to be able to trigger builds, he can give anonymous the correct privileges. If a user provides/configures a projekt token, he expects to be able to use it to trigger builds, without being forced to give anonymous users widespread privileges (or install a workaround plugin that shouldn't be necessary to exist in the first place).If you don't want the user to be able to trigger builds with the project token, remove the option altogether. It should then be provided by a plugin (_then_, the build root plugin makes sense , although it's still bad design as the solution lives outside the normal privilege system ).  
 

  
 
 
 
 

 
 
 

 
 
 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-37452) NPE if "This build is parameterized" enabled and no build parameters added

2016-09-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-37452  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: NPE if "This build is parameterized" enabled and no build parameters added   
 

  
 
 
 
 

 
 Please make sure you're on a current release of Jenkins before filing bugs. Otherwise you're likely just wasting time.  
 

  
 
 
 
 

 
 
 

 
 
 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-38123) Jenkins detected multiple instances after changing URL

2016-09-28 Thread erne...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ernestas Lukoševičius commented on  JENKINS-38123  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins detected multiple instances after changing URL   
 

  
 
 
 
 

 
 The issue appeared only when we changed the URL and one of the URLs in the error is the old one. And, thus, one of my questions is where it takes that URL from, as other than job configurations and logs - nothing in /var/lib/jenkins contain it anymore (checked using grep -R) Yes, I am absolutely sure. Both ps outputs for host and container show only one Jenkins. And there is also no other container using that volume. The issue seems to have resolved by itself. We have build log rotation set up. The only logical explanation I can think for this issue going away like that is that it sometimes used the URL from build logs to create .owner file. Maybe not true, but we haven't done anything else except for patiently waiting.  
 

  
 
 
 
 

 
 
 

 
 
 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-37452) NPE if "This build is parameterized" enabled and no build parameters added

2016-09-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37452  
 
 
  NPE if "This build is parameterized" enabled and no build parameters added   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-37499) Triggering builds with the project api token should not be using "anonymous" access rights

2016-09-28 Thread e...@enlightened.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicolai Ehemann commented on  JENKINS-37499  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Triggering builds with the project api token should not be using "anonymous" access rights   
 

  
 
 
 
 

 
 The build token root plugin is only a workaround. I think you should really be interested to fix the underlying problem. Where is the reasoning behind access by the project token to be anonymous? If a user wants anonymous users to be able to trigger builds, he can give anonymous the correct privileges. If a user provides/configures a projekt token, he expects to be able to use it to trigger builds, without being forced to give anonymous users widespread privileges (or install a workaround plugin that shouldn't be necessary to exist in the first place). If you don't want the user to be able to trigger builds with the project token, remove the option altogether. It should then be provided by a plugin (then, the build root plugin makes sense).  
 

  
 
 
 
 

 
 
 

 
 
 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-37294) Jenkins Plugin Manager is not working getting error

2016-09-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck resolved as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 

jenkins-core-1.593
 Long outdated.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-37294  
 
 
  Jenkins Plugin Manager is not working getting error   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Status: 
 Open 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 unsubs

[JIRA] (JENKINS-37257) Buildqueue shows inconsistent entries from time to time

2016-09-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-37257  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Buildqueue shows inconsistent entries from time to time   
 

  
 
 
 
 

 
 

Problem is since upgrade from 1.523.
 ~100 release in between? That doesn't exactly narrow it down…  
 

  
 
 
 
 

 
 
 

 
 
 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-37150) Add Whitelist to "Cross Site Request Forgery"

2016-09-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck resolved as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Specific endpoints in Jenkins can opt out of requiring CSRF crumbs. That's the approach that should be taken here, rather than burden the admin with something they're likely ill-equipped to deal with.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-37150  
 
 
  Add Whitelist to "Cross Site Request Forgery"   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Won't Fix  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38271) When creating a new item from copy which has parameter, SVN does not record any revision

2016-09-28 Thread magnus.arin...@afconsult.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Marcus Arganso commented on  JENKINS-38271  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: When creating a new item from copy which has parameter, SVN does not record any revision   
 

  
 
 
 
 

 
 Every build performed all the stages. Note that as stated in the description of this problem the SVN polling log stated: 

Workspace doesn't contain https://. Need a new build.
 Even though the repository was clearly in the workspace. Maybe the description of this bug is incorrect and confusing. Removing the random parameter string from my job, saving and re-adding it again solved the problem. Seems strange how the random string parameter could affect SVN but thats what happened.  
 

  
 
 
 
 

 
 
 

 
 
 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-37218) ClassFilter uses Regexs to match String.startsWith patterns

2016-09-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-37218  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ClassFilter uses Regexs to match String.startsWith patterns   
 

  
 
 
 
 

 
 stephenconnolly This is fixed now?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-37226) Downloading JDK gives ERROR: SEVERE ERROR occurs

2016-09-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 In the process of downloading, Jenkins gets redirected to an HTTPS URL, and it cannot validate the certificate. That's an issue between the site and the Java certificate store, and not with the application.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-37226  
 
 
  Downloading JDK gives ERROR: SEVERE ERROR occurs   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
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 th

[JIRA] (JENKINS-37498) Builds can not be triggered by api with project token when csrf protection is enabled

2016-09-28 Thread e...@enlightened.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicolai Ehemann resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 It's actually a duplicate of #22474. Sorry I didn't find that one when reporting the bug (yes, I did a search before). As that one lingers since more than two years, I don't expect it to be resolved too soon.   
 

  
 
 
 
 

 
 Jenkins /  JENKINS-37498  
 
 
  Builds can not be triggered by api with project token when csrf protection is enabled   
 

  
 
 
 
 

 
Change By: 
 Nicolai Ehemann  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-37197) Allow custom configuration-file name

2016-09-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 JENKINS_HOME=wherever-you-want java -jar jenkins.war  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-37197  
 
 
  Allow custom configuration-file name   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
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-38141) We keep losing connectivity to Jenkins server

2016-09-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 This is an issue tracker, not a support site. Please ask for advice on the jenkinsci-users mailing list or in #jenkins on Freenode.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-38141  
 
 
  We keep losing connectivity to Jenkins server   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
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+

[JIRA] (JENKINS-33969) claim-plugin cannot be used with pipelines (workflows)

2016-09-28 Thread at.ra...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ramya Authappan commented on  JENKINS-33969  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: claim-plugin cannot be used with pipelines (workflows)   
 

  
 
 
 
 

 
 Hi is there a way to workaround this issue? I add this in my Jenkinsfile:  step([$class: 'ClaimPublisher']) But i see nothing after the build faliure. Jenkins version: 2.20 Claim Plugin Version: 2.8  
 

  
 
 
 
 

 
 
 

 
 
 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-38321) Move Pipeline editor to new repository

2016-09-28 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale assigned an issue to Michael Neale  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 This is almost done, there is a HOSTING backlog. Once it is, I will setup CI for it (with a Jenkinsfile). cc Josh McDonald - I don't expect there are tests in it yet but it will just run mvn test the usual way to validate PRs.   
 

  
 
 
 
 

 
 Jenkins /  JENKINS-38321  
 
 
  Move Pipeline editor to new repository   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 
 
Assignee: 
 James Dumay Michael Neale  
 

  
 
 
 
 

 
 
 

 
 
 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-38130) JENKINS_HOME is set different on trigger manual build

2016-09-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-38130  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JENKINS_HOME is set different on trigger manual build   
 

  
 
 
 
 

 
 is the envinject plugin installed?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38130) JENKINS_HOME is set different on trigger manual build

2016-09-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38130  
 
 
  JENKINS_HOME is set different on trigger manual build   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Priority: 
 Blocker Minor  
 

  
 
 
 
 

 
 
 

 
 
 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-38123) Jenkins detected multiple instances after changing URL

2016-09-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-38123  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins detected multiple instances after changing URL   
 

  
 
 
 
 

 
 The URL has nothing to do with it. Are you absolutely sure there's no other Jenkins container on the same host with the same JENKINS_HOME volume?  
 

  
 
 
 
 

 
 
 

 
 
 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-33507) Bitbucket Server webhooks and Bitbucket Cloud build status notifications

2016-09-28 Thread mihai.marine...@bksv.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Marinescu commented on  JENKINS-33507  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Bitbucket Server webhooks and Bitbucket Cloud build status notifications   
 

  
 
 
 
 

 
 Antonio Muñiz When do you plan to release this ? Is there a way i can test this now ?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38050) Unable to successfully compare SHA-1 for all plugins using Web-GUI for Plugins Update Center

2016-09-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Temporary infra issue, we removed the misconfigured Chinese mirror and things should be fine now. Please try to post your war stories to your blog, literally half the issue description has nothing to do with anything. Makes it very difficult to determine what the bug you're reporting actually is.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-38050  
 
 
  Unable to successfully compare SHA-1 for all plugins using Web-GUI for Plugins Update Center   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

  

[JIRA] (JENKINS-38119) All jobs finish in timeout randomly

2016-09-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 This is an issue tracker, not a support site.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-38119  
 
 
  All jobs finish in timeout randomly   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
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-38599) groovy-axis to accept number array

2016-09-28 Thread daniel.bl...@au.ibm.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Black created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38599  
 
 
  groovy-axis to accept number array   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 emanuelez  
 
 
Components: 
 groovyaxis-plugin  
 
 
Created: 
 2016/Sep/29 6:12 AM  
 
 
Environment: 
 groovyaxis 0.3  jenkins 2.23  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Daniel Black  
 

  
 
 
 
 

 
 The following results in "default" being the value rather than the number(s). While quoting all these numbers worked, I suspect this could be done in the plugin. 

 
if (context == null) {
return [1]
}

def test = context.build.buildVariableResolver.resolve("test")

if (test == "oltp") {
return [1,8,16,32,64,96,128]
}

if (test == "oltp_decimal") {
return [1,8,16,32,64,96,128]
}

return [1]
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
  

[JIRA] (JENKINS-38326) Redesign the headers hierarchy

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


 
 
 
 

 
 
 

 
   
 Brody Maclean started work on  JENKINS-38326  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Brody Maclean  
 
 
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-37853) Unable to 'restart' jenkins fater upgrade when launched through java service wrapper

2016-09-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-37853  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to 'restart' jenkins fater upgrade when launched through java service wrapper   
 

  
 
 
 
 

 
 

I need a service that restarts on boot and that I can manage / stop/ start if needed
 How is that different from the service that gets set up by the RPM?  
 

  
 
 
 
 

 
 
 

 
 
 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-38325) We need a logo mark for Blue Ocean

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


 
 
 
 

 
 
 

 
   
 Brody Maclean closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38325  
 
 
  We need a logo mark for Blue Ocean   
 

  
 
 
 
 

 
Change By: 
 Brody Maclean  
 
 
Status: 
 In Progress Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38443) Pollscm trigger runs the job twice for the same commit

2016-09-28 Thread nick.sonnev...@smartward.com.au (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Sonneveld edited a comment on  JENKINS-38443  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pollscm trigger runs the job twice for the same commit   
 

  
 
 
 
 

 
 As far as I know, we're only polling "daily" per branch , configured via pollSCM .  We do have a mercurial  trigger  hook that GETs "/mercurial/notifyCommit"  for each commit but I feel that shouldn't affect things  as that is just notifying jenkins that "something" changed .  The parent multibranch job does not have any polling configured.  
 

  
 
 
 
 

 
 
 

 
 
 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-37489) Jenkins UI slow page load (big TTFB) - possible LDAP issue

2016-09-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Looks like a duplicate of JENKINS-35493  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-37489  
 
 
  Jenkins UI slow page load (big TTFB) - possible LDAP issue   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-37498) Builds can not be triggered by api with project token when csrf protection is enabled

2016-09-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-37498  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Builds can not be triggered by api with project token when csrf protection is enabled   
 

  
 
 
 
 

 
 Where's the bug here? If you POST, you're expected to provide a token. /crumbIssuer/api/xml exists for that reason.  
 

  
 
 
 
 

 
 
 

 
 
 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-37499) Triggering builds with the project api token should not be using "anonymous" access rights

2016-09-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck resolved as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Use the Build Token Root Plugin  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-37499  
 
 
  Triggering builds with the project api token should not be using "anonymous" access rights   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Won't Fix  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38443) Pollscm trigger runs the job twice for the same commit

2016-09-28 Thread nick.sonnev...@smartward.com.au (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Sonneveld reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38443  
 
 
  Pollscm trigger runs the job twice for the same commit   
 

  
 
 
 
 

 
Change By: 
 Nick Sonneveld  
 
 
Resolution: 
 Not A Defect  
 
 
Status: 
 Resolved Reopened  
 

  
 
 
 
 

 
 
 

 
 
 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-37434) Select version of Jenkins to auto upgrade to

2016-09-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-37434  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Select version of Jenkins to auto upgrade to   
 

  
 
 
 
 

 
 Probably too much effort to be worth it, e.g. if there's a security update, we wouldn't want people to download an older release. Not to mention that we don't currently have the necessary metadata in the update site JSON, so needs an infra change as well. If you don't like the defaults, there's always manual download.  
 

  
 
 
 
 

 
 
 

 
 
 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-38443) Pollscm trigger runs the job twice for the same commit

2016-09-28 Thread nick.sonnev...@smartward.com.au (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Sonneveld edited a comment on  JENKINS-38443  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pollscm trigger runs the job twice for the same commit   
 

  
 
 
 
 

 
 As far as I know, we're only polling "daily" per branch.  We do have a mercurial trigger for each commit but I feel that shouldn't affect things.   The parent multibranch job does not have any polling configured.  
 

  
 
 
 
 

 
 
 

 
 
 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-38443) Pollscm trigger runs the job twice for the same commit

2016-09-28 Thread nick.sonnev...@smartward.com.au (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Sonneveld commented on  JENKINS-38443  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pollscm trigger runs the job twice for the same commit   
 

  
 
 
 
 

 
 As far as I know, we're only polling "daily" per branch. We do have a mercurial trigger for each commit but I feel that shouldn't affect things.  
 

  
 
 
 
 

 
 
 

 
 
 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-38461) Flag to disable Inject Node Properties -> Environment Variables at job level

2016-09-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck resolved as Incomplete  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Unclear what this is about.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-38461  
 
 
  Flag to disable Inject Node Properties -> Environment Variables at job level
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Incomplete  
 

  
 
 
 
 

 
 
 

 
 
 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.

[JIRA] (JENKINS-38461) Flag to disable Inject Node Properties -> Environment Variables at job level

2016-09-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-38461  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Flag to disable Inject Node Properties -> Environment Variables at job level
 

  
 
 
 
 

 
 What is this about? Is this about the terrible plugin that's messed up everything remotely related to environment variables, rather than core?  
 

  
 
 
 
 

 
 
 

 
 
 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-38186) java.io.NotSerializableException: groovy.lang.MapWithDefault

2016-09-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Due to https://github.com/jenkinsci/workflow-cps-plugin/#technical-design If a regression, that's due to https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Groovy+Plugin#PipelineGroovyPlugin-2.14%28Sep07%2C2016%29 Also see https://github.com/jenkinsci/pipeline-plugin/blob/master/TUTORIAL.md#serializing-local-variables  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-38186  
 
 
  java.io.NotSerializableException: groovy.lang.MapWithDefault   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   



[JIRA] (JENKINS-38449) ZipExtractionInstaller not working behind proxy

2016-09-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-38449  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ZipExtractionInstaller not working behind proxy   
 

  
 
 
 
 

 
 stephenconnolly Is this even fixable after your changes for JENKINS-33414?  
 

  
 
 
 
 

 
 
 

 
 
 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-38443) Pollscm trigger runs the job twice for the same commit

2016-09-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 You're probably polling too often. Jenkins looks at past builds to determine what has already been built, and if there's not enough time to start a build and checkout from SCM to record what the current state is, Jenkins will just queue another build, as what has been found hasn't been built yet.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-38443  
 
 
  Pollscm trigger runs the job twice for the same commit   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
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 messa

[JIRA] (JENKINS-38559) Improve Plugin Management

2016-09-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck resolved as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Let's see… 
 
Support Core plugin includes a Dockerfile to recreate an instance in the support bundles it creates 
Jenkins remote API let's you retrieve a list of plugins and versions from Jenkins, making it trivial to transform that into wget statements (e.g. https://jenkins/pluginManager/api/xml?tree=plugins[shortName,version,enabled] (and if you don't need exact versions, there's https://github.com/jenkinsci/install-necessary-plugins ) 
Then there's always tar czf … $JENKINS_HOME/plugins/*.jpi. 
 While none of these may be the "perfect" solution, they should all be close enough. Resolving as Won't Fix, as that's my best guess here unless you decide to work on something yourself (and the major obstacle here is that the update site metadata does not include arbitrary versions, but only the newest one, so this issue has a major infra component as well unless you decide to hard-code paths). Feel free to reopen, but don't hold your breath for anyone else to work on this.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-38559  
 
 
  Improve Plugin Management   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Won't Fix  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 

[JIRA] (JENKINS-38487) Jenkins fails to startup if the EnvInject global system properties file is missing

2016-09-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38487  
 
 
  Jenkins fails to startup if the EnvInject global system properties file is missing   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Labels: 
 robustness  
 

  
 
 
 
 

 
 
 

 
 
 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-38565) Build history lost after renaming project

2016-09-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-38565  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Build history lost after renaming project   
 

  
 
 
 
 

 
 Your report is contradictory – first, you write that the project renames itself, then you write that the build names are set. Which is 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-38567) Upgrading from 1.646 to 1.651.3 breaks creating parameters from Groovy

2016-09-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 That's not what a minimal reproduction case looks like. Do you actually expect someone to work through this? That said, probably fallout from https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11 (first item).  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-38567  
 
 
  Upgrading from 1.646 to 1.651.3 breaks creating parameters from Groovy   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
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 

[JIRA] (JENKINS-38579) "All" view hyperlinks get localized, conflict with BlueOcean

2016-09-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-38579  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "All" view hyperlinks get localized, conflict with BlueOcean   
 

  
 
 
 
 

 
 Not a core issue. If the 'All' name is hardcoded, that's just plain wrong as users can change the default view, and even remove the 'All; view. https://wiki.jenkins-ci.org/display/JENKINS/Editing+or+Replacing+the+All+View  
 

  
 
 
 
 

 
 
 

 
 
 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-38579) "All" view hyperlinks get localized, conflict with BlueOcean

2016-09-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38579  
 
 
  "All" view hyperlinks get localized, conflict with BlueOcean   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Component/s: 
 core  
 

  
 
 
 
 

 
 
 

 
 
 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-38598) User can connect to Git with Username and Password

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


 
 
 
 

 
 
 

 
   
 James Dumay created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38598  
 
 
  User can connect to Git with Username and Password   
 

  
 
 
 
 

 
Issue Type: 
  Story  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2016/Sep/29 4:11 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 James Dumay  
 

  
 
 
 
 

 
 In Scope 
 
Make username/password credentials work 
Simple text area to copy/paste the SSH key 
Validate that the text area is not empty 
Validate that the credentials are correct 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
 

[JIRA] (JENKINS-38597) User can connect to Git with SSH key

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


 
 
 
 

 
 
 

 
   
 James Dumay created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38597  
 
 
  User can connect to Git with SSH key   
 

  
 
 
 
 

 
Issue Type: 
  Story  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2016/Sep/29 4:10 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 James Dumay  
 

  
 
 
 
 

 
 In Scope 
 
Make SSH key credentials work 
Simple text area to copy/paste the SSH key 
Validate that the text area is not empty 
Validate that the credentials are correct 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
 

[JIRA] (JENKINS-38596) User can connect to a git repository

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


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38596  
 
 
  User can connect to a git repository   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 

  
 
 
 
 

 
 *In Scope** Allow the user to specify a URL*  Always uses system ssh  Radio list that shows different credentials and their forms: **  Just add a single radio option for that.  System SSH * * SSH** Username password* Only the System SSH does anything*  Validate that the credentials are correct* Validate that the fields are not empty* Create Pipeline button redirects them to the activity page of a Pipeline  
 

  
 
 
 
 

 
 
 

 
 
 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-38587) User can add and edit a block scoped step

2016-09-28 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38587  
 
 
  User can add and edit a block scoped step   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 
 
Summary: 
 User can add  and edit  a block scoped step  
 

  
 
 
 
 

 
 
 

 
 
 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-38587) User can add and edit a block scoped step

2016-09-28 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38587  
 
 
  User can add and edit a block scoped step   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 

  
 
 
 
 

 
 *In scope** User can add a block scoped step to the main step list*  User can click on a block scoped step and edit its attributes*  Should look like the screenshot below !Pipeline config - block scope.png|thumbnail!   
 

  
 
 
 
 

 
 
 

 
 
 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-38585) User can add a new step from the list of available steps and edit it

2016-09-28 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38585  
 
 
  User can add a new step from the list of available steps and edit it   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 
 
Summary: 
 User can add a new step from the list of available steps  and edit 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-38583) update node version in mvn front end plugin

2016-09-28 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale closed an issue as Won't Do  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 bah, no point in doing this now: https://github.com/npm/npm/issues/11993#issuecomment-231973924 still an issue with 6 . Eventually worth doing, but won't solve any current problems it seems. Closing.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-38583  
 
 
  update node version in mvn front end plugin   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 
 
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 this group an

[JIRA] (JENKINS-38596) User can connect to a git repository

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


 
 
 
 

 
 
 

 
   
 James Dumay created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38596  
 
 
  User can connect to a git repository   
 

  
 
 
 
 

 
Issue Type: 
  Story  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2016/Sep/29 3:53 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 James Dumay  
 

  
 
 
 
 

 
 In Scope 
 
Allow the user to specify a URL 
Always uses system ssh 
 
Just add a single radio option for that. 
  
Validate that the credentials are correct 
Validate that the fields are not empty 
Create Pipeline button redirects them to the activity page of a Pipeline 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

[JIRA] (JENKINS-38585) User can add a new step from the list of available steps

2016-09-28 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-38585  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: User can add a new step from the list of available steps   
 

  
 
 
 
 

 
 This is probably the chunkiest ticket, if it makes sense to spin off other ones, we can.   
 

  
 
 
 
 

 
 
 

 
 
 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-38595) User can select from list of SCM providers

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


 
 
 
 

 
 
 

 
   
 James Dumay created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38595  
 
 
  User can select from list of SCM providers   
 

  
 
 
 
 

 
Issue Type: 
  Story  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2016/Sep/29 3:51 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 James Dumay  
 

  
 
 
 
 

 
 In Scope 
 
Extension point to provide buttons for different SCM providers 
e.g. Git, Github, Bitbucket. 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
  

[JIRA] (JENKINS-38585) User can add a new step from the list of available steps

2016-09-28 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38585  
 
 
  User can add a new step from the list of available steps   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 

  
 
 
 
 

 
 *In Scope** User clicks "Add Step" and the dialog appears showing a list of steps* Clicking "Use Step" adds a the step to the end of the step list* User can see the form for the step in the editor* List of available steps is driven by the API provided by JENKINS-38584* An extension point for a step editor to plug into* Implement for at least 2 different steps (so we know what a step editor form looks like) *Out of Scope** Adding a step which doesn't have an editor (handled in another ticket)  
 

  
 
 
 
 

 
 
 

 
 
 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-38585) User can add a new step from the list of available steps

2016-09-28 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38585  
 
 
  User can add a new step from the list of available steps   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 

  
 
 
 
 

 
 *In Scope** User clicks "Add Step" and the dialog appears showing a list of steps* Clicking "Use Step" adds a the step to the end of the step list* User can see the form for the step in the editor* List of available steps is driven by the API provided by JENKINS-38584 * An extension point for a step editor to plug into* Implement for at least 2 different steps (so we know what a step editor form looks like)  
 

  
 
 
 
 

 
 
 

 
 
 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-38591) User can get the Jenkinsfile for a Pipeline

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


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-38591  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: User can get the Jenkinsfile for a Pipeline   
 

  
 
 
 
 

 
 Michael Neale first cut is just to copy and paste from the dialog after "save"  
 

  
 
 
 
 

 
 
 

 
 
 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-38591) User can get the Jenkinsfile for a Pipeline

2016-09-28 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-38591  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: User can get the Jenkinsfile for a Pipeline   
 

  
 
 
 
 

 
 James Dumay Won't the first iteration of this only support downloading of Jenkinsfile?   
 

  
 
 
 
 

 
 
 

 
 
 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-38312) TFS plugin fails with TF400898: An Internal Error Occurred

2016-09-28 Thread jaredljen...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jared Jensen commented on  JENKINS-38312  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: TFS plugin fails with TF400898: An Internal Error Occurred   
 

  
 
 
 
 

 
 I searched the application log for both the error code and Activity Id with no matches. Then I filtered to a source of "Jenkins" and saw mostly informational events, with the last one on 9/18 showing the service starting. Both builds that occurred since 9/18 failed with the same stack trace.  
 

  
 
 
 
 

 
 
 

 
 
 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-38312) TFS plugin fails with TF400898: An Internal Error Occurred

2016-09-28 Thread jaredljen...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jared Jensen assigned an issue to Olivier Dagenais  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38312  
 
 
  TFS plugin fails with TF400898: An Internal Error Occurred   
 

  
 
 
 
 

 
Change By: 
 Jared Jensen  
 
 
Assignee: 
 Jared Jensen Olivier Dagenais  
 

  
 
 
 
 

 
 
 

 
 
 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-38434) Project list shows outdated icons

2016-09-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-38434  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Project list shows outdated icons   
 

  
 
 
 
 

 
 Most UI efforts are currently focused on the 'blue ocean' project. I doubt we'll ever do a large scale overhaul of the existing UI. https://jenkins.io/blog/2016/05/26/introducing-blue-ocean/ https://jenkins.io/blog/2016/07/19/blue-ocean-update/ https://jenkins.io/blog/2016/09/19/blueocean-beta-declarative-pipeline-pipeline-editor/  
 

  
 
 
 
 

 
 
 

 
 
 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-36603) API to enable automatic discovery of pipelines for Github

2016-09-28 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-36603  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: API to enable automatic discovery of pipelines for Github   
 

  
 
 
 
 

 
 James Dumay any reason why this is "won't fix"?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38594) User can click "Create Pipeline" and open the creation flow process

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


 
 
 
 

 
 
 

 
   
 James Dumay created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38594  
 
 
  User can click "Create Pipeline" and open the creation flow process   
 

  
 
 
 
 

 
Issue Type: 
  Story  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2016/Sep/29 2:18 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 James Dumay  
 

  
 
 
 
 

 
 In Scope 
 
Blank dialog with "Create Pipeline" in header 
Creation flow goes into its own plugin "blueocean-pipeline-creation-plugin" 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
   

[JIRA] (JENKINS-20668) Persist Jenkins swarm slaves when they go offline

2016-09-28 Thread bkl...@advent.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bevan Kling commented on  JENKINS-20668  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Persist Jenkins swarm slaves when they go offline   
 

  
 
 
 
 

 
 Would it be possible to add the ability to set the node properties for the following options in the swarm config 
 
Node Offline Email Notification 
Node owners 
 
 
Send email when connected 
Send email when disconnected 
Send email on every launch failure 
Send email on first launch failure 
Send email when temporary off-line mark applied 
Send email when temporary off-line mark applied 
Send email when temporary off-line mark removed 
  
 

  
 
 
 
 

 
 
 

 
 
 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.

[JIRA] (JENKINS-38593) Double build triggers by branch indexing

2016-09-28 Thread jrs.dmz.2...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joseph Schneider commented on  JENKINS-38593  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Double build triggers by branch indexing   
 

  
 
 
 
 

 
 Also of note, the githook triggered build (#7) is MUCH nicer in that it has the commit messages listed, whereas the branch index created one (#8) doesn't. I'm not sure if that's just because it came second.  
 

  
 
 
 
 

 
 
 

 
 
 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-38593) Double build triggers by branch indexing

2016-09-28 Thread jrs.dmz.2...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joseph Schneider created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38593  
 
 
  Double build triggers by branch indexing   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 stephenconnolly  
 
 
Components: 
 branch-api-plugin, github-organization-folder-plugin  
 
 
Created: 
 2016/Sep/29 1:57 AM  
 
 
Environment: 
 Jenkins 2.7.4  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Joseph Schneider  
 

  
 
 
 
 

 
 Expected behavior: A git hook from github will trigger only a single job. A newly detected branch will automatically trigger a build. Observed behavior: A git hook will trigger a build, but the branch indexing will also trigger a build. When a new branch is detected, only a single build is triggered (by branch indexing). snippet from the log: `SCM changes detected in DroneDeploy/drone_pipeline/stage. Triggering #7` Nothing else relevant in the logs after that (as far as build triggering goes) but two jobs are triggered: #7 ``` Started by GitHub push by mikedeploysdrones Revision: 7b0f8da66854b2d364ef2da527d7b4ba8838fc70 ``` #8 ``` Branch indexing Revision: 7b0f8da66854b2d364ef2da527d7b4ba8838fc70 stage ``` When I turn off "Automatic branch project triggering", then the second job doesn't get triggered, but then new branches don't get built the first time, they have to be manually triggered. As far as I can tell, only having branch indexing to trigger builds would fix the problem. However, in order to trigger the branch indexing, I need a githook, which will also trigger a build. My githook is currently configured for the following events: Create, Delete, Push, Repository. I feel like I'm doing something really dumb here because this isn't exactly a subtle issue, although relatively benign. Happy to provide additional information.  
 

  

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

2016-09-28 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-34564  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
 espenalb Ben Herfurth perhaps open a new ticket for the path limit on windows? as it may be able to be reduced.  I note that windows 10 claims to have removed that limit: https://mspoweruser.com/ntfs-260-character-windows-10/  
 

  
 
 
 
 

 
 
 

 
 
 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-38578) Git Publisher is not working after promotion of build

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


 
 
 
 

 
 
 

 
   
 Mark Waite edited a comment on  JENKINS-38578  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git Publisher is not working after promotion of build   
 

  
 
 
 
 

 
 Please provide step by step instructions which will allow someone else to see the problem. When I say "step by step", I mean that you should describe how to duplicate the problem in such a way that someone (like me) who does not know what you mean by "after the promotion" can still reproduce the problem.  One way to do that is to describe a numbered series of steps that can be followed.  Another way is to provide a screencast, preferably with narration.  Another way might be to create a docker image and share the definition of the docker image which shows the 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-36599) API to validate github access key and retrieve scopes

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


 
 
 
 

 
 
 

 
   
 James Dumay resolved as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36599  
 
 
  API to validate github access key and retrieve scopes   
 

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-36603) API to enable automatic discovery of pipelines for Github

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


 
 
 
 

 
 
 

 
   
 James Dumay resolved as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36603  
 
 
  API to enable automatic discovery of pipelines for Github   
 

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-36597) API to create a Pipeline using a Git repository

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


 
 
 
 

 
 
 

 
   
 James Dumay resolved as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36597  
 
 
  API to create a Pipeline using a Git repository   
 

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-35799) Developer wants to use Bitbucket as a branch source

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


 
 
 
 

 
 
 

 
   
 James Dumay resolved as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-35799  
 
 
  Developer wants to use Bitbucket as a branch source   
 

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-36601) API to query all the repositories the user has access to on github

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


 
 
 
 

 
 
 

 
   
 James Dumay resolved as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36601  
 
 
  API to query all the repositories the user has access to on github   
 

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


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

2016-09-28 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-34564  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
 Does it matter what the name is on disk? Should the JENKINS_HOME be as transparent as this? I am curious as to what people are doing with it (this change only impacts how it appears on disk if I understand it 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-36600) API to query all the organizations the user has access to on Github

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


 
 
 
 

 
 
 

 
   
 James Dumay resolved as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36600  
 
 
  API to query all the organizations the user has access to on Github   
 

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38434) Project list shows outdated icons

2016-09-28 Thread rogerdp...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 rogerdpack commented on  JENKINS-38434  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Project list shows outdated icons   
 

  
 
 
 
 

 
 Yeah, I'd probably put this as a "feature request" in that case. Cheers!  
 

  
 
 
 
 

 
 
 

 
 
 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-38592) pipelines data for json is getting a bit too crazy

2016-09-28 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-38592  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: pipelines data for json is getting a bit too crazy   
 

  
 
 
 
 

 
 Thorsten Scherler can you confirm if the metadata is used at all on the dashboard now? (if you know) - perhaps the solution is to not have it for the listing (but I don't know if some is used). Whilst future plugins may use it - it is less likely on dashboard listing.  
 

  
 
 
 
 

 
 
 

 
 
 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-38592) pipelines data for json is getting a bit too crazy

2016-09-28 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38592  
 
 
  pipelines data for json is getting a bit too crazy   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 

  
 
 
 
 

 
 In many cases the  / piplines json  for the dashboard (search results)  is blowing out to 14kb for 26 "rows" of data. This isn't a huge json transfer, but when you look closer, the impact of plugins adding to actions appears to be huge, and may be the cause of some problems. As part of looking at a support ticket [~tscherler] uncovered that for 26 pipelines, there is really 20 lines of attributes that are used by the dashboard == 520 lines (roughly). However there is 10k lines in the response - this is a bit out of control. It seems that every plugin installed adds actions for every little thing, which the dashboard doesn't need. For example{noformat}"_class": "io.jenkins.blueocean.service.embedded.rest.ActionProxiesImpl","_links": {  "self": {"_class": "io.jenkins.blueocean.rest.hal.Link","href": "/blue/rest/organizations/jenkins/... (hidden)"  }},"_class": "com.cloudbees.plugins.credentials.ViewCredentialsAction","stores": {},"urlName": "credentials"  }],{noformat}is added to every pipeline (along with 100's of others). Note also the whitespace (may be another problem). It really depends on the plugins. Also {noformat} {"_class": "hudson.model.TextParameterDefinition","defaultParameterValue": {  "_class": "hudson.model.StringParameterValue",  "name": "jiraComment",  "value": ""},"description": "Additional info for theissue's comment","name": "jiraComment","type": "TextParameterDefinition"  },{noformat}will never be of use to the dashboard (well probably). Some questions: Is there a better query to use to make the response smaller/more compact? (even just eyeballing the reponse could be helped by not returning the metadata optionally). I expect the calculation of this is quite expensive. Could this be a source of the slowdown when people have enough/certain plugins installed?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 
 

[JIRA] (JENKINS-38592) pipelines data for json is getting a bit too crazy

2016-09-28 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38592  
 
 
  pipelines data for json is getting a bit too crazy   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 
 
Sprint: 
 pacific  
 

  
 
 
 
 

 
 
 

 
 
 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-38592) pipelines data for json is getting a bit too crazy

2016-09-28 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale edited a comment on  JENKINS-38592  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: pipelines data for json is getting a bit too crazy   
 

  
 
 
 
 

 
 FYI here it is for 3 pipelines and a minimal install: https://gist.github.com/michaelneale/9127c8e14d16baf05910807bd8ac8cc9This isn't as problematic as other "real world" examples. It is still 90% noise for the pipeline screen, but the action list seems fairly finite. The problem is with every single plugin adding to it, when it is returned in the listing. It also doesn't seem bugger (no wayward whitespace in _class or nulls). (putting in current sprint as there is work on to look at search response times)  
 

  
 
 
 
 

 
 
 

 
 
 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-38592) pipelines data for json is getting a bit too crazy

2016-09-28 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-38592  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: pipelines data for json is getting a bit too crazy   
 

  
 
 
 
 

 
 FYI here it is for 3 pipelines and a minimal install: https://gist.github.com/michaelneale/9127c8e14d16baf05910807bd8ac8cc9 This isn't as problematic as other "real world" examples. It is still 90% noise for the pipeline screen, but the action list seems fairly finite. The problem is with every single plugin adding to it, when it is returned in the listing. It also doesn't seem bugger (no wayward whitespace in _class or nulls).  
 

  
 
 
 
 

 
 
 

 
 
 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-38592) pipelines data for json is getting a bit too crazy

2016-09-28 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38592  
 
 
  pipelines data for json is getting a bit too crazy   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Vivek Pandey  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2016/Sep/29 1:36 AM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Michael Neale  
 

  
 
 
 
 

 
 In many cases the /piplines json is blowing out to 14kb for 26 "rows" of data. This isn't a huge json transfer, but when you look closer, the impact of plugins adding to actions appears to be huge, and may be the cause of some problems.  As part of looking at a support ticket Thorsten Scherler uncovered that for 26 pipelines, there is really 20 lines of attributes that are used by the dashboard == 520 lines (roughly).  However there is 10k lines in the response - this is a bit out of control.  It seems that every plugin installed adds actions for every little thing, which the dashboard doesn't need.  For example 

 
"_class": "io.jenkins.blueocean.service.embedded.rest.ActionProxiesImpl",
"_links": {
  "self": {
"_class": "io.jenkins.blueocean.rest.hal.Link",
"href": "/blue/rest/organizations/jenkins/... (hidden)"
  }
},
"_class": "com.cloudbees.plugins.credentials.ViewCredentialsAction",
"stores": {},
"urlName": "credentials"
  }
],
 

 is added to every pipeline (along with 100's of others). Note also the whitespace (may be another problem). It really depends on the plugins.  Also  

 
 {
"_class": "hudson.model.TextParameter

[JIRA] (JENKINS-35856) JDL component for Dialog

2016-09-28 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale edited a comment on  JENKINS-35856  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JDL component for Dialog   
 

  
 
 
 
 

 
 This is required for both editor and creation of new pipelines (the one component should be used). The creation one is just a long one of these that you scroll down as you move along  cc [~cliffmeyers] perhaps if you need this for creation soon, could pull this off Josh' queue? otherwise he will get to it in due course .   
 

  
 
 
 
 

 
 
 

 
 
 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-35856) JDL component for Dialog

2016-09-28 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-35856  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JDL component for Dialog   
 

  
 
 
 
 

 
 This is required for both editor and creation of new pipelines (the one component should be used). The creation one is just a long one of these that you scroll down as you move along.   
 

  
 
 
 
 

 
 
 

 
 
 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-38556) Jenkins spawns infinite windows spot instances on aws.

2016-09-28 Thread sbr...@imagus.com.au (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Steve Brain updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38556  
 
 
  Jenkins spawns infinite windows spot instances on aws.   
 

  
 
 
 
 

 
Change By: 
 Steve Brain  
 
 
Component/s: 
 aws-java-sdk-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-38526) "General Build Step" and pipeline node icon don't reflect unstable results

2016-09-28 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-38526  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "General Build Step" and pipeline node icon don't reflect unstable results   
 

  
 
 
 
 

 
 Régis Desgroppes no worries - its all arm waving terminology, still not settled on names for everything, so no surprise (I just new from recent memory).  Will be good to get this resolved, hopefully soon. Thanks for this! (acts as another vote on the real 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-38023) Favourite card label does not contain full path

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


 
 
 
 

 
 
 

 
   
 Brody Maclean edited a comment on  JENKINS-38023  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Favourite card label does not contain full path   
 

  
 
 
 
 

 
 Logic: Base folder, Parent and Pipeline are shown, everything else collapsed into folder icon, unless path is hovered on.Demo:http://codepen.io/brody/pen/KrZJKp !pipelines-collapses-path.png! Mock up for Dashboard Pipelines & Favs. https://zpl.io/Me1KCFYI Folder icon is from Material Design Iconset https://design.google.com/icons/#ic_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-38023) Favourite card label does not contain full path

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


 
 
 
 

 
 
 

 
   
 Brody Maclean edited a comment on  JENKINS-38023  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Favourite card label does not contain full path   
 

  
 
 
 
 

 
 Logic: Base folder, Parent and Pipeline are shown, everything else collapsed into folder icon, unless path is hovered on.Demo:http://codepen.io/brody/pen/KrZJKp!pipelines-collapses-path.png |thumbnail !Mock up for Dashboard Pipelines & Favs. https://zpl.io/Me1KCFYI Folder icon is from Material Design Iconset https://design.google.com/icons/#ic_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-38023) Favourite card label does not contain full path

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


 
 
 
 

 
 
 

 
   
 Brody Maclean updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38023  
 
 
  Favourite card label does not contain full path   
 

  
 
 
 
 

 
Change By: 
 Brody Maclean  
 
 
Attachment: 
 pipelines-collapses-path.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-38556) Jenkins spawns infinite windows spot instances on aws.

2016-09-28 Thread sbr...@imagus.com.au (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Steve Brain commented on  JENKINS-38556  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins spawns infinite windows spot instances on aws.   
 

  
 
 
 
 

 
 Same problem, I updated to the latest aws-java-sdk 1.11.37 from 1.10.50 library and restarted my Jenkins instance, and noticed no nodes were being created. I looked at my ec2 page and had the maximum number of allowed machines running or starting up. I terminated these and it filled up again. I immediately undid the upgrade and it started working correctly. The jenkins log was filled with these Sep 29, 2016 12:01:08 AM hudson.plugins.ec2.EC2Cloud provision INFO: Attempting to provision slave from template hudson.plugins.ec2.SlaveTemplate@1a01b2a0 needed by excess workload of 1 units of label 'cxx' Considering launching ami-63112100 for template Linux AMI Sep 29, 2016 12:01:10 AM hudson.plugins.ec2.SlaveTemplate logProvisionInfo INFO: Considering launching ami-63112100 for template Linux AMI Setting Instance Initiated Shutdown Behavior : ShutdownBehavior.Stop Sep 29, 2016 12:01:10 AM hudson.plugins.ec2.SlaveTemplate logProvisionInfo INFO: Setting Instance Initiated Shutdown Behavior : ShutdownBehavior.Stop Looking for existing instances with describe-instance: {InstanceIds: [],Filters: [ {Name: image-id,Values: [ami-63112100]} ,  {Name: instance.group-name,Values: [JenkinsSecurity]} ,  {Name: key-name,Values: [Jenkins_keys]} ,  {Name: instance-type,Values: [c3.large]} ,  {Name: tag:Name,Values: [Centos Jenkins Slave CXX]} ,  {Name: tag:Jenkins,Values: [Slave]} ],} Sep 29, 2016 12:01:11 AM hudson.triggers.SafeTimerTask run SEVERE: Timer task hudson.slaves.NodeProvisioner$NodeProvisionerInvoker@459472fa failed java.lang.NoSuchMethodError: com.amazonaws.services.ec2.AmazonEC2.createTags(Lcom/amazonaws/services/ec2/model/CreateTagsRequest;)V at hudson.plugins.ec2.SlaveTemplate.updateRemoteTags(SlaveTemplate.java:882) at hudson.plugins.ec2.SlaveTemplate.provisionOndemand(SlaveTemplate.java:585) at hudson.plugins.ec2.SlaveTemplate.provision(SlaveTemplate.java:377) at hudson.plugins.ec2.EC2Cloud.getNewOrExistingAvailableSlave(EC2Cloud.java:515) at hudson.plugins.ec2.EC2Cloud.provision(EC2Cloud.java:532) at hudson.slaves.NodeProvisioner$StandardStrategyImpl.apply(NodeProvisioner.java:701) at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:307) at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:60) at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:798) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:50) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Sep 29, 2016 12:01:18 AM hudson.plugins.ec2.EC2Cloud provision INFO: Attempting to provision slave from template hudson.plugins.ec2.SlaveTemplate@1a01b2a0 needed by excess workload of 1 units of label 'cxx' Considering launching ami-63112100 for template Linux AMI Sep 29, 2016 12:01:19 AM hudson.plugins.ec2.SlaveTemplate logProvisionInfo INFO: Considering launching ami-63112100 for template Linux AMI Setting Instance Initiated Shutdown Behavior : ShutdownBehavior.Stop Sep 29, 2016 12:01:19 AM hudson.plugins.ec2.SlaveTemplate logProvisionInfo INFO: Setting Instance Initiated Shutdo

  1   2   3   4   >