Re: [PATCH-for-5.2 v4 00/17] ci: Move various jobs from Travis to GitLab CI

2020-12-09 Thread Thomas Huth
On 08/11/2020 21.45, Philippe Mathieu-Daudé wrote: > We have various job covered on Travis-CI, but recommend the > community to use GitLab, so build failures are missed. > > We need help to move the jobs to GitLab (we will keep the s390x > and ppc64 containerized jobs on Travis as there is no simi

Re: [PATCH-for-5.2 v4 00/17] ci: Move various jobs from Travis to GitLab CI

2020-11-10 Thread Philippe Mathieu-Daudé
On 11/10/20 4:55 PM, Alex Bennée wrote: > > Philippe Mathieu-Daudé writes: > >> We have various job covered on Travis-CI, but recommend the >> community to use GitLab, so build failures are missed. >> >> We need help to move the jobs to GitLab (we will keep the s390x >> and ppc64 containerized j

Re: [PATCH-for-5.2 v4 00/17] ci: Move various jobs from Travis to GitLab CI

2020-11-10 Thread Alex Bennée
Philippe Mathieu-Daudé writes: > We have various job covered on Travis-CI, but recommend the > community to use GitLab, so build failures are missed. > > We need help to move the jobs to GitLab (we will keep the s390x > and ppc64 containerized jobs on Travis as there is no similar > offer on Gi

[PATCH-for-5.2 v4 00/17] ci: Move various jobs from Travis to GitLab CI

2020-11-08 Thread Philippe Mathieu-Daudé
We have various job covered on Travis-CI, but recommend the community to use GitLab, so build failures are missed. We need help to move the jobs to GitLab (we will keep the s390x and ppc64 containerized jobs on Travis as there is no similar offer on GitLab). Start moving jobs. Resulting pipelines