[ https://ovirt-jira.atlassian.net/browse/OVIRT-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39332#comment-39332 ] Nir Soffer commented on OVIRT-2730: ----------------------------------- On Wed, May 15, 2019 at 6:56 PM Nir Soffer <nsoffer@redhat.com> wrote:

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/...

The test environment seems to be different that what we have when check-patch is triggered from gerrit.

For reference, I started only this build, from Jenkins UI: https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner/... Which seem to the same thing.

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/...

./ovirt-ci run -s check-patch.linters 100007

https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner/...

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

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/... 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/... ./ovirt-ci run -s check-patch.linters 100007 https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner/... 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)