[JIRA] (JENKINS-38652) To create a JobRestriction's NodeProperty and adding it to the node via a groovy code

[amitkumar_ghat...@persistent.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Amitkumar Ghatwal assigned an issue to Oleg Nenashev  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38652  
 
 
  To create a JobRestriction's NodeProperty and adding it to the node via a groovy code   
 

  
 
 
 
 

 
Change By: 
 Amitkumar Ghatwal  
 
 
Assignee: 
 Amitkumar Ghatwal Oleg Nenashev  
 

  
 
 
 
 

 
 
 

 
 
 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-38652) To create a JobRestriction's NodeProperty and adding it to the node via a groovy code

[amitkumar_ghat...@persistent.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Amitkumar Ghatwal created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38652  
 
 
  To create a JobRestriction's NodeProperty and adding it to the node via a groovy code   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Amitkumar Ghatwal  
 
 
Attachments: 
 job-restriction plugin.doc  
 
 
Components: 
 job-restrictions-plugin  
 
 
Created: 
 2016/Oct/03 5:18 AM  
 
 
Environment: 
 Jenkins version 2.10 , Job Restrictions Plugin version 0.5  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Amitkumar Ghatwal  
 

  
 
 
 
 

 
 Hi All , I have the below groovy code which creates a slave node import jenkins.model.* import hudson.model.* import hudson.slaves.* import hudson.plugins.sshslaves.* println "create a slave node.. \n\r" Slave slave_node = new DumbSlave(  "My_Slave_Node_Autogenerated", "This slave node is generated using a jenkins job via groovy script", "/home/jenkins", "1", Node.Mode.NORMAL, SLAVE_NODE_LABEL, new SSHLauncher(SLAVE_IP_ADDR,22,SLAVE_LOGIN,SLAVE_PWD,"","","","",""), new RetentionStrategy.Always(), new LinkedList() ) Jenkins.instance.addNode(slave_node) Which groovy steps should I adding to above groovy script to create below changes (attached) for slave node configuration as shown in the pic below Any pointers how to enable "restrict jobs execution at node " for the above create slave node using groovy script . Please assign this ticket to : Oleg Nenashev  as he requested by him. Hi Oleg, Could you please help in assisting me in giving those groovy steps by which I can create/edit the node properties for any newly created slave node ,via "Restrict jobs execution at node " as shown in the attached document. Thanks, 

[JIRA] (JENKINS-38601) Cannot mark Multibranch Pipeline as Favorite in Blue Ocean

[jdu...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-38601  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot mark Multibranch Pipeline as Favorite in Blue Ocean   
 

  
 
 
 
 

 
 I think at the very least we can make this fail without an error in the console and pop up a toast to say that we couldn't favorite the pipeline as master branch does not exist?  
 

  
 
 
 
 

 
 
 

 
 
 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-38601) Cannot mark Multibranch Pipeline as Favorite in Blue Ocean

[jdu...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-38601  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot mark Multibranch Pipeline as Favorite in Blue Ocean   
 

  
 
 
 
 

 
 Eventually we want the default branch name to be whatever the upstreams "default branch" is (both Github and Bitbucket share a default branch concept). I didn't understand what your expected behavior should be in this case - did you mean we should disable the favoriting button if the master branch does not exist?  
 

  
 
 
 
 

 
 
 

 
 
 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-37837) Regression: JWT token not present when logged in on blueocean.io

[vivek.pan...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey stopped work on  JENKINS-37837  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-37667) Use ForkScanner to build DAG (ie adapt to bismuth api)

[vivek.pan...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey started work on  JENKINS-37667  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-35821) API to return per node averages, and ETA based on history of execution

[vivek.pan...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey commented on  JENKINS-35821  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: API to return per node averages, and ETA based on history of execution   
 

  
 
 
 
 

 
 Michael Neale Bismuth API gives basic structure to parse executed flow nodes in SAX like parser, it also gives structure for timing info. Lets keep this ticket open as we need to implement these functionalities in blueocean api.  
 

  
 
 
 
 

 
 
 

 
 
 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-38506) Invalid workspace path for pipeline jobs on jenkins master

[fah...@cliqz.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Faheem Nadeem updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38506  
 
 
  Invalid workspace path for pipeline jobs on jenkins master   
 

  
 
 
 
 

 
Change By: 
 Faheem Nadeem  
 

  
 
 
 
 

 
 There seems to be a recent change in strategy on how folders are organized in workspace folder on Jenkins master for first stage SCM checkouts from multibranch jobs. Previously they used to be nested folders now they are not.   My problem is ,  there  is  seems to be  a  size limit on the workspace subfolder name and you are cropping the git repository name, which is causing some maintenance problems. e.g.A pull request to a Git repository name '_navigation extension_' is cropped to some thing like this:{code:none}avigation-extension_PR-2464-KJBGB3QGPGBXAOYPEHJ33MLLSHZ5D7E5YXNLYLFVQGYPXWOKA4CQ@script{code}Another one '_aws-infrastructure-data_' is something like:{code:none}-infrastructure-data_master-O7PVEBG7YU24BDNRZTSG3VBPTCGPVWE5PF2OZ35TBWNASAJB2OOA@script{code}so naturally you cannot do something like:{code:none}$ cd -infrastructure-data_master-O7PVEBG7YU24BDNRZTSG3VBPTCGPVWE5PF2OZ35TBWNASAJB2OOA@script-bash: cd: -i: invalid optioncd: usage: cd [-L|[-P [-e]] [-@]] [dir]{code} Secondly, the path seems to be too long which can also create some problems.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 

[JIRA] (JENKINS-38506) Invalid workspace path for pipeline jobs on jenkins master

[archie_ba...@hotmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Archibald updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38506  
 
 
  Invalid workspace path for pipeline jobs on jenkins master   
 

  
 
 
 
 

 
Change By: 
 Nick Archibald  
 
 
Priority: 
 Minor Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38506) Invalid workspace path for pipeline jobs on jenkins master

[archie_ba...@hotmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Archibald edited a comment on  JENKINS-38506  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Invalid workspace path for pipeline jobs on jenkins master   
 

  
 
 
 
 

 
 This problem is causing a problem on windows machines as the path is now too long to check out all the code and restore nuget, npm and bower packages. It also looks like the change has broken the use of the 'Workspace Root Directory' configuration as none of the code is being checked out to the provided directory it is just being checked out to the default Jenkins workspace path. So in short my Companies build environment is now broken :-(  
 

  
 
 
 
 

 
 
 

 
 
 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-38506) Invalid workspace path for pipeline jobs on jenkins master

[archie_ba...@hotmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Archibald commented on  JENKINS-38506  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Invalid workspace path for pipeline jobs on jenkins master   
 

  
 
 
 
 

 
 This problem is causing a problem on windows machines as the path is now too long to check out all the code and restore nuget, npm and bower packages. It also looks like the change has broken the use of the 'Workspace Root Directory' configuration as none of the code is being checked out to the provided directory it is just being checked out to the default Jenkins workspace path.  
 

  
 
 
 
 

 
 
 

 
 
 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-37289) authentication issue instant is too old or in the future

[benjamin.j.mcc...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ben McCann resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37289  
 
 
  authentication issue instant is too old or in the future   
 

  
 
 
 
 

 
Change By: 
 Ben McCann  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-37289) authentication issue instant is too old or in the future

[benjamin.j.mcc...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ben McCann commented on  JENKINS-37289  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: authentication issue instant is too old or in the future   
 

  
 
 
 
 

 
 Thank you for that pointer. I just released plugin version 0.12 if you'd like to give it a try  
 

  
 
 
 
 

 
 
 

 
 
 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-38651) Actions created by TransientActionFactory are not displayed in Label view

[vinc...@latombe.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vincent Latombe updated  JENKINS-38651  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38651  
 
 
  Actions created by TransientActionFactory are not displayed in Label view   
 

  
 
 
 
 

 
Change By: 
 Vincent Latombe  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38651) Actions created by TransientActionFactory are not displayed in Label view

[vinc...@latombe.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vincent Latombe updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38651  
 
 
  Actions created by TransientActionFactory are not displayed in Label view   
 

  
 
 
 
 

 
Change By: 
 Vincent Latombe  
 

  
 
 
 
 

 
 Label#index.jelly refers to $ \ {it.actions} which is deprecated and doesn't include actions created through TransientActionFactory implementations.  
 

  
 
 
 
 

 
 
 

 
 
 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-38651) Actions created by TransientActionFactory are not displayed in Label view

[vinc...@latombe.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vincent Latombe started work on  JENKINS-38651  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Vincent Latombe  
 
 
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-38651) Actions created by TransientActionFactory are not displayed in Label view

[vinc...@latombe.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vincent Latombe created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38651  
 
 
  Actions created by TransientActionFactory are not displayed in Label view   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2016/Oct/02 4:15 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Vincent Latombe  
 

  
 
 
 
 

 
 Label#index.jelly refers to $ {it.actions}  which is deprecated and doesn't include actions created through TransientActionFactory implementations.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA 

[JIRA] (JENKINS-38651) Actions created by TransientActionFactory are not displayed in Label view

[vinc...@latombe.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vincent Latombe assigned an issue to Vincent Latombe  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38651  
 
 
  Actions created by TransientActionFactory are not displayed in Label view   
 

  
 
 
 
 

 
Change By: 
 Vincent Latombe  
 
 
Assignee: 
 Vincent Latombe  
 

  
 
 
 
 

 
 
 

 
 
 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-38481) AWS method change causes too many slaves to be launched

[pe...@reidweb.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Reid commented on  JENKINS-38481  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: AWS method change causes too many slaves to be launched   
 

  
 
 
 
 

 
 OK, cool. Just wanted clarification on that.  
 

  
 
 
 
 

 
 
 

 
 
 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-38481) AWS method change causes too many slaves to be launched

[franc...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Francis Upton commented on  JENKINS-38481  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: AWS method change causes too many slaves to be launched   
 

  
 
 
 
 

 
 Generally we close the issue when the release is made. The release has been made and will be available in the next 24 hours in the repo, this action is automatic. You can see the release in the source repository: https://github.com/jenkinsci/ec2-plugin/releases  
 

  
 
 
 
 

 
 
 

 
 
 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-38481) AWS method change causes too many slaves to be launched

[pe...@reidweb.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Reid commented on  JENKINS-38481  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: AWS method change causes too many slaves to be launched   
 

  
 
 
 
 

 
 The release for this issue has not yet been released - can you please re-open this issue until the fix is available in the plugin repository.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38481) AWS method change causes too many slaves to be launched

[franc...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Francis Upton closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fixed in release 1.36.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-38481  
 
 
  AWS method change causes too many slaves to be launched   
 

  
 
 
 
 

 
Change By: 
 Francis Upton  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38481) AWS method change causes too many slaves to be launched

[franc...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Francis Upton updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38481  
 
 
  AWS method change causes too many slaves to be launched   
 

  
 
 
 
 

 
Change By: 
 Francis Upton  
 
 
Summary: 
 Error while launching new ec2 slave AWS method change causes too many slaves to be launched  
 

  
 
 
 
 

 
 
 

 
 
 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-38650) Typos in CLI commands: "comama-separated"

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev started work on  JENKINS-38650  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
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-38650) Typos in CLI commands: "comama-separated"

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev assigned an issue to Oleg Nenashev  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38650  
 
 
  Typos in CLI commands: "comama-separated"   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Assignee: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 
 

 
 
 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-38650) Typos in CLI commands: "comama-separated"

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38650  
 
 
  Typos in CLI commands: "comama-separated"   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 Screen Shot 2016-10-02 at 17.38.04.png  
 
 
Components: 
 core  
 
 
Created: 
 2016/Oct/02 3:43 PM  
 
 
Environment: 
 jenkins-2.22  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 Just noticed several glitches in CLI descriptions during the management script development.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
   

[JIRA] (JENKINS-38650) Typos in CLI commands: "comama-separated"

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38650  
 
 
  Typos in CLI commands: "comama-separated"   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Component/s: 
 cli  
 

  
 
 
 
 

 
 
 

 
 
 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-38649) Add support to Job-dsl

[luigi.tagliamont...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Luigi Tagliamonte created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38649  
 
 
  Add support to Job-dsl   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Kirill Merkushev  
 
 
Components: 
 github-plugin  
 
 
Created: 
 2016/Oct/02 3:28 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Luigi Tagliamonte  
 

  
 
 
 
 

 
 Would be great to add support for JobDSL plugin. I use JobDSL to generate a jenkins job for the branches of my project, would be great to automatically add github commit status to all generated jobs.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by 

[JIRA] (JENKINS-38481) Error while launching new ec2 slave

[scm_issue_l...@java.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-38481  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Error while launching new ec2 slave   
 

  
 
 
 
 

 
 Code changed in jenkins User: Nicolas De Loof Path: pom.xml src/test/java/hudson/plugins/ec2/SlaveTemplateUnitTest.java http://jenkins-ci.org/commit/ec2-plugin/c8983e4a8c3b784ae5a9a58127c88f3013db490d Log: JENKINS-38481 1.11.37 changed com.amazonaws.services.ec2.AmazonEC2#createTags return type, so incompatible binary change  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-37289) authentication issue instant is too old or in the future

[tomi.pakari...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tomi Pakarinen commented on  JENKINS-37289  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: authentication issue instant is too old or in the future   
 

  
 
 
 
 

 
 It seems that jenkins maven repository url have changed.. https://groups.google.com/d/msg/jenkinsci-dev/qn486AYUVWk/P-t0U8hGCQAJ https://issues.jenkins-ci.org/browse/INFRA-588  
 

  
 
 
 
 

 
 
 

 
 
 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-38534) ProcessKillingVeto.all() forces Jenkins class to be instantiated on remote agents

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38534  
 
 
  ProcessKillingVeto.all() forces Jenkins class to be instantiated on remote agents   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Issue Type: 
 Improvement Bug  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38534) ProcessKillingVeto.all() forces Jenkins class to be instantiated on remote agents

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-38534  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ProcessKillingVeto.all() forces Jenkins class to be instantiated on remote agents   
 

  
 
 
 
 

 
 I'd rather consider it as a bug  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38390) Timestamp background color white

[stevengbr...@java.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Steven G Brown commented on  JENKINS-38390  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Timestamp background color white   
 

  
 
 
 
 

 
 I'm at a loss. Any ideas how to fix this without reintroducing JENKINS-34019 ?  
 

  
 
 
 
 

 
 
 

 
 
 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-38648) Allow sorting of generated jobs on summary page

[rob.kie...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Kielty created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38648  
 
 
  Allow sorting of generated jobs on summary page   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Rob Kielty  
 
 
Components: 
 job-dsl-plugin  
 
 
Created: 
 2016/Oct/02 12:10 PM  
 
 
Labels: 
 job-dsl-plugin improvement  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Rob Kielty  
 

  
 
 
 
 

 
 Sorts alphabetically the list of Generated Jobs on the Summary Page of a seed job   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 
 

[JIRA] (JENKINS-38134) Generate checksums for war, Windows and OS X distributables

[scm_issue_l...@java.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-38134  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Generate checksums for war, Windows and OS X distributables   
 

  
 
 
 
 

 
 Code changed in jenkins User: Daniel Beck Path: Makefile msi/publish.sh osx/publish.sh setup.mk http://jenkins-ci.org/commit/packaging/2ab413be28a67b15413e65116c719c971fa8f145 Log: Revert "JENKINS-38134 Generate shasum for war, windows and osx installers" This reverts commit 916f556aad4d6fbbc7c8044c3056005cb29f652f.  
 

  
 
 
 
 

 
 
 

 
 
 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-38134) Generate checksums for war, Windows and OS X distributables

[scm_issue_l...@java.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-38134  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Generate checksums for war, Windows and OS X distributables   
 

  
 
 
 
 

 
 Code changed in jenkins User: Daniel Beck Path: Makefile msi/publish.sh osx/publish.sh setup.mk http://jenkins-ci.org/commit/packaging/6ebdddca9e01bd8896fc2c829bce4bd7f34218b4 Log: Merge pull request #74 from daniel-beck/revert-69 Revert "JENKINS-38134 Generate shasum for war, windows and osx inst… Compare: https://github.com/jenkinsci/packaging/compare/298a4ca518a1...6ebdddca9e01  
 

  
 
 
 
 

 
 
 

 
 
 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-38481) Error while launching new ec2 slave

[chriskulin...@yahoo.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Kulinski commented on  JENKINS-38481  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Error while launching new ec2 slave   
 

  
 
 
 
 

 
 We also had this issue. Spun up slaves until we hit our EC2 instance cap. Not fun. Tested the PR fix linked above and it solved the problem. Release this fix soon!  
 

  
 
 
 
 

 
 
 

 
 
 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-38390) Timestamp background color white

[stevengbr...@java.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Steven G Brown commented on  JENKINS-38390  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Timestamp background color white   
 

  
 
 
 
 

 
 Another example can be found here: JENKINS-38573.  
 

  
 
 
 
 

 
 
 

 
 
 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-38573) Timestamp CSS style is problematic

[stevengbr...@java.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Steven G Brown resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Thanks for reporting.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-38573  
 
 
  Timestamp CSS style is problematic   
 

  
 
 
 
 

 
Change By: 
 Steven G Brown  
 
 
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-38085) Settings not appearing in the sidebar

[stevengbr...@java.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Steven G Brown commented on  JENKINS-38085  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Settings not appearing in the sidebar   
 

  
 
 
 
 

 
 
 
Confirmed, although it appears the timestamps now render in inverted colors (black text on white), which is distracting to the eye.
 This has been raised as JENKINS-38573.  
 

  
 
 
 
 

 
 
 

 
 
 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-38643) Organize pom for simple dependency management

[axmetishe+jenkins...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eugene Ahmethanov resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 https://github.com/jenkinsci/git-parameter-plugin/pull/39  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-38643  
 
 
  Organize pom for simple dependency management   
 

  
 
 
 
 

 
Change By: 
 Eugene Ahmethanov  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38647) Vault Key Not Saved In Vault Error Messaging

[grose.matth...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 mg updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38647  
 
 
  Vault Key Not Saved In Vault Error Messaging   
 

  
 
 
 
 

 
Change By: 
 mg  
 

  
 
 
 
 

 
 failure with "com.bettercloud.vault.VaultException: com.bettercloud.vault.VaultException: Vault responded with HTTP status code: 404" if any of the requested keys aren't present in the vault.  Given this causes a hard failure, to  help  streamline debugging or necessary communication on what keys are missing would believe we'd prefer a more descriptive message   
 

  
 
 
 
 

 
 
 

 
 
 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-38646) Using credentials plugin for authentication token

[grose.matth...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 mg commented on  JENKINS-38646  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Using credentials plugin for authentication token   
 

  
 
 
 
 

 
 marking as major unless corrected this was intentional.  
 

  
 
 
 
 

 
 
 

 
 
 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-38646) Using credentials plugin for authentication token

[grose.matth...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 mg updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38646  
 
 
  Using credentials plugin for authentication token   
 

  
 
 
 
 

 
Change By: 
 mg  
 
 
Priority: 
 Minor Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38647) Vault Key Not Saved In Vault Error Messaging

[grose.matth...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 mg created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38647  
 
 
  Vault Key Not Saved In Vault Error Messaging   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Peter Tierno  
 
 
Components: 
 hashicorp-vault-plugin  
 
 
Created: 
 2016/Oct/02 6:17 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 mg  
 

  
 
 
 
 

 
 failure with "com.bettercloud.vault.VaultException: com.bettercloud.vault.VaultException: Vault responded with HTTP status code: 404" if any of the requested keys aren't present in the vault. Given this causes a hard failure, to streamline debugging or necessary communication on what keys are missing would believe we'd prefer a more descriptive message   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
   

[JIRA] (JENKINS-38646) Using credentials plugin for authentication token

[grose.matth...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 mg updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38646  
 
 
  Using credentials plugin for authentication token   
 

  
 
 
 
 

 
Change By: 
 mg  
 
 
Issue Type: 
 Improvement New Feature  
 

  
 
 
 
 

 
 
 

 
 
 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.