[ https://ovirt-jira.atlassian.net/browse/OVIRT-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37119#comment-37119 ] sbonazzo commented on OVIRT-2201: --------------------------------- It covers ~90% of what we had in v1, it still miss: - a way to quickly see if jobs are failing on a specific branch - a way to consume builds from a specific branch (some jobs take latestSuccessfulBuild from Jenkins for building and this causes random branch selection based on last build). About this, maybe jobs should be changed for not consuming builders directly, but needs to track down them.

[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: Improvement Components: Standard CI (Pipelines) 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/lastSuccessfulBuild... 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@redhat.com <https://red.ht/sig>

-- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)