On 19 March 2014 17:00, Emmanuel Bernard wrote:
> 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.
Good point: fixed
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!
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 wrote:
> hi everyone,
>
> I'll be happy to help with the activity of isolating build job in
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 l
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
