On 2 August 2017 at 13:28, Guillaume Smet <guillaume.s...@gmail.com> wrote: > On Wed, Aug 2, 2017 at 1:21 PM, Sanne Grinovero <sa...@hibernate.org> wrote: >> >> This might work for HV but please don't do this generally? >> Concurrently running builds will fail because of conflicting resource >> usage, >> and we had plenty of cases in which some ports are needd which you >> didn't even know about. > > > At least for all the projects using our unified release scripts it shouldn't > be an issue: we don't run the tests in the release process (you're supposed > to check that all the CI jobs are green before releasing). > > It might still be an issue though if you start resources even if the tests > are not running. Might be the case with OGM and Search.
Right, Search for example starts ES even if you skip tests (there's a JIRA to improve on that). But my point though is more about the unknowns: it's painful to figure out such things after the fact so we need to be careful with such jobs. > > -- > Guillaume _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
