Tests still have python2.7 configs remaining and some tests
are named -debian, implying the old ones are for centos and
can be removed.
This commit removes the python2.7 and centos configs from tox
and zuul.
Test Plan:
1. PASS - Ran all tests in tox and verified if every test
finished with the desired output.
2. PASS - Ran tests in zuul environment and checked if
it was successful.
Story: 2010531
Task: 48384
Change-Id: Ibac431754cda5150847a4f47768000d8a222434d
Signed-off-by: Gustavo Pereira <gustavo.lyrapereira@windriver.com>
Updating the rsa ssh host key based on:
https://github.blog/2023-03-23-we-updated-our-rsa-ssh-host-key/
Note: In the future, StarlingX should have a zuul job and
secret setup for all repos so we do not need to do this
for every repo.
Needed to rename the secret, because zuul fails if like-named
secrets have diffent values in different branches of the same
repo.
Partial-Bug: #2015246
Change-Id: I84a2a4e1755b5cfc08a1d43c1c6ab0e39be90373
Signed-off-by: Davlet Panech <davlet.panech@windriver.com>
The python2.7 jobs will no longer be executed as part
of the zuul check and gate.
The nodeset with the python2.7 interpreter has been
updated around Feb 5th 2023.
Story: 2010531
Task: 47310
Signed-off-by: Al Bailey <al.bailey@windriver.com>
Change-Id: Ic5fffbde73a4f7aaddfd0086efa7e4c1d9f8b25f
The ubuntu-jammy nodeset gets selected by default
starting around yesterday, and something about the
headers is mismatched.
Collecting cffi>=1.1
Failed to build cffi
ubuntu-focal seem to work fine.
Will specify the nodeset to be focal to resolve this.
Partial-Bug: 1994843
Signed-off-by: Al Bailey <al.bailey@windriver.com>
Change-Id: Id92b1eeb2e8e915f18c144f1b9de321bab85f76f
A different version of astroid is required for python3.9, pylint,
and pep8. The pylint setup related to pip and upper constraints
is different for python3.9. Updated the requirement packages'
software version(to versions that support python3.9) Updated
'cover' tox.ini target to be python3.9
This flake8 suppresion is added:
H126: flag use of third party mock
These pylint disable/enable alarm checks are removed due to deprecation:
-Enable
E1606: execfile-builtin
E1607: old-ne-operator
E1608: old-octal-literal
E1610: non-ascii-bytes-literal
E1611: invalid-unicode-literal
W1641: eq-without-hash
-Disable
W0403: relative-import
These pylint suppressions need to be added
W0707: raise-missing-from
W1406: redundant-u-string-prefix
W1514: unspecified-encoding
E1101: no-member
The explicit addition of python3 checks that were required
when running pylint in python2 to test python3 are removed
since pylint is now running in python3 and gets those
checks implicitly.
Removed config keys from the pylint.rc that are no longer
valid for the version of pylint executed by python3.9.
The zuul target explicitly specifies python3.9 and the
ubuntu-focal node to ensure it has the correct interpreter.
Depends-On: https://review.opendev.org/c/starlingx/distcloud/+/850543
Story: 2008943
Task: 45692
Signed-off-by: BoYuan Chang <boyuan.chang@windriver.com>
Change-Id: I70280a5fee178c228e138d4ac1c047dae7696c85
Adding py39 gate.
Removing redundant py36 Zuul jobs since we now have py39 Zuul jobs in
place with the debian nodeset
Story: 2006796
Task: 42980
Signed-off-by: Bernardo Decco <bernardo.deccodesiqueira@windriver.com>
Change-Id: I9a3d047b81c599b96b4ace040be237d16b655c99
The py2.7 jobs need to specify xenial
The py3.6 jobs need to specify bionic
The focal zuul nodes only have python 3.8 installed in them
Zuul targets that invoke a generic python3 interpreter such
as pep8 is not specified.
The copyright date was updated in order to trigger
the zuul jobs, as a no-delta type of change.
Change-Id: If5352228a018f3147ae78172ae625066150c0a95
Partial-Bug: 1928978
Signed-off-by: albailey <Al.Bailey@windriver.com>
Setting up the bandit tool for the scanning of HIGH severity issues
in the python codes under Starlingx/distributedcloud folder.
Expecting this merge will enable zuul job for CI/CD of bandit scan.
Configuration files:
1. tox.ini for adding bandit environment and command.
2. test-requirements.txt for adding bandit version.
3. .zuul.yaml file for adding bandit job and configuring under
check job to run code scan every time before code commit.
Test:
Run tox -e bandit command inside the fault folder to validate the
bandit scan and result.
Please note:
Changes will be implemented in batches and this is Batch6 change.
Story: 2007541
Task: 39648
Depends-On: https://review.opendev.org/#/c/721294/
Change-Id: I6fdfeacdb000faafc73c44eef352bf2abd38a9a2
Signed-off-by: Sharath Kumar K <sharath.kumar@intel.com>
The existing py27 unit tests were not all passing in py36,
however now they are and so the zuul check and gate for py36
have been added.
Change-Id: Ie293ec69a04e6fd657f960aa9a135c428138b4b4
Story: 2004515
Task: 39768
Signed-off-by: albailey <Al.Bailey@windriver.com>
The pylint that was specified as an upper constraint was not
as strict as the newer versions.
- Fixed or suppressed any new error codes being reported.
Suppressed error codes should be fixed by additional reviews.
- added a zuul target for pylint
- Added dcdbsync to the folders being processed by pylint.
- Removed the env:UPPER_CONSTRAINTS_FILE from tox.ini so that zuul
does not override the upper constraints with an newer version.
- Needed to add greenlet to the extension-pkg-whitelist since
runtime introspection of that component is not possible.
- oslo-messaging get_transport deprecated 'aliases' in pike, and
removed it in rocky. The packaged version in STX is 5.30.6
which still supports aliases. This requires us to explicitly
run tox with the version that we ship (pre-stein). This is
controlled by a local upper-constraints.txt file.
Related-Bug: 1865054
- Paste file handling reports a pylint issue which has been suppressed
Related-Bug: 1865085
Story: 2004515
Task: 38882
Change-Id: Ie7c8c2adab1eeb9100159a2aa29968a0b557e2e4
Signed-off-by: Al Bailey <Al.Bailey@windriver.com>
Use templates instead of individual jobs so that these
can be changed in one place.
Depends-On: https://review.opendev.org/677606
Change-Id: Ice80a94fe8c5d3634e729c888672ce698049f87a
* Add pointers in the main doc to api-ref and releasenotes pages
* Add publish-stx-api-ref and publish-stx-releasenotes jobs
* Add search at bottom of api-ref and relnotes pages to trigger the jobs
Depends-On: https://review.openstack.org/#/c/608409/
Change-Id: Ide9a7d5829b41191c9127af75c4320f94d82f428
Signed-off-by: Abraham Arce <abraham.arce.moreno@intel.com>
Also set the theme to alabaster until starlingxdocs is ready
Change-Id: I2d5d4456b3f21ea2c27f6e6b519170482f617fb5
Signed-off-by: Dean Troyer <dtroyer@gmail.com>
Baseline changes to comply with Release Notes Management
based in Reno [0]:
* Use build-openstack-releasenotes job for release notes
(We can't use the OpenStack releasenotes template as it includes
publish jobs, stx needs its own)
* Add newnote tox environment as convenience for creating new release
notes, re-using the releasenotes venv.
* Remove the unused 'true' tox environment.
[0] https://docs.openstack.org/reno/latest/
Story: 2003101
Task: 26620
Change-Id: Ie0eac726983f8cdfb6bade20a2b5445559a962e0
Signed-off-by: Abraham Arce <abraham.arce.moreno@intel.com>
* Add .gitreview
* Add .zuul.yaml with basic linters and pep8 jobs
* Fix up tox.ini to run linters and pep8 environments. This
changed some leagacy config in the default testenv that will
affect the more specific environments.
Change-Id: Ieca279a240b8705dcb73d9d195e1658a40e199e1
Signed-off-by: Dean Troyer <dtroyer@gmail.com>
Gustavo Pereira