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 178528 - The project does not use any supported version control system when using local Mercurial and trying to add new build to local Hudson
Summary: The project does not use any supported version control system when using loca...
Status: RESOLVED DUPLICATE of bug 161912
Alias: None
Product: connecteddeveloper
Classification: Unclassified
Component: Hudson (show other bugs)
Version: 6.x
Hardware: Macintosh Mac OS X
: P3 normal (vote)
Assignee: Jesse Glick
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-12 10:34 UTC by vernons
Modified: 2009-12-14 08:56 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Screenshot depicting error message when trying to create new Hudson build (56.95 KB, image/png)
2009-12-12 10:34 UTC, vernons 		Details
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 vernons 2009-12-12 10:34:22 UTC 
Created attachment 92463 [details]
Screenshot depicting error message when trying to create new Hudson build

After successfully creating a project locally and placing it under local version control with Mercurial, if you attempt to create a build in Hudson the dialog will display a message "The project does not use any supported version control system.", even after the project is properly initialized and committed to the version control system. 

Configuring Hudson directly from the Hudson web interface works as expected (Hudson is able to detect commits to the project which spawns automated builds).

The Continuous Build and Version Control systems should be more closely integrated so that local projects in distributed version control systems can be properly recognized as being version controlled and allow automatic deployment to the local Hudson instance.

(see attached screenshot for message)
Comment 1 Tomas Stupka 2009-12-14 03:31:57 UTC 
please evaluate
Comment 2 Jesse Glick 2009-12-14 08:56:58 UTC 
Currently refuses to create a job for a Mercurial repository with no paths.default.

*** This bug has been marked as a duplicate of bug 161912 ***