[hibernate-dev] ci.hibernate.org and network port assignment

[Emmanuel Bernard]

Is it possible to do something a little smarter and let the website jobs
run in parallel to this port cock fight builds?
I got stuck behind an ORM job that turn out to just fail after 30 mins
for some reasons I did not get.

Emmanuel

On Wed 2014-03-19 14:56, Sanne Grinovero wrote:
> Thanks Paolo!
> 
> @All, since we now have a single executor on the CI server, I've
> enforced a 90 minutes timeout on the ORM build job (master) as it
> occasionally hangs.
> 
> On 18 March 2014 22:49, Paolo Antinori <paolo.antinori at gmail.com> wrote:
> > hi everyone,
> >
> > I'll be happy to help with the activity of isolating build job in docker
> > containers started directly via jenkins.
> >
> > The technology should allow concurrent  build job totally isolated, as
> > anticipated.
> >
> > I am going to start with OGM that is the project I am more familiar with
> > and I will let you know of eventual achievement.
> >
> >
> > paolo
> >
> >
> >
> > I've created WEBSITE-178 [1] as once again we had testsuites failing
> > because of a network port being used by a different job; bad luck, but
> > we can do better.
> >
> > Assuming we want to use the Jenkins plugin "port allocator", this
> > would however need to be consistently honored by all builds we launch:
> > it passes variables which we should use, but it can't enforce them
> > AFAIK.
> >
> > Is that going to be maintanable in the long run?
> >
> > An alternative would be to consistently run each and every build in
> > its own isolated docker container, but
> > a) that's not something I can setup overnight
> > b) we'd need to use more complex build scripts, for example the nice
> > Maven and Gradle integrations with the Jenkins build configuration
> > would be unusable.
> >
> > We're having quite a list of services; even ignoring the OGM exotic
> > databases we have at least:
> >  - Byteman
> >  - JGroups
> >  - Arquillian
> >  - WildFly
> >  - ActiveMQ (JMS tests in Search)
> >  - ... ?
> >
> > To fight the urgent need, I'm going to prevent parallelism of any
> > build. Let's hope ORM's master doesn't get stuck, as everything else
> > would be blocked. I really hope this measure stays as temporary as
> > possible :-/
> >
> > -- Sanne
> > _______________________________________________
> > hibernate-dev mailing list
> > hibernate-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev