Hi, On Fri, 2020-12-04 at 14:59 +0700, btell...@linagora.com (OpenPaaS) wrote:
[...] > > > > Here is what I would like to do at this stage : > > - Isolate the unstable tests under with an unstable tag (akin to > > "feature > > tags") > I'd advocate a @Disabled tag, referencing both a JIRA ticket specific > to > the bugfix needed, and the JIRA of the CI build. > > Having a list of such issues in the JIRA (CI setup) ticket would be > valuable. I'd even advise doing subtickets to have a nice checklist. Let's say there's 10 unstable tests that will prevent the CI PR to be green, do you expect Jean to open 10 tickets with explanation of each problem? That would be a very high expectation. > > - exclude these tests from the default surefire execution profile, > > - add a parallel pipeline step for these tests where the step > > failure > > doesn't fail the pipeline [2] > > - ensure that the build is green > > - merge so the project finally has a working public CI > > > > I intend to start working on this quickly so we can all enjoy a > > functional > > public CI. > +1 I agree on the approach. I think we can event skip the "add a parallel pipeline step" part entirely. The simpler the better. [...] Cheers, -- Matthieu Baechler --------------------------------------------------------------------- To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
