[JIRA] (OVIRT-2730) Running sub stages using https://jenkins.ovirt.org/job/standard-manual-runner/
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39333#comment-39333 ] Barak Korren commented on OVIRT-2730: ------------------------------------- On Wed, 15 May 2019 at 18:58, Nir Soffer (oVirt JIRA) < Looking at the stdci.yaml file I get when cloning the patch - I don't see any substages or distroes defined in it, so STDCI does what it can in that case - run the default substage for the specified architectures that it can find script files for. Is this based on a very old version of vdsm's stdci.yaml ? You can see the exact same thing happening for check-patch triggered from Gerrit: https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pat... In fact running check-patch with manual runner is quite useless, since CI will always run it for you anyway when you push the patch... Because you can't select substages like that. check-network would not work since its not defined in stdci.yaml for that patch. It runs the exact same code. - allow selection of a sub stage? Probably not gonna happen - this would require some deep changes. - nice to have - allow selection of multiple sub stages Same as above, you can only select a stage at this point. -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
-- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100102)
On Thu, May 16, 2019 at 8:23 AM Barak Korren (oVirt JIRA) < jira@ovirt-jira.atlassian.net> wrote:
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.
check-network would not work since its not defined in stdci.yaml for that patch.
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-runner/... 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-runner/... ./ovirt-ci run check-patch 98608 https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner/... So running stages seems to work fine. It runs the exact same code.
participants (2)
-
Barak Korren (oVirt JIRA) -
Nir Soffer