Vojtech Szocs commented on OVIRT-416:

> So the question is, can we reduce this to 1-2 permutations? if this is just 
> going to nightly / hourly repo then we don't need all these permutations and 
> we'll enjoy a much faster verification on the experimental flow which 
> collects artifacts from build-artifacts jobs.


Full GWT build (all browsers & languages) is not needed for oVirt nightly 
(snapshot) builds. It's only needed for oVirt official (release) builds.

> We are now adding the 'build official manual' option to standard CI, so we 
> can keep the 27 permutations there for official builds. 

Sounds good to me.

> [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
Infra mailing list

Reply via email to