[ https://ovirt-jira.atlassian.net/browse/OVIRT-719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
eyal edri [Administrator] reassigned OVIRT-719: ----------------------------------------------- Assignee: Gil Shinar (was: infra) This can help dramatically to reduce number of check-patch jobs... > check-patch jobs should check if the patch is still open > --------------------------------------------------------- > > Key: OVIRT-719 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-719 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri [Administrator] > Assignee: Gil Shinar > > We sometimes see multiple check-patch jobs still running while actually the > patch for them was already merged. > This happens when Jenkins queue is too big and the committer merge the patch > before the job in CI finish or even starts. > In the case where the job didn't even start because of long queue, there is > not reason to continue running the job if the patch was merged. > Any post merge logic will be run in check-merged stage and there is no value > in adding info on the check-patch to the merged commit. > It should be easy to check in the beginning of the check-patch job and part > of standard CI if the patch that is triggered the job is still open and the > job should continue. > If the patch is merged, then we should abort the job and thus cleaning the > queue from check-patch jobs that won't have any value . -- This message was sent by Atlassian JIRA (v1000.383.0#100014) _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra