On Mon, Oct 28, 2019 at 10:08:33PM +0800, Bin Meng wrote: > Hi Tom, > > On Mon, Oct 28, 2019 at 9:44 PM Tom Rini <tr...@konsulko.com> wrote: > > > > On Sun, Oct 27, 2019 at 05:28:25AM -0700, Bin Meng wrote: > > > > > This expands current Azure Pipelines Windows host tools build > > > testing to cover all the CI testing in gitlab and travis CI. > > > > > > Note for some unknown reason, the 'container' cannot be used for > > > any jobs that have buildman, for buildman does not exit properly > > > and hangs the job forever. As a workaround, we manually call > > > docker to run the image to perform the CI tasks. > > > > > > A complete run on Azure Pipelines takes about 2 hours and 10 > > > minutes. > > > > > > Signed-off-by: Bin Meng <bmeng...@gmail.com> > > > > Thanks for doing the work. I will kick things such that we can have > > this run automatically, regularly. My only concern is, are we unable to > > have a world build split like on GitLab? The matrix of "break jobs up > > such that it stays under 50 minutes" is one of the pain points to Travis > > and I'd like to avoid that with Azure if we can as well. > > I think we can do the same world build split like on GitLab. However I > suspect a complete run will take much more time compared to GitLab. > Based on my testing I see each job is a 2-core VM with 8GiB memory, > not as powerful as current GitLab CI runner machine. Although the free > Azure account can support up to 360 minutes per job, having the same > world build split loses the chance to do more parallelism utilizing > the free 10 jobs.
Ah, OK. In that case, yes, mirroring Travis is a reasonable starting point and trying to further optimize from there can be done. -- Tom
signature.asc
Description: PGP signature
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
