Gate fix: Cap hacking to avoid gate failure

Code Issues Proposed changes

hacking is not capped in g-r and it is in
blacklist for requirement as hacking new version
can break the gate jobs.
Hacking can break gate jobs because of various
reasons:
- There might be new rule addition in hacking
- Some rules becomes default from non-default
- Updates in pycodestyle etc
That was the main reason it was not added in g-r
auto sync also. Most of the project maintained the
compatible and cap the hacking version in
test-requirements.txt and update to new version when
project is ready. Bumping new version might need code
fix also on project side depends on what new in that
version.
If project does not have cap the hacking version then,
there is possibility of gate failure whenever new hacking
version is released by QA team.
Example of such failure in recent release of hacking 1.1.0
- http://lists.openstack.org/pipermail/openstack-dev/2018-May/130282.html
Change-Id: I2c84d3368bd6675c28ebba695e0c1afdd2867588

This commit is contained in:

ghanshyam

2018年05月09日 02:15:31 +00:00

parent 2df41a80e3

commit a69ccee287

1 changed files with 1 additions and 1 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

2
test-requirements.txt

View File

@@ -1,7 +1,7 @@

# The order of packages is significant, because pip processes them in the order

# of appearance. Changing the order has an impact on the overall integration

# process, which may cause wedges in the gate later.

hacking>=1.0.0 # Apache-2.0

hacking>=1.0.0,<1.1.0 # Apache-2.0

coverage!=4.4,>=4.0 # Apache-2.0

mock>=2.0.0 # BSD

testtools>=2.2.0 # MIT

Gate fix: Cap hacking to avoid gate failure

2 test-requirements.txt Unescape Escape View File

2
test-requirements.txt

View File