[JIRA] (OVIRT-1223) Nightly/bare metal vdsm check-merged jobs
by danken (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1223?page=com.atlassian.jir... ]
danken commented on OVIRT-1223:
-------------------------------
spoken with Barak. He meant adding a new suit to OST.
> Nightly/bare metal vdsm check-merged jobs
> -----------------------------------------
>
> Key: OVIRT-1223
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1223
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Leon Goldberg
> Assignee: infra
> Fix For: OVIRT-INFRA-MAR-2017
>
>
> Hey,
> We're trying to come up with a solution to our lengthy check-merged
> jobs, that are about to become even lengthier now when we've
> discovered we're missing a permutation to our network tests.
> check-merged currently takes roughly 50 minutes to run to completion,
> with the network tests taking roughly 30 minutes; with the additional
> permutation check-merged will run for more than an hour.
> We thought of 2 possible solutions:
> 1) Only run the additional permutation once a day (e.g. introduce a
> nightly job).
> 2) Run check-merged on bare metal -- network tests take roughly 1/3 of
> the time on bare metal.
> Somehow closing the gap to bare metal would also of course be nice.
> We'd love your input.
> Thanks,
> Leon
--
This message was sent by Atlassian JIRA
(v1000.910.0#100040)
7 years, 5 months
[JIRA] (OVIRT-1223) Nightly/bare metal vdsm check-merged jobs
by danken (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1223?page=com.atlassian.jir... ]
danken commented on OVIRT-1223:
-------------------------------
I don't really understand your suggestion. OST is all about system test. vdsm check-merged is about testing vdsm API.
Do you suggest to pull in vdsm-tests onto host0 in OST, and run them there after OST finishes? Or do you suggest a completely new OST suit, dedicated to vdsm functional tests?
> Nightly/bare metal vdsm check-merged jobs
> -----------------------------------------
>
> Key: OVIRT-1223
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1223
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Leon Goldberg
> Assignee: infra
> Fix For: OVIRT-INFRA-MAR-2017
>
>
> Hey,
> We're trying to come up with a solution to our lengthy check-merged
> jobs, that are about to become even lengthier now when we've
> discovered we're missing a permutation to our network tests.
> check-merged currently takes roughly 50 minutes to run to completion,
> with the network tests taking roughly 30 minutes; with the additional
> permutation check-merged will run for more than an hour.
> We thought of 2 possible solutions:
> 1) Only run the additional permutation once a day (e.g. introduce a
> nightly job).
> 2) Run check-merged on bare metal -- network tests take roughly 1/3 of
> the time on bare metal.
> Somehow closing the gap to bare metal would also of course be nice.
> We'd love your input.
> Thanks,
> Leon
--
This message was sent by Atlassian JIRA
(v1000.910.0#100040)
7 years, 5 months
[JIRA] (OVIRT-1354) SDK STD-CI jobs do not include pust-build cleanup steps
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1354?page=com.atlassian.jir... ]
Barak Korren reassigned OVIRT-1354:
-----------------------------------
Assignee: Barak Korren (was: infra)
> SDK STD-CI jobs do not include pust-build cleanup steps
> -------------------------------------------------------
>
> Key: OVIRT-1354
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1354
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Components: Jenkins
> Reporter: Barak Korren
> Assignee: Barak Korren
> Priority: Highest
> Labels: standard-ci
>
> The SDK STD-CI jobs have been defined using ther own strange YAML because of reasons that have to do with the names of the Git repos they are built from.
> As a result a bug was introduced where the SDK jobs are created without cleanup steps. This ends up causing issues for other jobs shaving slaved with them.
--
This message was sent by Atlassian JIRA
(v1000.910.0#100040)
7 years, 5 months
[JIRA] (OVIRT-1354) SDK STD-CI jobs do not include pust-build cleanup steps
by Barak Korren (oVirt JIRA)
Barak Korren created OVIRT-1354:
-----------------------------------
Summary: SDK STD-CI jobs do not include pust-build cleanup steps
Key: OVIRT-1354
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1354
Project: oVirt - virtualization made easy
Issue Type: Bug
Components: Jenkins
Reporter: Barak Korren
Assignee: infra
Priority: Highest
The SDK STD-CI jobs have been defined using ther own strange YAML because of reasons that have to do with the names of the Git repos they are built from.
As a result a bug was introduced where the SDK jobs are created without cleanup steps. This ends up causing issues for other jobs shaving slaved with them.
--
This message was sent by Atlassian JIRA
(v1000.910.0#100040)
7 years, 5 months
[JIRA] (OVIRT-1354) SDK STD-CI jobs do not include pust-build cleanup steps
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1354?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-1354:
--------------------------------
Epic Link: OVIRT-400
> SDK STD-CI jobs do not include pust-build cleanup steps
> -------------------------------------------------------
>
> Key: OVIRT-1354
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1354
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Components: Jenkins
> Reporter: Barak Korren
> Assignee: infra
> Priority: Highest
> Labels: standard-ci
>
> The SDK STD-CI jobs have been defined using ther own strange YAML because of reasons that have to do with the names of the Git repos they are built from.
> As a result a bug was introduced where the SDK jobs are created without cleanup steps. This ends up causing issues for other jobs shaving slaved with them.
--
This message was sent by Atlassian JIRA
(v1000.910.0#100040)
7 years, 5 months