[
https://ovirt-jira.atlassian.net/browse/OVIRT-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39336#comment-39336
]
Barak Korren commented on OVIRT-2730:
-------------------------------------
On Fri, 17 May 2019 at 01:04, Nir Soffer (oVirt JIRA) <
I looked at the parameters screen
<https://jenkins.ovirt.org/job/standard-manual-runner/265/parameters/> for
the refspec you passed to the manual runner (refs/changes/07/100007/8) and
then simply checked out the patch with `git review -d 100007`. Looking at
`stdci.yaml` there you can see its quite different then the one in the
master branch.
So is commenting `ci test please` or `ci please test` or just `ci test` in
gerrit....
Checkout the patch and have a look, the CI system does not rebase before
testing, so it does not matter which branch you intend to merge into, only
which commit you started from when first creating the local branch you
wrote the patch in.
--
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
> 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 -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
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/infra@ovirt.org/message/GQEM6HHPYBOJ7VXAG2DH7CJLJTMLEDL5/
