Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Generate Jenkins AMI if it doesn't exist #55

Open
PaulDuvall opened this issue Feb 18, 2016 · 4 comments
Open

Generate Jenkins AMI if it doesn't exist #55

PaulDuvall opened this issue Feb 18, 2016 · 4 comments

Comments

@PaulDuvall
Copy link
Contributor

Determine if Jenkins AMI exists and it’s the correct version; otherwise, it will launch Packer. Jenkins is maintained in https://github.com/stelligent/tophat

@dnguyen9
Copy link

Jenkins AMI and jenkins-instance.json only describes for us-east-1 region. this will fail if it is launch in any other region

@PaulDuvall
Copy link
Contributor Author

#54 Correct. The AMI needs to be updated for all supported CodePipeline regions, not all AWS regions, since this solution runs on CodePipeline. As of today, this is us-east-1 and us-west-2. Although, the Jenkins AMI runs from https://github.com/stelligent/tophat so it'll be updated there and support more regions. But, when consumed from Dromedary, it'll support the CodePipeline regions.

@dnguyen9
Copy link

dnguyen9 commented Mar 1, 2016

Paul, can you confirm the security settings on https://s3.amazonaws.com/stelligent-training-public/master/jenkins-instance.json ? it seem it's not public.

@PaulDuvall
Copy link
Contributor Author

@dq922 Done. Sorry about that. I'd uploaded some new changes and didn't change the default permissions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants