-
Notifications
You must be signed in to change notification settings - Fork 2
Travisbeantest #8
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
Conversation
thatandromeda
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Assuming that the answer to my question is "yes", and you've verified that this setup causes a deploy to happen (e.g. that the hashes in the requirements.txt file don't make anything blow up), go ahead and merge. Otherwise let's talk :)
| - DJANGO_DB_USER=postgres | ||
| - DJANGO_SETTINGS_MODULE=hamlet.settings.test | ||
| before_deploy: | ||
| - rm -rf hamlet/testmodels/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to clarify, this happens on Travis's clone of the code and not on master?
| - DJANGO_SETTINGS_MODULE=hamlet.settings.test | ||
| before_deploy: | ||
| - rm -rf hamlet/testmodels/ | ||
| - pipenv lock --requirements > requirements.txt |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, cool, this is a sweet way to handle the requirements.txt problem.
.travis.yaml
Merge this before doing any deploys! I'm deleting the old environment (Hamtest) although I did like the name...