Re: [hibernate-dev] New CI slaves now available!

2018-01-04 Thread Yoann Rodiere
Great, thanks for all the work! Now that we have on-demand slave spawning, maybe we could get rid of our "hack" consisting in assigning 5 slots to each slave and a weight of 3 to each job? I would expect the website and release jobs to rarely wait in the queue, and if they do we can always set up

[hibernate-dev] Plans to release 5.2.13?

2018-01-04 Thread Gail Badner
We discussed stopping 5.2 releases at the F2F, but I can't remember what was decided. I see that there is a 5.2 branch. Should we be backporting to 5.2 branch? Thanks, Gail ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss

Re: [hibernate-dev] New CI slaves now available!

2018-01-04 Thread Steve Ebersole
Awesome Sanne! Great work. Anything you need us to do to our jobs? On Thu, Jan 4, 2018, 5:20 PM Sanne Grinovero wrote: > Hi all, > > we're having shiny new boxes running CI: more secure, way faster and > less "out of disk space" prolems I hope. > > # Slaves > > Slaves have been rebuilt from sc

[hibernate-dev] New CI slaves now available!

2018-01-04 Thread Sanne Grinovero
Hi all, we're having shiny new boxes running CI: more secure, way faster and less "out of disk space" prolems I hope. # Slaves Slaves have been rebuilt from scratch: - from Fedora 25 to Fedora 27 - NVMe disks for all storage, including databases, JDKs, dependency stores, indexes and journals

Re: [hibernate-dev] CDI integration in Hibernate ORM and the Application scope

2018-01-04 Thread Sanne Grinovero
On 4 January 2018 at 14:19, Steve Ebersole wrote: > Well there seems to be some disagreement about that. I personally think we > do not need anything other than a pre-shutdown hook so that we can release > our CDI references. Sanne seemed to think we needed something more > "integrated". I thin

Re: [hibernate-dev] CDI integration in Hibernate ORM and the Application scope

2018-01-04 Thread Sanne Grinovero
On 4 January 2018 at 16:39, Sanne Grinovero wrote: > On 4 January 2018 at 14:19, Steve Ebersole wrote: >> Well there seems to be some disagreement about that. I personally think we >> do not need anything other than a pre-shutdown hook so that we can release >> our CDI references. Sanne seemed

Re: [hibernate-dev] CDI integration in Hibernate ORM and the Application scope

2018-01-04 Thread Steve Ebersole
Well there seems to be some disagreement about that. I personally think we do not need anything other than a pre-shutdown hook so that we can release our CDI references. Sanne seemed to think we needed something more "integrated". I think we should start with the simple and add deeper integratio

Re: [hibernate-dev] CDI integration in Hibernate ORM and the Application scope

2018-01-04 Thread Scott Marlow
I can arrange to keep access to the specific ExtendedBeanManager/LifecycleListener, that is not difficult. What changes do we need from the CDI implementation? On Jan 3, 2018 4:36 PM, "Steve Ebersole" wrote: If you have access to the specific ExtendedBeanManager/LifecycleListener, that should a

Re: [hibernate-dev] ORM CI jobs - erroneous github triggers

2018-01-04 Thread Steve Ebersole
Lol. No idea why these are even built period. Thanks Sanne On Thu, Jan 4, 2018 at 6:13 AM Sanne Grinovero wrote: > Also these jobs were configured to build automatically every 5 hours: > - hibernate-orm-4.2-h2 > - hibernate-orm-4.3-h2 > > I removed the schedule, they will be built when (and

Re: [hibernate-dev] ORM CI jobs - erroneous github triggers

2018-01-04 Thread Sanne Grinovero
Also these jobs were configured to build automatically every 5 hours: - hibernate-orm-4.2-h2 - hibernate-orm-4.3-h2 I removed the schedule, they will be built when (and only when) anything is committed to their respective branches. On 3 January 2018 at 19:15, Steve Ebersole wrote: > Nice! Gl