Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cross-project-issues-dev] PLEASE READ: Old Hudson jobs, hudson-perf1-tests

Folks,

I have a few issues with Hudson that I plan on resolving shortly:


Issue 1:
Old jobs. There are jobs that haven't run in 8 months or more, and I
will purge them.  Please have a look at the job list, and if there are
jobs there that are no longer used, please let me know (via webmaster@)
and I will delete them.

Issue 2:
The hudson-perf1-tests slave is always idle, and no projects are tied to
it.  I had set it up with a dedicated CPU core to run performance
tests.  As I understand it, this slave is no longer needed, so I will
transform it into a regular build slave.

Issue 3:
I'm preparing to install a Hudson slave on the two IBM POWER servers at
the OSUOSL.  These remote slaves will not have access to /shared and
will not have signing capabilities (at least not initially).  We will,
however, install all the required build tools locally and these monster
boxes will be perfect for huge build jobs and tests.  In setting these
slaves up, am I correct in assuming your jobs are modular enough to take
advantage of remote server cycles without access to /shared and signing?

Thanks,

Denis


Back to the top