Re: [virgo-dev] Should we request a HIPP for Virgo?

[Markus Knauer <mknauer@xxxxxxxxxxxxxxxxx>]

+1 ...

Being able to write directly into the download area makes all scripts much simpler... and I know the pain of NFS problems on the main shared Hudson cluster...

If I can be of any help with the move let me know.

Thanks,
Markus

On Tue, Dec 3, 2013 at 3:16 PM, Florian Waibel <fwaibel@xxxxxxxxxxxxxxxxx> wrote:

During the last week it was two times that the Virgo builds piled up in Hudson build queue.

Lot’s of other projects are currently moving to there own Hudson instance (HIPP - http://wiki.eclipse.org/Hudson#HIPP).

Currently a build job “hangs” with a successful build:

BUILD SUCCESSFUL
Total time: 3 minutes 52 seconds
[locks-and-latches] Releasing all the locks
[locks-and-latches] All the locks released
Archiving artifacts
…

A HIPP

* doesn’t use NFS mounts - no more stale NFS handles,
* comes with a newer Hudson version and could use cascading of job configurations (@see https://bugs.eclipse.org/bugs/show_bug.cgi?id=390895) and
* is allowed to write into the download area and/or the code repositories.

What do you think?

_______________________________________________
virgo-dev mailing list
virgo-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/virgo-dev