[
https://ovirt-jira.atlassian.net/browse/OVIRT-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=38033#comment-38033
]
Dafna Ron commented on OVIRT-2501:
----------------------------------
CQ is not completely automated and what I mean by that is that we (i.e me/infra
owners) need to look at the failures and determine if the cause of failure/root
cause of failure or some other patch is responsible.
Having said that, we want, in future, to involve the developers automatically
at an earlier stage then this one but we are still considering several
solutions for this.
> Add gerrit comment about actual CQ results
> ------------------------------------------
>
> Key: OVIRT-2501
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2501
> Project: oVirt - virtualization made easy
> Issue Type: Task
> Reporter: Yedidyah Bar David
> Assignee: infra
>
> Hi all,
> I do not know how the CQ works, or even the terminology. Sorry.
> When a patch is merged in gerrit, some time later a job is triggered
> that adds it to the CQ. This job adds a link like [1].
> Later, the CQ tests the batch of changes, and either approves them or
> bisects them to try to find the bad one. I can't see in the gerrit
> page, e.g. [2], any comment from this part. Please make the relevant
> jobs add suitable comments to relevant gerrit changes. E.g. "This
> change passed the CQ <link>", or failed, or some other suspect change
> failed and therefore this one isn't published either, or whatever.
> [1] https://jenkins.ovirt.org/job/standard-enqueue/16271/
> [2] https://gerrit.ovirt.org/#/c/94106/
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100092)
_______________________________________________
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/J757DLVED4U24D5ONRESLVIVH6OKDBPP/
