Sorry but that's not going to work. The Release field is in reference to
the TeamForge release area and is a user defined release name within
TeamForge. I work for CollabNet so I would be interested to here how you
expected it to work.
btw: I have switched this thread to jenkinsci-users which
gt; that level of granularity does each CTF project require a fee. And believe me
> it is not cheap...
>
> Take care
> Jan
>
> Am Donnerstag, 24. Mai 2012 16:27:58 UTC+2 schrieb Darryl Bowler:
> Have you seen this?
> http://wiki.hudson-ci.org/display/HUDSON/CollabNet+Plugin
n if I could split everything in TeamForge to smaller projects to reach
> that level of granularity does each CTF project require a fee. And believe me
> it is not cheap...
>
> Take care
> Jan
>
> Am Donnerstag, 24. Mai 2012 16:27:58 UTC+2 schrieb Darryl Bowler:
> Have you se
Have you seen this?
http://wiki.hudson-ci.org/display/HUDSON/CollabNet+Plugin -> Authentication
or
http://wiki.hudson-ci.org/display/HUDSON/Authentication
Look at "Authorize users at the project level"
Regards
On May 24, 2012, at 4:20 AM, Jan Seidel wrote:
> Hi folks,
>
> I've got a question.
:
> That is correct. It does have the appropriate URL and is a working one.
> Thanks
>
> From: jenkinsci-users@googlegroups.com
> [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Darryl Bowler
> Sent: Tuesday, May 22, 2012 12:54 PM
> To: jenkinsci-users@googlegro
> CollabNet FileRelease: Critical Error: login to https://collabnet.xyz.abc
> failed
I assume you have replaced "https://collabnet.xyz.abc"; with the URL to a
functional Teamforge server?
Regards
On May 22, 2012, at 2:35 PM, wrote:
> We are using Collabnet to upload the builds. Here is the in
