[
https://ovirt-jira.atlassian.net/browse/OVIRT-2201?page=com.atlassian.jir...
]
Barak Korren commented on OVIRT-2201:
-------------------------------------
[~sbonazzo(a)redhat.com] rereading our chat transcript above it seems to me that given that
in V2, things do not land on 'tested' unless they pass check-merged (in addition
to all other conditions), and if we implement OVIRT-1717 (tagging commints that make it to
tested), we can drop this requirement.
Am I right about this, or are there other use cases I need to take into account?
[regression] STDCI v2 doesn't distinguish jobs for different
branches
---------------------------------------------------------------------
Key: OVIRT-2201
URL:
https://ovirt-jira.atlassian.net/browse/OVIRT-2201
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: sbonazzo
Assignee: infra
In V1 we had jobs with different name based on branches they were building.
In V2 we have single job building all branches.
As an example for imgbased:
https://jenkins.ovirt.org/job/imgbased_standard-on-merge/lastSuccessfulBu...
will contain randomly 4.2 or master builds.
This won't allow to filter jenkins to see which branches are failing to
build, forcing developers to check manually.
This also won't allow to check if latest build landed in tested repo
because thee build may be targeted to a different branch than the one under
check.
To me this is a regression that will make me rethink about the switching to
v2 and considering reverting to v1.
--
SANDRO BONAZZOLA
ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <
https://www.redhat.com/>
sbonazzo(a)redhat.com
<
https://red.ht/sig>
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)