[JIRA] (JENKINS-47130) EC2 plugin 1.37 fails to provision previously defined slaves

2018-03-12 Thread franc...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Francis Upton closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-47130  
 
 
  EC2 plugin 1.37 fails to provision previously defined slaves   
 

  
 
 
 
 

 
Change By: 
 Francis Upton  
 
 
Status: 
 In Progress Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-47130) EC2 plugin 1.37 fails to provision previously defined slaves

2018-03-12 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-47130  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: EC2 plugin 1.37 fails to provision previously defined slaves   
 

  
 
 
 
 

 
 Code changed in jenkins User: Francis Upton IV Path: src/main/java/hudson/plugins/ec2/EC2Cloud.java src/main/java/hudson/plugins/ec2/EC2Step.java src/main/java/hudson/plugins/ec2/SlaveTemplate.java src/test/java/hudson/plugins/ec2/EC2StepTest.java http://jenkins-ci.org/commit/ec2-plugin/affb7f407cd024accdf4e9093b07efada117814d Log: JENKINS-50105 EC2 Step provisioning incorrectly specifies a label (#268) JENKINS-47130 EC2 plugin 1.37 fails to provision previously defined slaves  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-47130) EC2 plugin 1.37 fails to provision previously defined slaves

2018-03-11 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-47130  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: EC2 plugin 1.37 fails to provision previously defined slaves   
 

  
 
 
 
 

 
 Code changed in jenkins User: Francis Upton IV Path: src/main/java/hudson/plugins/ec2/EC2Cloud.java src/main/java/hudson/plugins/ec2/EC2Step.java src/main/java/hudson/plugins/ec2/SlaveTemplate.java src/test/java/hudson/plugins/ec2/EC2StepTest.java http://jenkins-ci.org/commit/ec2-plugin/a80c336bfc12ee28828981bdceae88842daabb07 Log: JENKINS-50105 EC2 Step provisioning incorrectly specifies a label JENKINS-47130 EC2 plugin 1.37 fails to provision previously defined slaves  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-47130) EC2 plugin 1.37 fails to provision previously defined slaves

2018-03-11 Thread franc...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Francis Upton commented on  JENKINS-47130  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: EC2 plugin 1.37 fails to provision previously defined slaves   
 

  
 
 
 
 

 
 I see the problem here. This was caused by the "node" field that was added to the SlaveTemplate https://github.com/jenkinsci/ec2-plugin/pull/232. The initial value of "node" was set to "true", allowing it to be provisioned normally. However, any serialized SlaveTemplates would (incorrectly) have the value of "false" which caused them to be ignored during the normal provisioning. The work of the PR did not consider this case.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-47130) EC2 plugin 1.37 fails to provision previously defined slaves

2018-03-11 Thread franc...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Francis Upton updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-47130  
 
 
  EC2 plugin 1.37 fails to provision previously defined slaves   
 

  
 
 
 
 

 
Change By: 
 Francis Upton  
 
 
Summary: 
 EC2 plugin 1.37  does not start stopped instances when provisionning  fails to provision previously defined slaves  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





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