[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: new procedure with GitLab CI
From: |
Jonas Hahnfeld |
Subject: |
Re: new procedure with GitLab CI |
Date: |
Wed, 27 May 2020 10:56:57 +0200 |
User-agent: |
Evolution 3.36.2 |
Am Mittwoch, den 27.05.2020, 10:54 +0200 schrieb Valentin Villenave:
> On 5/27/20, Jonas Hahnfeld <address@hidden> wrote:
> > Pinging this to attention...
>
> Yeah, that’s one of those “I’ve read it without fully understanding
> it” situations (and then the discussion devolved into James’s workflow
> and I lost track).
>
> So IIUC there’s no way to skip the rebase-triggered CI pipeline right
> now? (I didn’t quite understand if the -skip option worked or not in
> that case.)
We do want to have the pipeline on the commit before it is merged
because this replaces patchy. The only limitation is that all MRs are
checked individually.
> Or are we willing to accept situations where, in case of a fairly
> trivial rebase where side-effects are absolutely unlikely, people
> could manually stop the pipeline as soon as it starts, and force the
> merge to happen immediately?
This shouldn't and fortunately doesn't work, see above.
Jonas
signature.asc
Description: This is a digitally signed message part
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 <=
- Re: new procedure with GitLab CI, Valentin Villenave, 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, 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