Ec2 provider #636
Merged
Ec2 provider #636
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pawelgrzeda
force-pushed
the
ec2-provider
branch
5 times, most recently
from
f320053 to
68a1bae
Compare
pawelgrzeda
force-pushed
the
ec2-provider
branch
from
68a1bae to
e877b49
Compare
weban-pl
approved these changes
Jul 22, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ORIGINAL PR BY jonhenrik13 here
This PR Contains 10 of 12 commits from original as 2 of them was "merge from master" commits.
What is the problem that this PR is trying to fix?
Adding ec2 backend provider code in order to run builds in EC2
What approach did you choose and why?
I adapted the docker code to use EC2 api
How can you test this?
By setting TRAVIS_WORKER_PROVIDER_NAME='ec2'
What feedback would you like, if any?
I'd like feedback in the pr.