[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: new procedure with GitLab CI
From: |
Valentin Villenave |
Subject: |
Re: new procedure with GitLab CI |
Date: |
Wed, 27 May 2020 12:19:09 +0200 |
On 5/27/20, Valentin Villenave <address@hidden> wrote:
> On 5/27/20, Jonas Hahnfeld <address@hidden> wrote:
>> We do want to have the pipeline on the commit before it is merged
>> because this replaces patchy.
>
> Well, that’s absolutely crucial at the MR review stage. But after passing
[sorry, I forgot to end that sentence]
… After passing the review and countdown process, the need for CI
testing decreases. So an option to bypass the pipeline when we reach
the “rebase & merge” stage wouldn’t necessarily be harmful.
V.
Re: new procedure with GitLab CI, Dan Eble, 2020/05/23
Re: new procedure with GitLab CI, Jonas Hahnfeld, 2020/05/27
- Re: new procedure with GitLab CI, Valentin Villenave, 2020/05/27
- Re: new procedure with GitLab CI, Jonas Hahnfeld, 2020/05/27
- Re: new procedure with GitLab CI, Valentin Villenave, 2020/05/27
- Re: new procedure with GitLab CI,
Valentin Villenave <=
- Re: new procedure with GitLab CI, Jonas Hahnfeld, 2020/05/27
- Re: new procedure with GitLab CI, David Kastrup, 2020/05/27
- Re: new procedure with GitLab CI, Dan Eble, 2020/05/27
- Re: new procedure with GitLab CI, David Kastrup, 2020/05/27
- Re: new procedure with GitLab CI, Dan Eble, 2020/05/27
Re: new procedure with GitLab CI, Valentin Villenave, 2020/05/29
Re: new procedure with GitLab CI, Han-Wen Nienhuys, 2020/05/29
Re: new procedure with GitLab CI, David Kastrup, 2020/05/29
Re: new procedure with GitLab CI, Jonas Hahnfeld, 2020/05/30
Re: new procedure with GitLab CI, Jonas Hahnfeld, 2020/05/30