[JIRA] [ec2-plugin] (JENKINS-32088) Timed out after 0 seconds of waiting for winrm
Title: Message Title Francis Upton resolved as Fixed Jenkins / JENKINS-32088 Timed out after 0 seconds of waiting for winrm Change By: Francis Upton Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-32088) Timed out after 0 seconds of waiting for winrm
Title: Message Title Francis Upton closed an issue as Fixed Jenkins / JENKINS-32088 Timed out after 0 seconds of waiting for winrm Change By: Francis Upton Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-31804) After a while the ec2-plugin stops spinning up nodes, and spits out stacktraces. It also stops terminating nodes after their idle time
Title: Message Title Francis Upton assigned an issue to Kohsuke Kawaguchi Moving to Jenkins core, does not look like ec2 plugin issue (how do I pick who to assign this to in core)? Jenkins / JENKINS-31804 After a while the ec2-plugin stops spinning up nodes, and spits out stacktraces. It also stops terminating nodes after their idle time Change By: Francis Upton Assignee: Francis Upton Kohsuke Kawaguchi Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31183) System configuration return java.lang.NullPointerException
Title: Message Title Francis Upton assigned an issue to Kohsuke Kawaguchi Jenkins / JENKINS-31183 System configuration return java.lang.NullPointerException Change By: Francis Upton Assignee: Francis Upton Kohsuke Kawaguchi Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-5516) NPE in Amazon EC2 plugin
Title: Message Title Francis Upton closed an issue as Cannot Reproduce Ancient issue, closing. Jenkins / JENKINS-5516 NPE in Amazon EC2 plugin Change By: Francis Upton Status: Open Closed Assignee: Kohsuke Kawaguchi Francis Upton Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26493) Use new EC2 API endpoint hostnames
Title: Message Title Francis Upton resolved as Fixed To be released in 1.30 Jenkins / JENKINS-26493 Use new EC2 API endpoint hostnames Change By: Francis Upton Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-30527) After Jenkins restart existing on-demand EC2 slaves can't be used
Title: Message Title Francis Upton resolved as Duplicate I think this is a dup of JENKINS-23787 Jenkins / JENKINS-30527 After Jenkins restart existing on-demand EC2 slaves can't be used Change By: Francis Upton Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26493) Use new EC2 API endpoint hostnames
Title: Message Title Francis Upton commented on JENKINS-26493 Re: Use new EC2 API endpoint hostnames Can you verify this is working in the current (1.30) snapshot, and then I can release it? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-27601) instance caps incorrectly calculated
Title: Message Title Francis Upton commented on JENKINS-27601 Re: instance caps incorrectly calculated Can you try out the snapshot and see if it works for you (there were other problems with it that prevented me from doing a release)? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-23787) EC2-plugin not spooling up stopped nodes - "still in the queue ... all nodes of label ... are offline"
Title: Message Title Francis Upton resolved as Fixed Should be released in 1.30 Jenkins / JENKINS-23787 EC2-plugin not spooling up stopped nodes - "still in the queue ... all nodes of label ... are offline" Change By: Francis Upton Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-23787) EC2-plugin not spooling up stopped nodes - "still in the queue ... all nodes of label ... are offline"
Title: Message Title Francis Upton commented on JENKINS-23787 Re: EC2-plugin not spooling up stopped nodes - "still in the queue ... all nodes of label ... are offline" I believe I have now fixed this. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26493) Use new EC2 API endpoint hostnames
Title: Message Title Francis Upton commented on JENKINS-26493 Re: Use new EC2 API endpoint hostnames I have made the fix. I can't make a release at the moment because there is another critical bug in the unreleased version that I have to fix. I will try and get to it soon. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26493) Use new EC2 API endpoint hostnames
Title: Message Title Francis Upton commented on JENKINS-26493 Re: Use new EC2 API endpoint hostnames I don't understand why these have to be wired into the code? Can someone help me here? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26493) Use new EC2 API endpoint hostnames
Title: Message Title Francis Upton commented on JENKINS-26493 Re: Use new EC2 API endpoint hostnames No worries about the assignee. I have finally begun to look at this a bit and have commented on a previous pull request (https://github.com/jenkinsci/ec2-plugin/pull/161) that also claims to fix this (along with addressing the s3 hostnames [though it's unclear that that's required]). Hopefully we will get that other pull request in in the next day or so. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-23787) EC2-plugin not spooling up stopped nodes - "still in the queue ... all nodes of label ... are offline"
Title: Message Title Francis Upton commented on JENKINS-23787 Re: EC2-plugin not spooling up stopped nodes - "still in the queue ... all nodes of label ... are offline" @Ted, I don't see how that line broke it. Note that I changed EC2Cloud to look up any running (or pending) instances and check that they are known. Only if they are known will they count against the existing instances. I will test it again though, to try multiple instances with the same AMI. The reason the filter was removed is that we want to see if there is a running instance that's not known, and if so, use that one. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26493) Use new EC2 API endpoint hostnames
Title: Message Title Francis Upton commented on JENKINS-26493 Re: Use new EC2 API endpoint hostnames Sorry about the delay, I will have a look at this in the next day or so. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-23787) EC2-plugin not spooling up stopped nodes - "still in the queue ... all nodes of label ... are offline"
Title: Message Title Francis Upton commented on JENKINS-23787 Re: EC2-plugin not spooling up stopped nodes - "still in the queue ... all nodes of label ... are offline" I have just made a fix for this in unreleased 1.30, if you can get the SNAPSHOT version of the ec2-plugin, hopefully this is fixed. Please give it and try and let me know. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-23787) EC2-plugin not spooling up stopped nodes - "still in the queue ... all nodes of label ... are offline"
Title: Message Title Francis Upton commented on JENKINS-23787 Re: EC2-plugin not spooling up stopped nodes - "still in the queue ... all nodes of label ... are offline" Thanks for letting me know. I will close this one and reopen my duplicated report, as that has to do with hooking up to EC2 instances that are actually running (even though the corresponding Jenkins slave is offline). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-30213) Existing running on-demand instance not seen
Title: Message Title Francis Upton closed an issue as Duplicate Jenkins / JENKINS-30213 Existing running on-demand instance not seen Change By: Francis Upton Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-30213) Existing running on-demand instance not seen
Title: Message Title Francis Upton resolved as Duplicate JENKINS-23787 Jenkins / JENKINS-30213 Existing running on-demand instance not seen Change By: Francis Upton Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-30147) EC2 Key Pair's Private Key isn't stored correctly in config.xml file
Title: Message Title Francis Upton closed an issue as Incomplete Jenkins / JENKINS-30147 EC2 Key Pair's Private Key isn't stored correctly in config.xml file Change By: Francis Upton Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-30147) EC2 Key Pair's Private Key isn't stored correctly in config.xml file
Title: Message Title Francis Upton commented on JENKINS-30147 Re: EC2 Key Pair's Private Key isn't stored correctly in config.xml file The private key as stored in the config.xml file is an encrypted version (which is also used for the secret key). This mechanism has been working fine for a long time, so I'm not sure what's going on in your environment. If you can provide some steps to reproduce your exact problem, please reopen this bug report. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-30147) EC2 Key Pair's Private Key isn't stored correctly in config.xml file
Title: Message Title Francis Upton resolved as Incomplete See my previous comments. Jenkins / JENKINS-30147 EC2 Key Pair's Private Key isn't stored correctly in config.xml file Change By: Francis Upton Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-30213) Existing running on-demand instance not seen
Title: Message Title Francis Upton reopened an issue Not the same issue as the other one. Jenkins / JENKINS-30213 Existing running on-demand instance not seen Change By: Francis Upton Resolution: Duplicate Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-30208) Can't launch spot slave instance with aws-java-sdk 1.10.*
Title: Message Title Francis Upton resolved as Cannot Reproduce Can you check that your access Id and secret key are in fact correct? I know you can't look at your secret key as stored, but you can recopy it. Perhaps something happened to it in your config.xml file? I have been working with the SNAPSHOT version with the 1.10.2 API for on-depend instances and it's working fine (spot instances use the same mechanism). The particular error message you are getting simply indicates the access id/secret key are somehow wrong. If you are satisfied that your keys are right and have steps to reproduce this from a clean Jenkins/EC2 environment, please reopen this. Jenkins / JENKINS-30208 Can't launch spot slave instance with aws-java-sdk 1.10.* Change By: Francis Upton Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [ec2-plugin] (JENKINS-30208) Can't launch spot slave instance with aws-java-sdk 1.10.*
Title: Message Title Francis Upton closed an issue as Cannot Reproduce Jenkins / JENKINS-30208 Can't launch spot slave instance with aws-java-sdk 1.10.* Change By: Francis Upton Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-30213) Existing running on-demand instance not seen
Title: Message Title Francis Upton created an issue Jenkins / JENKINS-30213 Existing running on-demand instance not seen Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 30/Aug/15 9:36 AM Priority: Major Reporter: Francis Upton If an existing provisioned instance is running, and I start a job to use that instance, the instance will not be used. But it will not attempt to start a new instance. Here is what the log says: Aug 30, 2015 1:55:22 AM INFO hudson.plugins.ec2.EC2Cloud provision Excess workload after pending Spot instances: 1 Aug 30, 2015 1:55:23 AM INFO hudson.plugins.ec2.EC2Cloud addProvisionedSlave AMI Instance cap of 1 reached for ami ami-b7745bf2, not provisioning. Aug 30, 2015 1:55:32 AM INFO hudson.plugins.ec2.EC2Cloud provision Excess workload after pending Spot instances: 1 Aug 30, 2015 1:55:33 AM INFO hudson.plugins.ec2.EC2Cloud addProvisionedSlave AMI Instance cap of 1 reached for ami ami-b7745bf2, not provisioning. FeedAll SEVERE WARNING
[JIRA] [ec2-plugin] (JENKINS-30213) Existing running on-demand instance not seen
Title: Message Title Francis Upton commented on JENKINS-30213 Re: Existing running on-demand instance not seen This can happen if the instance is started by EC2 after having been stopped by Jenkins previously. It can also happen after the instance was disconnected by Jenkins. In either case, it is counted against the instance cap for the AMIs (and the total instance cap). But its associated slave is not connected to is and is showing as unavailable. The solution is probably to detect is the slave is unavailable but the instance is running (or starting presumably). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-29983) Region list not populating
Title: Message Title Francis Upton commented on JENKINS-29983 Re: Region list not populating OK, I'm not sure the best way to solve this. The way it used to work is the list of regions was hardcoded, and this change was made to make it dynamic. My idea at this point is that since your case is fairly rare we could probably solve the problem by better error reporting. SO when the region list cannot be populated, we could indicate a message that we can't get the region list because of access problems to the region we are trying (if the region was not previously specified, would be us-east-1) an suggest the permissions be checked. We could also have the errors in test connection more clearly indicate that the things that worked (the access key id for example in your case) and that the private key did not work - and what region was tried. What do you think? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-29983) Region list not populating when unable to access us-east-1 region
Title: Message Title Francis Upton updated an issue Jenkins / JENKINS-29983 Region list not populating when unable to access us-east-1 region Change By: Francis Upton Summary: Regionlistnotpopulating whenunabletoaccessus-east-1region Priority: Blocker Minor Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-29983) Region list not populating
Title: Message Title Francis Upton commented on JENKINS-29983 Re: Region list not populating Yes, I think that must be right (and bad). I'm surprised that we have not had this problem reported in the past because this mechanism has been in place for years now. So I wonder if something else might be going on. I don't remember much about how the access key id is bound to regions, is it typical that you have permissions on only one region? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-29983) Region list not populating when unable to access us-east-1 region
Title: Message Title Francis Upton commented on JENKINS-29983 Re: Region list not populating when unable to access us-east-1 region Another solution is to allow a field to select the region if the region is not shown on the list. It would be a text field where you can put what you like in. This could be used in the case where the list could not be populated. It's a little confusing, but I don't think it will be that bad. What's your opinion about that? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26493) Use new EC2 API endpoint hostnames
Title: Message Title Francis Upton resolved as Duplicate https://issues.jenkins-ci.org/browse/JENKINS-26854 Jenkins / JENKINS-26493 Use new EC2 API endpoint hostnames Change By: Francis Upton Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-29983) Region list not populating
Title: Message Title Francis Upton commented on JENKINS-29983 Re: Region list not populating It does pick a default region when doing a test connection (us-east-1). The region list is populated based on access to the default region to get the list, and it has to use the access key Id and secret access key to do so. The private key is not required. To troubleshoot this further, I would delete the private key and try the test connection again. And look in the log to see what's happening. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26854) EC2 slave launch stops working after a while with AmazonServiceException Request has expired
Title: Message Title Francis Upton resolved as Fixed Jenkins / JENKINS-26854 EC2 slave launch stops working after a while with AmazonServiceException Request has expired Change By: Francis Upton Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26854) EC2 slave launch stops working after a while with AmazonServiceException Request has expired
Title: Message Title Francis Upton closed an issue as Fixed Fixed in 1.28. Jenkins / JENKINS-26854 EC2 slave launch stops working after a while with AmazonServiceException Request has expired Change By: Francis Upton Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26854) EC2 slave launch stops working after a while with AmazonServiceException Request has expired
Title: Message Title Francis Upton commented on JENKINS-26854 Re: EC2 slave launch stops working after a while with AmazonServiceException Request has expired I think the release actually worked this time, so by tomorrow it should be present on the wiki page and available. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26854) EC2 slave launch stops working after a while with AmazonServiceException Request has expired
Title: Message Title Francis Upton commented on JENKINS-26854 Re: EC2 slave launch stops working after a while with AmazonServiceException Request has expired @Ximon, I had intended to do the release and I think something went wrong. I will try to fix this today. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-28003) ec2-plugin breaks with BouncyCastle 1.50
Francis Upton resolved JENKINS-28003 as Fixed ec2-plugin breaks with BouncyCastle 1.50 https://github.com/jenkinsci/ec2-plugin/pull/145 Change By: Francis Upton (20/Apr/15 3:31 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-28003) ec2-plugin breaks with BouncyCastle 1.50
Francis Upton closed JENKINS-28003 as Fixed ec2-plugin breaks with BouncyCastle 1.50 Change By: Francis Upton (20/Apr/15 3:31 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-6691) EC2 plugin will launch more instances than cap allows if enough jobs are queued up while no instances are active
Francis Upton closed JENKINS-6691 as Fixed EC2 plugin will launch more instances than cap allows if enough jobs are queued up while no instances are active Change By: Francis Upton (05/Feb/15 5:07 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-6691) EC2 plugin will launch more instances than cap allows if enough jobs are queued up while no instances are active
Francis Upton resolved JENKINS-6691 as Fixed EC2 plugin will launch more instances than cap allows if enough jobs are queued up while no instances are active This appears to be fixed thanks to Mike Bayer mike...@zzzcomputing.com on 10/9/12 6:42 PM Change By: Francis Upton (05/Feb/15 5:07 AM) Status: Open Resolved Assignee: KohsukeKawaguchi FrancisUpton Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-19845) EC2 plugin incorrectly reports current instance count
Francis Upton resolved JENKINS-19845 as Fixed EC2 plugin incorrectly reports current instance count Change By: Francis Upton (05/Feb/15 5:08 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-19845) EC2 plugin incorrectly reports current instance count
Francis Upton closed JENKINS-19845 as Fixed EC2 plugin incorrectly reports current instance count Change By: Francis Upton (05/Feb/15 5:08 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26531) Slave does not start if the temp dir is not set to anything after upgrade to 1.25
Francis Upton commented on JENKINS-26531 Slave does not start if the temp dir is not set to anything after upgrade to 1.25 All done, version 1.26 released. Sorry for the trouble. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26531) Slave does not start if the temp dir is not set to anything after upgrade to 1.25
Francis Upton started work on JENKINS-26531 Slave does not start if the temp dir is not set to anything after upgrade to 1.25 Change By: Francis Upton (27/Jan/15 9:14 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26531) Slave does not start if the temp dir is not set to anything after upgrade to 1.25
Francis Upton resolved JENKINS-26531 as Fixed Slave does not start if the temp dir is not set to anything after upgrade to 1.25 Change By: Francis Upton (27/Jan/15 9:14 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26531) Slave does not start if the temp dir is not set to anything after upgrade to 1.25
Francis Upton closed JENKINS-26531 as Fixed Slave does not start if the temp dir is not set to anything after upgrade to 1.25 Change By: Francis Upton (28/Jan/15 12:32 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26531) Weird Could not find /init.sh after update
Francis Upton commented on JENKINS-26531 Weird Could not find /init.sh after update @Hugo, yes, it should probably handle the empty temp dir better. Thanks for looking more deeply. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26531) Slave does not start if the temp dir is not set to anything after upgrade to 1.25
Francis Upton updated JENKINS-26531 Slave does not start if the temp dir is not set to anything after upgrade to 1.25 Change By: Francis Upton (21/Jan/15 7:17 PM) Summary: WeirdCould Slavedoes not find/init.sh startifthetempdirisnotsettoanything after update upgradeto1.25 Priority: Blocker Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26531) Weird Could not find /init.sh after update
Francis Upton commented on JENKINS-26531 Weird Could not find /init.sh after update Is there a stack trace? Can you attach the complete log? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26531) Weird Could not find /init.sh after update
Francis Upton commented on JENKINS-26531 Weird Could not find /init.sh after update Which version are you running? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-21147) Elimiate race condition so plugin can support more than 1 cloud configuration
Francis Upton resolved JENKINS-21147 as Fixed Elimiate race condition so plugin can support more than 1 cloud configuration The fix in this pull request was done. Change By: Francis Upton (01/Jan/15 3:13 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-21147) Elimiate race condition so plugin can support more than 1 cloud configuration
Francis Upton closed JENKINS-21147 as Fixed Elimiate race condition so plugin can support more than 1 cloud configuration Change By: Francis Upton (01/Jan/15 3:13 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-23705) EC2 slave disconnects on longer running builds
Francis Upton updated JENKINS-23705 EC2 slave disconnects on longer running builds Change By: Francis Upton (01/Jan/15 3:21 AM) Priority: Critical Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-23705) EC2 slave disconnects on longer running builds
Francis Upton commented on JENKINS-23705 EC2 slave disconnects on longer running builds @Sean, I run long running builds all the time and have never seen this problem. Can you provide the results of the System Information on the node (which shows the stack traces of everything going on)? Also, can you try Nelson's suggestion? I don't have the ClientAliveInterval set in the /etc/ssh/sshd_config file. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-15609) New created EC2 instance SCP Error
Francis Upton updated JENKINS-15609 New created EC2 instance SCP Error Downgrading to minor since it it's quite old and intermittent. Change By: Francis Upton (29/Dec/14 5:50 AM) Priority: Critical Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-16884) EC2 plugin starts too many slave nodes
Francis Upton closed JENKINS-16884 as Fixed EC2 plugin starts too many slave nodes Change By: Francis Upton (29/Dec/14 6:11 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-16485) Plugin throws exception in dev mode.
Francis Upton resolved JENKINS-16485 as Cannot Reproduce Plugin throws exception in dev mode. This has been working fine for me. Change By: Francis Upton (29/Dec/14 6:10 AM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-16485) Plugin throws exception in dev mode.
Francis Upton closed JENKINS-16485 as Cannot Reproduce Plugin throws exception in dev mode. Change By: Francis Upton (29/Dec/14 6:11 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-16884) EC2 plugin starts too many slave nodes
Francis Upton resolved JENKINS-16884 as Fixed EC2 plugin starts too many slave nodes Change By: Francis Upton (29/Dec/14 6:11 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-20353) EC2 plugin forgets about some instances it launched when Jenkins restarts
Francis Upton resolved JENKINS-20353 as Cannot Reproduce EC2 plugin forgets about some instances it launched when Jenkins restarts Change By: Francis Upton (29/Dec/14 6:26 AM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-20353) EC2 plugin forgets about some instances it launched when Jenkins restarts
Francis Upton closed JENKINS-20353 as Cannot Reproduce EC2 plugin forgets about some instances it launched when Jenkins restarts Change By: Francis Upton (29/Dec/14 6:27 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26232) Make temporary directory configurable
Francis Upton created JENKINS-26232 Make temporary directory configurable Issue Type: New Feature Assignee: Francis Upton Components: ec2-plugin Created: 27/Dec/14 8:40 AM Project: Jenkins Priority: Minor Reporter: Francis Upton This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26232) Make temporary directory configurable
Francis Upton closed JENKINS-26232 as Fixed Make temporary directory configurable Change By: Francis Upton (27/Dec/14 6:01 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26232) Make temporary directory configurable
Francis Upton resolved JENKINS-26232 as Fixed Make temporary directory configurable Change By: Francis Upton (27/Dec/14 6:01 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-23629) NPE with ReentrantLock
Francis Upton resolved JENKINS-23629 as Fixed NPE with ReentrantLock Change By: Francis Upton (27/Dec/14 6:02 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-23629) NPE with ReentrantLock
Francis Upton closed JENKINS-23629 as Fixed NPE with ReentrantLock Change By: Francis Upton (27/Dec/14 6:03 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-25837) ec2 plugins fails to launch new ec2 slaves if previous launch attempt had errors
Francis Upton updated JENKINS-25837 ec2 plugins fails to launch new ec2 slaves if previous launch attempt had errors Change By: Francis Upton (27/Dec/14 6:04 PM) Priority: Blocker Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-25749) spot instance slaves don't get the assigned tags
Francis Upton closed JENKINS-25749 as Fixed spot instance slaves dont get the assigned tags Change By: Francis Upton (27/Dec/14 6:07 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-25749) spot instance slaves don't get the assigned tags
Francis Upton resolved JENKINS-25749 as Fixed spot instance slaves dont get the assigned tags Probably fixed by https://github.com/jenkinsci/ec2-plugin/pull/106 Change By: Francis Upton (27/Dec/14 6:06 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-25718) Associate public ip has no effect with spot instances
Francis Upton closed JENKINS-25718 as Fixed Associate public ip has no effect with spot instances Change By: Francis Upton (27/Dec/14 6:07 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-25718) Associate public ip has no effect with spot instances
Francis Upton resolved JENKINS-25718 as Fixed Associate public ip has no effect with spot instances Change By: Francis Upton (27/Dec/14 6:07 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-25721) user-data mangling in spot instance slaves breaks cloudinit
Francis Upton resolved JENKINS-25721 as Fixed user-data mangling in spot instance slaves breaks cloudinit Change By: Francis Upton (27/Dec/14 6:11 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-25721) user-data mangling in spot instance slaves breaks cloudinit
Francis Upton closed JENKINS-25721 as Fixed user-data mangling in spot instance slaves breaks cloudinit Change By: Francis Upton (27/Dec/14 6:11 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-20734) NPE on some operations after restart
Francis Upton resolved JENKINS-20734 as Fixed NPE on some operations after restart Change By: Francis Upton (27/Dec/14 6:19 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-20734) NPE on some operations after restart
Francis Upton closed JENKINS-20734 as Fixed NPE on some operations after restart Change By: Francis Upton (27/Dec/14 6:19 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-18854) EC2 Plugin unable to connect to Eucalyptus 3.x
Francis Upton resolved JENKINS-18854 as Fixed EC2 Plugin unable to connect to Eucalyptus 3.x Change By: Francis Upton (27/Dec/14 6:20 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-18854) EC2 Plugin unable to connect to Eucalyptus 3.x
Francis Upton closed JENKINS-18854 as Fixed EC2 Plugin unable to connect to Eucalyptus 3.x Change By: Francis Upton (27/Dec/14 6:21 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-4995) Support windows AMI's in EC2 plugin
Francis Upton commented on JENKINS-4995 Support windows AMIs in EC2 plugin @Bryan, it would be great to get your help on this. Can't give you any hints right this minute. Let me look into things and get back to you. Ping me again early next week if you don't hear from me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-24676) Region list not being populated when keys are entered
Francis Upton commented on JENKINS-24676 Region list not being populated when keys are entered I'm not sure. I would prefer that an error be given when you do a test connection and no region has been specified rather than selecting a default region. Wouldn't this be more clear? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-24676) Region list not being populated when keys are entered
Francis Upton commented on JENKINS-24676 Region list not being populated when keys are entered @recampbell, yes makes sense, and maybe I'm just being pedantic, but with your change, wouldn't we be testing the connection with some default region (and it might work) and be misleading for the user, rather than failing the Test Connection with some reasonable message. I agree the current situation is bad. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-16079) If EC2 plugin fails to start a stopped slave because it's been manually started, it treats it as dead
Francis Upton closed JENKINS-16079 as Fixed If EC2 plugin fails to start a stopped slave because its been manually started, it treats it as dead Change By: Francis Upton (30/Jul/14 8:53 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-4995) Support windows AMI's in EC2 plugin
Francis Upton commented on JENKINS-4995 Support windows AMIs in EC2 plugin Even with the checkins to date, this is not quite complete. More testing it required. It has been integrated with the master source in the plugin so that hopefully others can test it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-4995) Support windows AMI's in EC2 plugin
Francis Upton assigned JENKINS-4995 to Francis Upton Support windows AMIs in EC2 plugin Change By: Francis Upton (29/Jul/14 11:15 PM) Assignee: FrancisUpton This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-23622) Can't delete a slave with 1.22
Francis Upton commented on JENKINS-23622 Cant delete a slave with 1.22 Thanks I will get a fix for this in the next day and generate a new release. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-19943) EC2 plugin cannot connect to slaves outside us-east-1 on new AWS accounts (using EC2-VPC)
Francis Upton commented on JENKINS-19943 EC2 plugin cannot connect to slaves outside us-east-1 on new AWS accounts (using EC2-VPC) The patch looks good, would you mind making a pull request? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-17086) Use IAM Role when creating instance
Francis Upton commented on JENKINS-17086 Use IAM Role when creating instance Keep bugging me John, I have a little work to do on the multi-cloud support and I'm jammed, I will try to get to it this week and then do a release. Sorry it's so late. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-15389) Fingerprinting private key for discovery is flawed
Francis Upton resolved JENKINS-15389 as Duplicate Fingerprinting private key for discovery is flawed https://issues.jenkins-ci.org/browse/JENKINS-17683 Change By: Francis Upton (16/May/13 4:54 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-17086) Use IAM Role when creating instance
Francis Upton resolved JENKINS-17086 as Fixed Use IAM Role when creating instance Change By: Francis Upton (16/May/13 5:37 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-16280) EC2 Plugin will not build Java projects.
Francis Upton resolved JENKINS-16280 as Not A Defect EC2 Plugin will not build Java projects. This does not sound like a bug, if you still think it is, please provide more information and reopen it. Change By: Francis Upton (10/May/13 11:07 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-15081) Errors with multiple EC2 Clouds
Francis Upton reopened JENKINS-15081 Errors with multiple EC2 Clouds There remain problems with multiple cloud support that will be shortly addressed. Change By: Francis Upton (02/May/13 7:22 PM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-15081) Errors with multiple EC2 Clouds
Francis Upton commented on JENKINS-15081 Errors with multiple EC2 Clouds Just checked in fixes that should make this work properly. I tested it with multiple clouds and both spot and demand instances. Also clarified that the cloud has to be uniquely identified by the region (and made the UI such that it would not allow duplicate EC2 clouds to be created). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-15081) Errors with multiple EC2 Clouds
Francis Upton commented on JENKINS-15081 Errors with multiple EC2 Clouds Here is the commit that had the remaining fixes. Note the bug report number in the commit message is incorrect: https://github.com/jenkinsci/ec2-plugin/commit/9095d318589809ea69cd7e1ca9e1ff94012794d6 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-15081) Errors with multiple EC2 Clouds
Francis Upton resolved JENKINS-15081 as Fixed Errors with multiple EC2 Clouds Change By: Francis Upton (02/May/13 7:56 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-15081) Errors with multiple EC2 Clouds
Francis Upton resolved JENKINS-15081 as Fixed Errors with multiple EC2 Clouds Change By: Francis Upton (30/Apr/13 11:08 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-4995) Support windows AMI's in EC2 plugin
Francis Upton commented on JENKINS-4995 Support windows AMIs in EC2 plugin As a temporary measure, you can make a script in your Windows instance to connect with JNLP, the spot folks have used that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-8616) cannot use spot instances
Francis Upton updated JENKINS-8616 cannot use spot instances This was done by the folks at RTI. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-8616) cannot use spot instances
Francis Upton resolved JENKINS-8616 as Fixed cannot use spot instances Change By: Francis Upton (29/Apr/13 4:15 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-17683) Incorrect hash calculated for custom SSH keys
Francis Upton resolved JENKINS-17683 as Fixed Incorrect hash calculated for custom SSH keys Change By: Francis Upton (29/Apr/13 4:27 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
