[JIRA] (OVIRT-416) [standard-ci] build-artifacts should reuse the artifacts built on check-merged if any

[eyal edri [Administrator] (oVirt JIRA)]

    [ https://ovirt-jira.atlassian.net/browse/OVIRT-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19039#comment-19039 ] 

eyal edri [Administrator] commented on OVIRT-416:
-------------------------------------------------

[~sbonazolla at redhat.com] [~mperina] do you know if today check-merged.sh in ovirt-engine is building the same RPMs as build-artifacts?

Potentially they can be different since its a different bash script, but if they are the same we can save a lot of time running duplicate rpm builds... 

Now that we enabled GWT compilation per patch, maybe we can drop the rpm build on check-merged.sh and just do it in build-artifacts?  

we'll find an error in either jobs anyway.. what do you think?

> [standard-ci] build-artifacts should reuse the artifacts built on check-merged if any
> -------------------------------------------------------------------------------------
>
>                 Key: OVIRT-416
>                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-416
>             Project: oVirt - virtualization made easy
>          Issue Type: Improvement
>            Reporter: David Caro Estevez
>            Assignee: infra
>
> Right now most projects just rebuild twice the artifacts, what for some means a big waste of resources, if we could just reuse what was built previously there would be no rebuilding.
> Something to take into account is that the distributions that check-merged and build-artifacts run for might not match, so you can be running check-merged only on fc23 but building artifacts for fc23, fc22 an el7 (as an example), maybe we should not allow different distros on each stage?|



--
This message was sent by Atlassian JIRA
(v1000.184.1#100008)