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

Switch to using a container for Travis builds #634

Merged
merged 1 commit into from Jul 11, 2015

Conversation

codemercenary
Copy link
Contributor

Switch to container builds for speed and performance reasons as per this discussion. Full VM builds are slow and unresponsive, this system is far superior.

@codemercenary codemercenary force-pushed the feature-traviscontainer branch 30 times, most recently from caaf126 to 093adcb Compare July 11, 2015 03:52
@codemercenary
Copy link
Contributor Author

Update: Container builds are actually slightly slower, but they seem to kick off faster than their VM counterparts, and Travis seems to want us to move over there. In any event, build times are at least something that's within our power to address.

Switch to container builds for speed and performance reasons as per [this](http://docs.travis-ci.com/user/migrating-from-legacy) discussion.  Full VM builds are slow and unresponsive, this system is far superior.
codemercenary added a commit that referenced this pull request Jul 11, 2015
Switch to using a container for Travis builds
@codemercenary codemercenary merged commit 9563e92 into develop Jul 11, 2015
@codemercenary codemercenary deleted the feature-traviscontainer branch July 11, 2015 04:07
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

Successfully merging this pull request may close these issues.

None yet

1 participant