> On Sep 22, 2019, at 11:26 PM, Balay, Satish <ba...@mcs.anl.gov> wrote: > > Even-though a fix addresses a breakage in a single build - that change > could break other things so its generally best to run a full test. Sure before a merge we want everything tested but when one is iterating on a single bug it would be a much better use of resources > > However if I need to run a single (or a few) test(s) - I would do [not > an elegant solution you are looking for]: > > - start a new pipeline with the fix > - cancel this pipeline > - restart only the selected runs [within this pipeline] YES! > > The status in the MR will reflect that the pipeline failed [due to all the > other canceled jobs] > > Satish > > On Mon, 23 Sep 2019, Smith, Barry F. via petsc-dev wrote: > >> >> When you fix something on a branch that broke a particular job in >> gitlab-ci it would be nice to be able to run that single job on the updated >> branch instead of having to submit an entirely new pipeline >> >> Does this exist? Should this be requested in gitlab-ci issues? Could we >> make a work around where we hack .gitlab-ci.yml based on a variable to >> return immediately except on the one truly desired job? >> >> >> >> >> >
Re: [petsc-dev] It would be really nice if you could run a single job on the pipeline with a branch
Smith, Barry F. via petsc-dev Sun, 22 Sep 2019 21:35:37 -0700
- [petsc-dev] It would be really nice if you c... Smith, Barry F. via petsc-dev
- Re: [petsc-dev] It would be really nice... Balay, Satish via petsc-dev
- Re: [petsc-dev] It would be really ... Smith, Barry F. via petsc-dev
- Re: [petsc-dev] It would be rea... Jed Brown via petsc-dev
- Re: [petsc-dev] It would be... Smith, Barry F. via petsc-dev