This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 178803 - Hudson component should support the ClearCase version control system
Summary: Hudson component should support the ClearCase version control system
Status: RESOLVED WONTFIX
Alias: None
Product: connecteddeveloper
Classification: Unclassified
Component: Hudson (show other bugs)
Version: 6.x
Hardware: All All
: P4 normal (vote)
Assignee: Jesse Glick
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-17 13:09 UTC by mezlight
Modified: 2010-10-14 14:24 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description mezlight 2009-12-17 13:09:44 UTC 
I am not sure why the ClearCase version control system was not added to the Hudson component when there is a ClearCase plug-in to Netbeans.  Please add ClearCase support to the Hudson component.  Thanks...
Comment 1 Jesse Glick 2009-12-17 13:20:28 UTC 
CC support is not in the standard NB distribution, and its complexity and commercial nature will make it harder to test any integration. I do not plan to do so myself. Contributions welcome from CC experts; see hudson.subversion or hudson.mercurial modules as examples.
Comment 2 mezlight 2009-12-17 13:33:57 UTC 
(In reply to comment #1)
> CC support is not in the standard NB distribution, and its complexity and
> commercial nature will make it harder to test any integration. I do not plan to
> do so myself. Contributions welcome from CC experts; see hudson.subversion or
> hudson.mercurial modules as examples.

How does one go about getting the source code for the plug-in?
Comment 3 Jesse Glick 2009-12-17 13:47:32 UTC 
See for example:

http://hg.netbeans.org/cdev/file/default/hudson.mercurial/

The HudsonSCM service interface (in the hudson module, currently only exposed to known "friends") defines three things you can extend so far:

1. forFolder lets you configure SCM information on a newly created job based on what can be found in the working dir of the local project. Only useful for people using NB to create jobs, typically novice Hudson users with small projects.

2. translateWorkspacePath can be used to improve hyperlinking behavior in console output etc.

3. parseChangeSet can be used to display a changelog for a build in the IDE's Output Window.
Comment 4 Jesse Glick 2010-10-14 14:24:39 UTC 
I will not work on this myself.