That's it, thanks!
On Fri, Jun 24, 2016 at 11:13 AM Sanne Grinovero
wrote:
> On 24 June 2016 at 16:40, Steve Ebersole wrote:
> > I definitely want it run regularly (i.e. not "just before a release").
> I'd
> > be ok with it being nightly. That's why I
On 24 June 2016 at 16:40, Steve Ebersole wrote:
> I definitely want it run regularly (i.e. not "just before a release"). I'd
> be ok with it being nightly. That's why I asked in the first place.
> Everyone who responded +1'd to it being on-each-push. I really don't care.
>
I definitely want it run regularly (i.e. not "just before a release"). I'd
be ok with it being nightly. That's why I asked in the first place.
Everyone who responded +1'd to it being on-each-push. I really don't
care. I tend to agree it should be nightly, but I only get one vote :)
So the one
If check is so compute intensive, does it really have to be done on each
commit? When I've seen failures, it has been easy to figure out what is
wrong. Can the check job be done nightly, or on demand (e.g., before a
release)?
On Sat, Jun 18, 2016 at 11:20 AM, Steve Ebersole
http://ci.hibernate.org/job/hibernate-orm-master-h2-main/
http://ci.hibernate.org/job/hibernate-orm-master-h2-check/
Initial attempt
On Sat, Jun 18, 2016 at 12:58 PM Sanne Grinovero
wrote:
> On 18 June 2016 at 18:50, Chris Cranford wrote:
> > +1
> >
>
On 18 June 2016 at 18:50, Chris Cranford wrote:
> +1
>
> I think (1) and (2) on each push still makes sense with (3) being nightly.
+1
-- Sanne
>
> Chris
>
>
> On 06/18/2016 11:33 AM, Steve Ebersole wrote:
>> We have been having a lot of timeouts on the ORM CI builds.
+1 too.
On Sat, Jun 18, 2016 at 8:50 PM, Chris Cranford wrote:
> +1
>
> I think (1) and (2) on each push still makes sense with (3) being nightly.
>
> Chris
>
>
> On 06/18/2016 11:33 AM, Steve Ebersole wrote:
> > We have been having a lot of timeouts on the ORM CI builds.
+1
I think (1) and (2) on each push still makes sense with (3) being nightly.
Chris
On 06/18/2016 11:33 AM, Steve Ebersole wrote:
> We have been having a lot of timeouts on the ORM CI builds. Mainly this is
> due to ancillary tasks. Currently the ORM jobs execute:
>
> 1. clean
> 2.
We have been having a lot of timeouts on the ORM CI builds. Mainly this is
due to ancillary tasks. Currently the ORM jobs execute:
1. clean
2. test
3. check
4. :documentation:aggregateJavadocs
5. publish
A huge chunk of the time is taken up in (3) which performs (a) checkstyle