56f6938968
It's a common desire to be able to have a job that runs unittests against the git checkout of another repository, but getting the tox environment into that shape is a bunch of extra work. Now that we have a defined place where repos go and they're always on the build node, we can look in the source dir for git repos that contain python packages and ask setup.py for the name of the python package they provide. We can then see what packages tox decided to install for this environment, see if we have any matching ones in the source code repos we've put on disk and if so we can re-install those depends from the source location. That way we can cause a tox job to use a second repo for cross-repo unittesting simply by adding that project to required_projects. Add a flag to disable the behavior ... although the easiest way to disable the behavior is to just not list other projects in required_projects. Change-Id: Ia5250c11b1d73baaa70ea1cef7ea1ba4d5bab821 Story: 2001136 Task: 4852 |
||
|---|---|---|
| .. | ||
| integration-tests | ||
| multinode | ||
| python | ||
| tox | ||
| unittests | ||