Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Rebuild tox environment after change requirements
Tox does not detect changes in requirements, and will fail with missing imports. [example](https://saml.buildvm.openshift.eng.bos.redhat.com:8888/job/art-tools/job/elliott/job/master/6/console) [tox bug](tox-dev/tox#149) This PR looks at the files that have changed in the last 5 commits, and if one of the files that might contain requirements have changed, will add the argument `--recreate` to the `tox` invocation. The magical number 5 was chosen, as it is conceivable that there are multiple commits locally which contain the change, and the change in dependencies is not detected. Alternative approaches are: - install a tox plugin - always recreate in Jenkins
- Loading branch information