I tried to run check-patch and check-patch linters substage from the
command line:
using:
https://github.com/nirs/oci/pull/37
I assumed that this will run the entire check-patch stage, including all
the sub stages:
./ovirt-ci run -s check-patch 100007
But it run something that looks like check-patch with el7:
https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner/detail/standard-manual-runner/265/pipeline
The test environment seems to be different that what we have when
check-patch is triggered
from gerrit.
Then I tried to run the linters substage:
./ovirt-ci run -s check-patch.linters 100007
https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner/detail/standard-manual-runner/267/pipeline
./ovirt-ci run -s check-patch.linters 100007
https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner/detail/standard-manual-runner/266/pipeline
Both succeeded without running anything
Running build-artifacts works, not sure about check-network.
Can we fix the manual job so:
it run exactly the same way as it run when gerrit trigger the job
allow selection of a sub stage?
nice to have - allow selection of multiple sub stages
Nir