Bug 180628 - Uninformative error message in the New Continuous Build dialog
Uninformative error message in the New Continuous Build dialog
Status: NEW
Product: connecteddeveloper
Classification: Unclassified
Component: Hudson
6.x
All All
: P3 (vote)
: TBD
Assigned To: Jaroslav Havlin
issues@connecteddeveloper
: USABILITY
Depends on: 161912
Blocks:
  Show dependency treegraph
 
Reported: 2010-02-11 12:31 UTC by Petr Jiricka
Modified: 2012-06-14 16:43 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Jiricka 2010-02-11 12:31:21 UTC
The dialog displays the following message for me: "The project does not use any supported version control system." (I tried with projects which are in Mercurial and Git.)

It would be useful to show which version control systems are the supported ones (possibly as a link to an external web page).
Comment 1 Jesse Glick 2010-02-11 12:50:59 UTC
Perhaps you tried with a Mercurial repo that had no paths.default, which it would not really make sense to publish. Or a project which was a subdir of a repo - not supported currently since Hg does not support partial checkouts. In any event the messaging should be improved.
Comment 2 Petr Jiricka 2010-02-12 06:35:48 UTC
> Perhaps you tried with a Mercurial repo that had no paths.default

Yes, that was the case. I tried to remedy that by making the repository "remote" through hg serve + doing a clone, but that still did not work because

> a project which was a subdir of a repo

I did not realize that the first level of subdirectories is not supported; I think at least that would make sense (with the understanding that the whole repository would be checked out, which I think is fine), as source repositories are often set up that way. Not always the repository root equals the NB project.

Anyway, in this latter case the error message in the dialog is simply incorrect, so IMO this is a defect.
Comment 3 Jesse Glick 2010-02-12 10:17:10 UTC
See also bug #161912.

(In reply to comment #2)
> source repositories
> are often set up that way. Not always the repository root equals the NB
> project.

Indeed, but it is not clear how well this can really be supported. Besides the fact that the whole repo will be checked out - which may be a problem or may be correct - it is difficult for workspace path translation (used in console mode) to work when the Hudson workspace is not the NB project root. These more complex cases probably exceed the limits of what can be considered out-of-the-box functionality; it is very unlikely the IDE would set up the job the way you actually want.
Comment 4 crosati 2010-05-17 14:35:05 UTC
I have the same problem with projects stored into a CVS repository.

Any idea?

Claudio
Comment 5 Jesse Glick 2010-05-17 18:28:46 UTC
(In reply to comment #4)
> I have the same problem with projects stored into a CVS repository.

There is no support for CVS currently, sorry.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo