Hi everyone,
Here are the minutes of the biweekly NoORM IRC meeting:
16:06 < jbott> Meeting ended Tue Jan 16 15:05:30 2018 UTC. Information
about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
16:06 < jbott> Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2018
Did you happen to do the same for Gradle caches?
Some jobs are failing:
* What went wrong:
Could not resolve all dependencies for configuration
':buildSrc:runtimeClasspath'.
> Timeout waiting to lock artifact cache
> (/efs-maven-artifacts/.gradle/caches/modules-2). It is currently in use by
>
On 01/12/2018 12:54 PM, Sanne Grinovero wrote:
> On 12 January 2018 at 17:32, Brett Meyer wrote:
>> If I don't have time to contribute to Pax Exam, I certainly don't have
>> time to start a new project haha...
>>
>> And realistically, that "something new" would likely involve containers
>> anyway.
2018-01-15 11:54 GMT+01:00 Yoann Rodiere :
> > We should reconfigure those to not "install" - that's actually a bad
> > habit, legacy from Maven 2 times - people nowadays recommend using
> > "mvn clean verify", especially on CI environments.
>
> I could not agree more, that would be cleaner, but t
Yes I did it for Gradle too, sorry. The `/efs-maven-artifacts` is the
guilty mount point.
I don't know any quick solutions for the various concerns you all
raised, so I'll roll this back tonight.
It's good to know that it's not too hard to have a shared FS between
these machines; needs better pla
well Gradle is used in CI environments all over the place, so it must
work. But I think we need some different configurations in the Gradle
command used. For example, it is highly suggested that the Gradle daemon
be disabled in CI but I'm not sure all of our jobs actually do that. I'll
look into
On 16 January 2018 at 21:33, Steve Ebersole wrote:
> well Gradle is used in CI environments all over the place, so it must work.
> But I think we need some different configurations in the Gradle command
> used. For example, it is highly suggested that the Gradle daemon be
> disabled in CI but I'm
Version F27v17 of the slaves is running now, with NFS drive removed.
sorry for the experiment :)
Thanks
Sanne
On 16 January 2018 at 21:51, Sanne Grinovero wrote:
> On 16 January 2018 at 21:33, Steve Ebersole wrote:
>> well Gradle is used in CI environments all over the place, so it must work.
