[JIRA] (JENKINS-47301) JClouds aws-ec2 always tries to use default subnet

6 views
Skip to first unread message

tim@panubo.com (JIRA)

unread,
Mar 21, 2018, 8:04:03 PM3/21/18
to jenkinsc...@googlegroups.com
Tim Robinson commented on Improvement JENKINS-47301
 
Re: JClouds aws-ec2 always tries to use default subnet

I'm also seeing this issue on AWS. Also tested against a recent SNAPSHOT but got the same error.

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

grv87@yandex.ru (JIRA)

unread,
Mar 26, 2018, 1:55:02 PM3/26/18
to jenkinsc...@googlegroups.com

+1

VPC setting is not honored. I got 'No default VPC for this user' error.

grv87@yandex.ru (JIRA)

unread,
Mar 29, 2018, 12:27:02 PM3/29/18
to jenkinsc...@googlegroups.com

grimbeaj@gmail.com (JIRA)

unread,
Aug 15, 2018, 11:06:02 AM8/15/18
to jenkinsc...@googlegroups.com

I would really like to see this get fixed at some point. My team and I have been having to use the EC2 plugin to get around the failure of this one to operate as expected. That plugin is a lot less robust than JClouds and has required us to put a lot of brittle cron jobs in place to take care of things that this one natively supports.

This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

fritz@fritz-elfert.de (JIRA)

unread,
Dec 14, 2019, 5:57:02 AM12/14/19
to jenkinsc...@googlegroups.com
Fritz Elfert updated Improvement JENKINS-47301
 

Committed to master. Please test (I don't have an AWS account anymore)

Will be released in 2.16. Sorry it took so long.

Jenkins / Improvement JENKINS-47301
Change By: Fritz Elfert
Status: Open Fixed but Unreleased
Resolution: Fixed
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

fritz@fritz-elfert.de (JIRA)

unread,
Dec 17, 2019, 3:26:04 AM12/17/19
to jenkinsc...@googlegroups.com
 

Released in 2.16

Change By: Fritz Elfert
Status: Fixed but Unreleased Resolved
Reply all
Reply to author
Forward
0 new messages