This repository has been archived by the owner on Dec 4, 2018. It is now read-only.
configure travis to generate wheel artifacts #68
Merged
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.
This configures Travis so that whenever a new Github 'release' is created, a wheel is generated and attached to the release page. Here's an example of what that looks like, from college-costs: https://github.com/cfpb/college-costs/releases/tag/2.3.9
Some benefits: this should make deployments faster and simpler (since the package will never need to be "built" in Jenkins), and removes the requirement that every app must support whatever Node version that cfgov-refresh depends on.
You can see in optional-public that we've started replacing git checkout URL's with absolute links to the built wheels: https://github.com/cfpb/cfgov-refresh/blob/master/requirements/optional-public.txt
Additions
Changes
Testing
Checklist