Mark Struberg wrote:
I also second the wish to take ALL sandbox plugins under CI, not only the
actively maintained ones.
Does this make such a huge difference?
Sure, testing more is nice. Let's just keep in mind that this CI server
is not dedicated to Mojo plugins but it also used for Apache code and
Sonatype's own stuff. So I would rather start easy before putting the
entire collection of our 150 Mojo plugins onto Hudson. Not sure whether
that's the proper translation but when somebody offers you a helping
hand, you don't take the whole arm.
I mean if no checkins happen to a plugin, then CI will not be triggered at all.
To save us from the hassle of setting up individual Hudson jobs for each
plugin, we will do a reactor build. In the case of the non-sandbox
stuff, Hudson will be monitoring the entire SVN trunk and if a change is
detected, the reactor build will be fired, i.e. all selected plugins
will be build even if only the source of one of them has actually changed.
And there should be no broken (compile or tests fail) plugin anyway!
Hehe, that would be cool but I stopped believing that ;-)
Benjamin
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
