On Mon, Feb 08, 2021 at 04:33:36PM +0000, Daniel P. Berrangé wrote: > This series fixes a problem with our gitlab CI rules that cause > container builds to be skipped. See the commit description in the > first patch for the details on this problem. > > The overall result of this series though is a small increase in overall > pipeline time. > > Previously > > - When container jobs are skipped: approx 1hr 5 mins > - When container jobs are run, cached by docker: approx 1hr 15 mins > - When container jobs are run, not cached by docker: approx 1hr 30 mins > > With this series applied the first scenario no longer exists, so > all piplines are either 1hr 15 or 1hr 30 depending on whether the > container phase is skipped.
I mean to say the biggest problem I see is the cross-win64-system job. This consumes 1 hour 5 minutes all on its own. It is at least 15 minutes longer that every other job AFAICT. So no matter how well we parallelize stuff, 1 hr 5 is a hard lower limit on pipeline duration right now. We might want to consider how to split the win64 job or cut down what it does in some way ? Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|