[
https://ovirt-jira.atlassian.net/browse/OVIRT-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37168#comment-37168
]
sbonazzo commented on OVIRT-2201:
---------------------------------
{quote}"As an oVirt developer, I want to see the build status for the HEAD
commit of a particular branch of my project so that I can <need to fill in
reason here>"{quote}
- get the general CI health of a release (master vs 4.2)
- take immediate action on the specific branch of a project
{quote}"As an oVirt developer I want to have a way to acquire the lasted CI
build on a particular branch on a particular project so that I can use it as a
dependency for other jobs".
About this last one - I guess we can ask people in devel if "tested" would be a
good enough compromise?
{quote}
Issue with this is that you may have a change which depends on a change in
another package (example: ovirt-host-deploy with otopi) and having to rely on
tested instead of lastSuccessfullBuild means you need to wait for change queue
to succeed and publish to tested before being able to run check-patch. This
means a delay on the handling of the patch of ~1 hour which is suboptimal.
> [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/artifact/
> 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/>
> [email protected]
> <https://red.ht/sig>
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
_______________________________________________
Infra mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]/message/4BTHGRAE5XAXQXXMA6BXV4OFRRUQS4MW/
