Nir Soffer created OVIRT-2730:
---------------------------------
Summary: Running sub stages using
https://jenkins.ovirt.org/job/standard-manual-runner/
Key: OVIRT-2730
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2730
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: Nir Soffer
Assignee: infra
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
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100102)
_______________________________________________
Infra mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/[email protected]/message/UITZXUPHTOZWND6LCMA2FUTZGDFMZWD4/
