* Fixes ocassionally pre-commit linting was broken after a merge (-a)
By always running on all files we avoid this rare case from happening.
As seen on https://review.openstack.org/#/c/636160/55
* Fix minor bashare identation error that slipped in due to previous
issue fix.
* Adds .eggs/ to ignore
* Moves whitelist_externals at top level to simplify tox.ini file
* Adds missing file patterns for tox py27/py35 job
* Avoids repetition of file patterns between py27/py37 jobs.
* removed pyflakes as this is included in flake8
* Running just "tox" now works even if developer has alternative python
versions like py36/py37 instead of py35. No impact on CI where job
is forcing use of specific interpreter.
* Remove bindep tox env and include bindep run as part of unittest
environments. This will assure it runs on CI, as it previously din't.
Change-Id: Ia8f98fc0fda18203be3c17d4fdb93d33ca244dc4
Currently, we do this in a combination of bash in this
repo and the release files themselves. However, as we begin
to support more different upgrade scenarios, this has proven
to be difficult to maintain.
Instead, we will use this python script to create a dictionary
of releases which describes which release will be used at each
point in the deploy: undercloud_install, undercloud_upgrade,
overcloud_deploy, and overcloud_upgrade.
This commit only provides an intial skeleton to work from.
Follow-up commits will provide:
1. The ability to get a DLRN hash for each of the above breakpoints
2. A CLI for the tool so it can be called from the TOCI scripts
3. The ability to parse a featureset config for upgrade variables
4. The ability to output the dictionary for consumption by TOCI scripts
Change-Id: Ibf61d7d12230f6714eb7dad91169aa043f5f8417
This updates the CI status report so that we generate
a tripleo-jobs.html-table that can be used to include
the CI status results in an external website. The
existing tripleo-jobs.html is still generated like
it was before.
Change-Id: I97285e147e79efbce3c16bf56e5a1eaa1656c1e4
Ghanshyam Mann