-
Notifications
You must be signed in to change notification settings - Fork 3k
Continuous Integration Features #1040
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
…et, etc) for tests up front, before any tests are built
Travis failed with an error as it installed only colorama and pretty table.
|
I realize the irony in saying I'm not sure where to fix this, given that Travis is a Continuous Integration service :) Is there a script that manages the pip module installation? Or does it run the setup.py in the repository root? |
@bridadan :-))))) Here .travis.yaml file:
Add there jinja2 |
Ah, don't know how I missed it :P I pushed the changes and it looks like it's passing |
OK great :) |
I run one jenkins job with build_release script from this PR, all ok. Thanks |
Continuous Integration Features
This pull request adds some features that are useful for integrating our build system with Continuous Integration tools. These features include:
I have been testing this on my own VMs and everything seems to be running smoothly. Let me know if you have any thoughts on how things have been organized.