2012/2/17 Denis Roy <[email protected]> > On 02/17/2012 01:02 PM, David M Williams wrote: > >> Thought would be easy to use the production master > >> & slaves and the production memory dump would give real scenario. > > Sure. Easier. And by all means, I don't mind ... if just once. I would > just > > hate > > to see our production server progressively become the Hudson project's > > "test server" ... they should have > > their own test server :) > As Hudson is an Eclipse project, webmasters are willing to share the > keys to our current sandbox [1] with the Hudson team for their > testing/debugging. Our sandbox also has one active slave, but the > entire environment is very idle. > > [1] https://hudson.eclipse.org/sandbox/ > _______________________________________________ > cross-project-issues-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev >
We could easily put some load on sandbox if we move back our gerrit verification jobs for the jgit and egit projects from main hudson to sandbox hudson. These jobs start whenever a new or updated change is uploaded to Gerrit for code review. The jobs which have been migrated to main hudson last week anyway don't work properly yet. Could you adjust the gerrit-trigger plugin configuration of sandbox hudson to point at the shiny new Gerrit server and upload it's public key to Gerrit ? Then I will revive the verification build jobs and we'll create some load on sandbox hudson so that the Hudson team has some real traffic to monitor. -- Matthias
_______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
