Problem with different Subversion credentials

[Reinhard Nägele]

Hello,

We are currently evaluating Hudson. It looks pretty promising, but there is one thing that is a showstopper for us at the moment.

We'd like to use Hudson for many projects, all of which having different subversion repositories and credentials. Now, when I create a build and enter the Subversion URL, Hudsons asks for credentials if necessary. The problem now is that Hudson seems to lose or mix up these credentials. When I configure a build and run it, all is fine, but subsequently all other build will fail because the SVN checkout fails. All builds had originally been configured with the correct credentials.

I understand that Hudson is supposed to remember credentials for different repositories. So, something seems to go wrong here. I'll appreciate any assistance to solve this issue.

Thanks,
Reinhard

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[Reinhard Nägele]

I just found this issue: http://issues.hudson-ci.org/browse/HUDSON-3865.
So, I disabled credentials caching, but that did not help. I then looked
at the config file of the Subversion plugin and notice that it only
contains one entry. Whenever I enter credentials for a build this file
is updated with these credentials, that is the old entry is replaced. I
would expect credentials for every repository to show up in the file.
The file has one entry as follows:

<entry>
<string>&lt;<a href="https://myserver:443&gt;">https://myserver:443&gt; Subversion repository</string>
<hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
<userName>myuser</userName>
<password>mypass</password>
</hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
</entry>

The problem seems to be that the key is the server
"https://myserver:443." All our repositories are on this server. They
all seem to be treated as one repository. How can I solve this problem.
Should I file a JIRA ticket?

Thanks,
Reinhard


On 29.04.2010 08:26, Reinhard Nägele wrote:

> Hello,
>
> We are currently evaluating Hudson. It looks pretty promising, but there is one thing that is a showstopper for us at the moment.
>
> We'd like to use Hudson for many projects, all of which having different subversion repositories and credentials. Now, when I create a build and enter the Subversion URL, Hudsons asks for credentials if necessary. The problem now is that Hudson seems to lose or mix up these credentials. When I configure a build and run it, all is fine, but subsequently all other build will fail because the SVN checkout fails. All builds had originally been configured with the correct credentials.
>
> I understand that Hudson is supposed to remember credentials for different repositories. So, something seems to go wrong here. I'll appreciate any assistance to solve this issue.
>
> Thanks,
> Reinhard
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>    

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[Ulli Hafner]

This seems to be not supported yet so please file a new feature request
in Jira...

Ulli

Reinhard Nägele wrote:

> I just found this issue:
> http://issues.hudson-ci.org/browse/HUDSON-3865. So, I disabled
> credentials caching, but that did not help. I then looked at the
> config file of the Subversion plugin and notice that it only contains
> one entry. Whenever I enter credentials for a build this file is
> updated with these credentials, that is the old entry is replaced. I
> would expect credentials for every repository to show up in the file.
> The file has one entry as follows:
>
> <entry>
> <string>&lt;<a href="https://myserver:443&gt;">https://myserver:443&gt; Subversion repository</string>
> <hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
> <userName>myuser</userName>
> <password>mypass</password>
> </hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
> </entry>
>
> The problem seems to be that the key is the server
> "https://myserver:443." All our repositories are on this server. They
> all seem to be treated as one repository. How can I solve this
> problem. Should I file a JIRA ticket?
>
> Thanks,
> Reinhard
>
>
> On 29.04.2010 08:26, Reinhard Nägele wrote:
>> Hello,
>>
>> We are currently evaluating Hudson. It looks pretty promising, but
>> there is one thing that is a showstopper for us at the moment.
>>
>> We'd like to use Hudson for many projects, all of which having
>> different subversion repositories and credentials. Now, when I create
>> a build and enter the Subversion URL, Hudsons asks for credentials if
>> necessary. The problem now is that Hudson seems to lose or mix up
>> these credentials. When I configure a build and run it, all is fine,
>> but subsequently all other build will fail because the SVN checkout
>> fails. All builds had originally been configured with the correct
>> credentials.
>>
>> I understand that Hudson is supposed to remember credentials for
>> different repositories. So, something seems to go wrong here. I'll
>> appreciate any assistance to solve this issue.
>>
>> Thanks,
>> Reinhard
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>    
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[Reinhard Nägele]

Thanks, Ulli, here's the ticket:

http://issues.hudson-ci.org/browse/HUDSON-6392

Hasn't this come up before? I think this is a pretty normal use case.

Reinhard

On 29.04.2010 11:44, Ullrich Hafner wrote:

> This seems to be not supported yet so please file a new feature
> request in Jira...
>
> Ulli
>
> Reinhard Nägele wrote:
>> I just found this issue:
>> http://issues.hudson-ci.org/browse/HUDSON-3865. So, I disabled
>> credentials caching, but that did not help. I then looked at the
>> config file of the Subversion plugin and notice that it only contains
>> one entry. Whenever I enter credentials for a build this file is
>> updated with these credentials, that is the old entry is replaced. I
>> would expect credentials for every repository to show up in the file.
>> The file has one entry as follows:
>>
>> <entry>
>> <string>&lt;<a href="https://myserver:443&gt;">https://myserver:443&gt; Subversion repository</string>
>> <hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
>> <userName>myuser</userName>
>> <password>mypass</password>
>> </hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
>> </entry>
>>
>> The problem seems to be that the key is the server
>> "https://myserver:443." All our repositories are on this server. They
>> all seem to be treated as one repository. How can I solve this
>> problem. Should I file a JIRA ticket?
>>
>> Thanks,
>> Reinhard
>>
>>
>> On 29.04.2010 08:26, Reinhard Nägele wrote:
>>> Hello,
>>>
>>> We are currently evaluating Hudson. It looks pretty promising, but
>>> there is one thing that is a showstopper for us at the moment.
>>>
>>> We'd like to use Hudson for many projects, all of which having
>>> different subversion repositories and credentials. Now, when I
>>> create a build and enter the Subversion URL, Hudsons asks for
>>> credentials if necessary. The problem now is that Hudson seems to
>>> lose or mix up these credentials. When I configure a build and run
>>> it, all is fine, but subsequently all other build will fail because
>>> the SVN checkout fails. All builds had originally been configured
>>> with the correct credentials.
>>>
>>> I understand that Hudson is supposed to remember credentials for
>>> different repositories. So, something seems to go wrong here. I'll
>>> appreciate any assistance to solve this issue.
>>>
>>> Thanks,
>>> Reinhard
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[justinedelson]

It's more 'normal' to have a single CI user account per repository
with read access to all projects.

On Apr 29, 2010, at 6:43 AM, "Reinhard Nägele" <[hidden email]
m> wrote:

> Thanks, Ulli, here's the ticket:
>
> http://issues.hudson-ci.org/browse/HUDSON-6392
>
> Hasn't this come up before? I think this is a pretty normal use case.
>
> Reinhard
>
> On 29.04.2010 11:44, Ullrich Hafner wrote:
>> This seems to be not supported yet so please file a new feature
>> request in Jira...
>>
>> Ulli
>>
>> Reinhard N�gele wrote:
>>> I just found this issue: http://issues.hudson-ci.org/browse/HUDSON-3865
>>> . So, I disabled credentials caching, but that did not help. I
>>> then looked at the config file of the Subversion plugin and notice
>>> that it only contains one entry. Whenever I enter credentials for
>>> a build this file is updated with these credentials, that is the
>>> old entry is replaced. I would expect credentials for every
>>> repository to show up in the file. The file has one entry as
>>> follows:
>>>
>>> <entry>
>>> <string>&lt;<a href="https://myserver:443&gt;">https://myserver:443&gt; Subversion repository</string>
>>> <hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
>>> <userName>myuser</userName>
>>> <password>mypass</password>
>>> </hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
>>> </entry>
>>>
>>> The problem seems to be that the key is the server "https://
>>> myserver:443." All our repositories are on this server. They all
>>> seem to be treated as one repository. How can I solve this
>>> problem. Should I file a JIRA ticket?
>>>
>>> Thanks,
>>> Reinhard
>>>
>>>
>>> On 29.04.2010 08:26, Reinhard N�gele wrote:
>>>> Hello,
>>>>
>>>> We are currently evaluating Hudson. It looks pretty promising,
>>>> but there is one thing that is a showstopper for us at the moment.
>>>>
>>>> We'd like to use Hudson for many projects, all of which having
>>>> different subversion repositories and credentials. Now, when I
>>>> create a build and enter the Subversion URL, Hudsons asks for
>>>> credentials if necessary. The problem now is that Hudson seems to
>>>> lose or mix up these credentials. When I configure a build and
>>>> run it, all is fine, but subsequently all other build will fail
>>>> because the SVN checkout fails. All builds had originally been
>>>> configured with the correct credentials.
>>>>
>>>> I understand that Hudson is supposed to remember credentials for
>>>> different repositories. So, something seems to go wrong here.
>>>> I'll appreciate any assistance to solve this issue.
>>>>
>>>> Thanks,
>>>> Reinhard
>>>>
>>>> ---
>>>> ------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [hidden email]
>>>> For additional commands, e-mail: [hidden email]
>>>>
>>>
>>>
>>> ---
>>> ------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[Reinhard Nägele]

No, I'd say it is not. We use our CI system to cut releases using the
Maven Release Plugin, i. e. the user must be able to commit and create
tags.

On 29.04.2010 13:52, Justin Edelson wrote:

> It's more 'normal' to have a single CI user account per repository
> with read access to all projects.
>
> On Apr 29, 2010, at 6:43 AM, "Reinhard Nägele"<[hidden email]
> m>  wrote:
>
>    
>> Thanks, Ulli, here's the ticket:
>>
>> http://issues.hudson-ci.org/browse/HUDSON-6392
>>
>> Hasn't this come up before? I think this is a pretty normal use case.
>>
>> Reinhard
>>
>> On 29.04.2010 11:44, Ullrich Hafner wrote:
>>      
>>> This seems to be not supported yet so please file a new feature
>>> request in Jira...
>>>
>>> Ulli
>>>
>>> Reinhard N�gele wrote:
>>>        
>>>> I just found this issue: http://issues.hudson-ci.org/browse/HUDSON-3865
>>>> . So, I disabled credentials caching, but that did not help. I
>>>> then looked at the config file of the Subversion plugin and notice
>>>> that it only contains one entry. Whenever I enter credentials for
>>>> a build this file is updated with these credentials, that is the
>>>> old entry is replaced. I would expect credentials for every
>>>> repository to show up in the file. The file has one entry as
>>>> follows:
>>>>
>>>> <entry>
>>>> <string>&lt;<a href="https://myserver:443&gt;">https://myserver:443&gt; Subversion repository</string>
>>>> <hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
>>>> <userName>myuser</userName>
>>>> <password>mypass</password>
>>>> </hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
>>>> </entry>
>>>>
>>>> The problem seems to be that the key is the server "https://
>>>> myserver:443." All our repositories are on this server. They all
>>>> seem to be treated as one repository. How can I solve this
>>>> problem. Should I file a JIRA ticket?
>>>>
>>>> Thanks,
>>>> Reinhard
>>>>
>>>>
>>>> On 29.04.2010 08:26, Reinhard N�gele wrote:
>>>>          
>>>>> Hello,
>>>>>
>>>>> We are currently evaluating Hudson. It looks pretty promising,
>>>>> but there is one thing that is a showstopper for us at the moment.
>>>>>
>>>>> We'd like to use Hudson for many projects, all of which having
>>>>> different subversion repositories and credentials. Now, when I
>>>>> create a build and enter the Subversion URL, Hudsons asks for
>>>>> credentials if necessary. The problem now is that Hudson seems to
>>>>> lose or mix up these credentials. When I configure a build and
>>>>> run it, all is fine, but subsequently all other build will fail
>>>>> because the SVN checkout fails. All builds had originally been
>>>>> configured with the correct credentials.
>>>>>
>>>>> I understand that Hudson is supposed to remember credentials for
>>>>> different repositories. So, something seems to go wrong here.
>>>>> I'll appreciate any assistance to solve this issue.
>>>>>
>>>>> Thanks,
>>>>> Reinhard
>>>>>
>>>>> ---
>>>>> ------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: [hidden email]
>>>>> For additional commands, e-mail: [hidden email]
>>>>>
>>>>>            
>>>>
>>>> ---
>>>> ------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [hidden email]
>>>> For additional commands, e-mail: [hidden email]
>>>>
>>>>          
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>>        
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>      
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>    

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]