Re: [cross-project-issues-dev] PLEASE READ: Old Hudson jobs, hudson-perf

[Trip Gilman <trip@xxxxxxxxxxxxxxx>]

Denis,

We have a target platform (for buckminster) job that really doesn't need
to run unless the platform itself changes. However if this job is removed,
the target platform is removed from the buckminster meta-data and will
cause the main build jobs to fail.  I'm not sure how this affects what you
want to do overall.

Trip Gilman

On 2/9/12 8:39 AM, "Denis Roy" <denis.roy@xxxxxxxxxxx> wrote:

>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
>_______________________________________________
>cross-project-issues-dev mailing list
>cross-project-issues-dev@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev