Bugzilla – Full Text Bug Listing
| Summary: | Required Hudson Plugins | ||
|---|---|---|---|
| Product: | Community | Reporter: | Eclipse Webmaster <webmaster> |
| Component: | CI-Jenkins | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | ci.admin-inbox, d_a_carver, sbouchet, stepper, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Eclipse Webmaster
SVN Maven (may be installed by default) FindBugs Dry XVNC Gerrit CVS (which I think is installed by default). Promote builds Checkstyle It's hard for me to see what of the functionality that I configured in my jobs are plugins or not. I seem to need these: - Collect compiler warnings - Colect TODOs - Archive artifacts - Publish JUnit results - Emma coverage - Twitter - Editable email notification It seems some folks have a different definition of the word "required". We don't need a list of the currently used plugins -- we see that in Hudson now. We need to know which ones _to start with_. Our new Hudson will begin with a modest set of plugins. We will have a sandbox area to test different plugins to ensure they do not affect system stability, because there is one plugin that we all need and that we don't have yet: QuitRestartingHudsonEvery2days plugin I think we should create three buckets and categorize plugins in one of the three: ABSOLUTELY IMPOSSIBLE TO RUN A BUILD WITHOUT THESE PLUGINS ========================================================== These would be your CVS, SVN and Git plugins, Xvnc etc. THESE PLUGINS PROVIDE FUNCTIONALITY THAT MAKE ME MUCH MORE PRODUCTIVE ===================================================================== These would include your FindBugs plugins, etc. THESE PLUGINS PROVIDE NEAT FUNCTIONALITY THAT IS NICE, BUT I CAN LIVE WITHOUT ============================================================================= This bucket would include Twitter & IRC notification. (In reply to comment #3) > It's hard for me to see what of the functionality that I configured in my jobs > are plugins or not. I seem to need these: > > - Collect compiler warnings > - Colect TODOs > - Archive artifacts > - Publish JUnit results These are built in. > - Emma coverage > - Twitter > - Editable email notification These are plugins. (In reply to comment #4) > > THESE PLUGINS PROVIDE FUNCTIONALITY THAT MAKE ME MUCH MORE PRODUCTIVE > ===================================================================== > These would include your FindBugs plugins, etc. > > > THESE PLUGINS PROVIDE NEAT FUNCTIONALITY THAT IS NICE, BUT I CAN LIVE WITHOUT > ============================================================================= > This bucket would include Twitter & IRC notification. These two areas aren't as cut and dry as you may think. Both of these provide information back to the community on the status of the builds, and communication of the builds and the quality of the builds is a requirement for many projects. I do agree that we need a limited set of plugins to start out with, but saying something isn't required is a matter of perspective an opinion. If we don't want Hudson doing Static Code Analysi (which is what FindBugs, Checkstyle, etc are), then eclipse needs to look at using and install a Sonar server to handle this load. Now with that said we do have many plugins that aren't used. So I do think it is good to get a list of all the plugins that are currently being used so we can get down to the ones that are used. Additional Required Plugin: URL Change Trigger - is required by the EPP packaging builds. (In reply to comment #4) (In reply to comment #2) ok, i will so update my list : > > ABSOLUTELY IMPOSSIBLE TO RUN A BUILD WITHOUT THESE PLUGINS > ========================================================== Promote plugin . > > > THESE PLUGINS PROVIDE FUNCTIONALITY THAT MAKE ME MUCH MORE PRODUCTIVE > ===================================================================== Checkstyle > > > THESE PLUGINS PROVIDE NEAT FUNCTIONALITY THAT IS NICE, BUT I CAN LIVE WITHOUT > ============================================================================= green balls, CI game So here's what's active in the 'base' install(according to the new master) CVS Plugin Maven 2 Project Plugin SSH Slaves plugin Hudson Subversion Plug-in -M. (In reply to comment #8) > So here's what's active in the 'base' install(according to the new master) > > CVS Plugin > Maven 2 Project Plugin > SSH Slaves plugin > Hudson Subversion Plug-in > > -M. So beyond that for version control you'll need the latest: Git URL Change Plugins It's important to use the latest version of the Git plugin as it resolves some slave serialization errors that were preventing builds from happening on slaves. After reading the suggestions(and then reading up on each plugin) here are the plugins I'm going to install: Audit Trail Disk usage Email-Ext Buckminster URL change Find bugs Dry Xvnc Promote builds Check style Git I do have a question however: what's the 'real' difference between Dry and Check style? They both seem to do the same thing(or at least very similar things). Would it be possible to keep one and remove the other? -M. (In reply to comment #10) > After reading the suggestions(and then reading up on each plugin) here are the > plugins I'm going to install: > > Audit Trail > Disk usage > Email-Ext > Buckminster > URL change > Find bugs > Dry > Xvnc > Promote builds > Check style > Git > > > I do have a question however: what's the 'real' difference between Dry and > Check style? They both seem to do the same thing(or at least very similar > things). Would it be possible to keep one and remove the other? > > -M. Checkstyle and Dry are different and do different type of reporting. Dry only reports copy and paste detected code. Checkstyle checks coding style type rules (indentation, formating, variable naming, etc). I've setup the new instance with the plugins I listed in comment #10. As such I'm going to close this bug. We'll handle requests for new plugins as we do with wiki extensions, file a bug, gather support and we'll go from there. -M. |