Re: [cross-project-issues-dev] CVS triggers broken in Hudson ... fixed

[David M Williams <david_williams@xxxxxxxxxx>]

Thanks to our fast acting hudson admins, the CVS trigger problem is fixed, and you should not have to manually start an aggregation build.

Of course, you still can, if you don't want to wait 15 minutes :) [or, if you make a change to your repo, but not your cvs file] but do please bring it to our attention if things don't seem to be triggered in a timely fashion.

Thanks,


David M Williams---11/01/2011 02:52:53 AM---Apparently there is a "CVS trigger" problem with the Hudson 2.1.0 we are using, I've documented the

From: David M Williams/Raleigh/IBM@IBMUS
To: cross-project-issues-dev@xxxxxxxxxxx
Date: 11/01/2011 02:52 AM
Subject: [cross-project-issues-dev] CVS triggers broken in Hudson ... so feel free to "manually" start SimRel jobs
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

---

Apparently there is a "CVS trigger" problem with the Hudson 2.1.0 we are using, I've documented the issue in bug 362409 [1].

I have set the "Juno Aggregator" to run once every 8 hours ... but I think most of us are used to the "automatic" continuous builds, which won't work until Hudson is upgraded again (as far as I know). 

So, in the mean time, anyone who can "commit" to the Juno aggregation build should be able to "manually" start a build from the Hudson page at 

https://hudson.eclipse.org/hudson/view/Repository%20Aggregation/job/juno.runAggregator/

I just wanted to mention it here on this list, since I know some of you will be updating for M3 soon. 

Thanks, 

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=362409
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev