[v2] gitlab: expand the CI job coverage (RESEND)

[libvirt PATCH v2 0/9] gitlab: expand the CI job coverage (RESEND)

Posted by Daniel P. Berrangé 4 years ago

There are main goals with this series

  - Introduce a minimal job building the website and publishing
    an artifact which can be deployed onto libvirt.org
  - Introduce a minimal job building the libvirt.pot for import
    into Weblate (only runs on git master branch)
  - Expanding CI jobs to get coverage closer to Travis/Jenkins
  - Reducing cross-build jobs to just interesting variants,
    since the full set hasn't shown value in detecting failures

The Linux native job coverage is now a superset of that achieved
by Travis/Jenkins.

For post-merge testing the full set of jobs are run on git
master (measured approx 50 minutes total duration)

For pre-merge testing the Linux job count is reduced for quicker
turnaround time for developers (measured ~35 minutes total
duration)

Changed in v2:

  - Add more native test jobs to run on git master
  - Restrict git clone depth
  - User variable for "make" command name
  - Add test job to build the master pot file
  - Remove extra configure args for website job
  - Re-ordered patches to reduce repeated changes

Daniel P. Berrangé (9):
  gitlab: use CI for building website contents
  gitlab: reduce number of cross-build CI jobs
  gitlab: group jobs into stages
  gitlab: rename the cross build jobs
  gitlab: add mingw cross build CI jobs
  gitlab: add x86_64 native CI jobs
  gitlab: add variable for make command name
  gitlab: restrict git history to 100 commits
  gitlab: add job for building latest potfile

 .gitlab-ci.yml | 178 ++++++++++++++++++++++++++++++++++++++++---------
 1 file changed, 148 insertions(+), 30 deletions(-)

-- 
2.24.1

Re: [libvirt PATCH v2 0/9] gitlab: expand the CI job coverage (RESEND)

Posted by Daniel P. Berrangé 4 years ago

On Tue, Mar 24, 2020 at 04:23:56PM +0000, Daniel P. Berrangé wrote:
> There are main goals with this series
> 
>   - Introduce a minimal job building the website and publishing
>     an artifact which can be deployed onto libvirt.org
>   - Introduce a minimal job building the libvirt.pot for import
>     into Weblate (only runs on git master branch)
>   - Expanding CI jobs to get coverage closer to Travis/Jenkins
>   - Reducing cross-build jobs to just interesting variants,
>     since the full set hasn't shown value in detecting failures
> 
> The Linux native job coverage is now a superset of that achieved
> by Travis/Jenkins.
> 
> For post-merge testing the full set of jobs are run on git
> master (measured approx 50 minutes total duration)
> 
> For pre-merge testing the Linux job count is reduced for quicker
> turnaround time for developers (measured ~35 minutes total
> duration)

I meant to say you can see an illustration of the CI pipeline
in this URL.

   https://gitlab.com/berrange/libvirt/pipelines/129242976

Published artifacts are downloaded from the "jobs" tab, and if
we had unit tests published in junit data format, they'd appear
in the "tests" tab IIUC


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 :|