Use gerrit-tox-verify for SFC python verification 73/68873/5
authorJaime Caamaño Ruiz <jcaamano@suse.com>
Wed, 28 Feb 2018 12:37:32 +0000 (13:37 +0100)
committerThanh Ha <thanh.ha@linuxfoundation.org>
Thu, 15 Mar 2018 14:38:04 +0000 (10:38 -0400)
commit5fe149e6b21b1a95a84e5f4d5139ea7d7e15c544
tree3095127935113bf8f952379796d560395f09086e
parent14c05f7b54c2e90449fda116c0dfc5b3661c34e9
Use gerrit-tox-verify for SFC python verification

The original python verfication job had some issues with outdated pip
and setuptools. Take this chance to move SFC python verification over
to the global JJB tox verification job template.

The gap betwwen the two is the use of jenkins_build_package.sh to upload
the sfc-py artifact to pypi. This is silently failing anyway since the
credentials are no longer valid. It will neeed to be done through some
other way, if at all.

Change-Id: I08c483924468917bcc41fe77e06eff9930255859
JIRA: SFC-217
Signed-off-by: Jaime Caamaño Ruiz <jcaamano@suse.com>
jjb/sfc/sfc-python.yaml