Hi
I think that we need to change the setup in Hudson for Maven Plugins.
Currently there is a job [1] called "Maven-Plugins" which has a large
number of plugins as "Modules". This has benefits and drawbacks.
Benefits:
+ Only one configuration is needed per job, I think, totaling 1 in this
case.
Drawbacks:
- When anyone changes anything in any plugin (that is a "Module" in
Hudson) *all* the plugins are rebuilt. This leads to unnecessary SPAM on
[EMAIL PROTECTED] because Hudson send one e-mail per failed "Module".
- It puts an unnecessary load on the CI server.
I would like to remove the job "Maven-Plugins" and instead add a "tab",
or "view" as it is called in Hudson, called "Maven Plugins". Current
"views" include Forge, Maven, Maven 2.0.x, Maven 2.1x, Maven Artifact,
Maven IDE, Nexus, Plexus etc. Then we need to add one job, including
configuration, for each plugin. This should be a one time setup, but it
would improve the reports from Hudson regarding plugins.
Thoughts, opinions?
[1] http://ci.sonatype.org/job/Maven-Plugins/
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
