[
https://ovirt-jira.atlassian.net/browse/OVIRT-2730?page=com.atlassian.jir...
]
Nir Soffer commented on OVIRT-2730:
-----------------------------------
On Thu, May 16, 2019 at 8:23 AM Barak Korren (oVirt JIRA) <
How do you test this?
But CI is sometimes flaky, and we need to re-trigger a build. Using the
command line
tool is an easy way.
However this was mainly testing the capabilities of the manual runner. I
don't think
many people will use check-patch from the command line.
Because you can't select substages like that.
Very strange, the patch I tested is was on master which has valid
stdci.yaml.
Here is another check-network build - seems to work correctly:
https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runn...
I also did other 2 builds today, and they look normal:
./ovirt-ci run build-artifacts 98608
https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runn...
./ovirt-ci run check-patch 98608
https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runn...
So running stages seems to work fine.
It runs the exact same code.
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-runn...
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-runn...
./ovirt-ci run -s check-patch.linters 100007
https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runn...
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)