Skip to main content



      Home
Home » Archived » Hudson » Problems with SVN credentials and password parameters after upgrade
Problems with SVN credentials and password parameters after upgrade [message #1010834] Mon, 18 February 2013 05:06 Go to next message
Eclipse UserFriend
After testing Hudson 3 for a while we finally upgraded and are now facing a number of problems which did not occur during test. The difference is that for testing we used the embedded Jetty while the production system runs on Tomcat.

After the upgrade all password parameters in our jobs had wrong default values and SVN credentials did no longer work and had to be entered again for each job. With more than 300 jobs this is not exactly nice.

It looks like SVN credentials are saved differently now. After entering credentials again, an additional entry made it into subversion.credentials.

Reinhard
Re: Problems with SVN credentials and password parameters after upgrade [message #1010851 is a reply to message #1010834] Mon, 18 February 2013 05:42 Go to previous messageGo to next message
Eclipse UserFriend
Hi Reinhard,

It would be really great, if you add some error logs you are getting while performing the below steps.

I assume you are running the Hudson instance as a windows service. This issue could be caused because when a windows runs a service on start up, it executes as a "SYSTEM" user. So, the Hudson instance is executing as a "SYSTEM" user, and the certificate verification occurred on your username/password. Also if you go under the windows services window and use your login/password combination (See attached image). Under windows services right click Hudson -> properties -> Log On tab and login using "This account:" and specify your username/password combo.

HTH,

Regards,
Sidharth

[Updated on: Mon, 18 February 2013 05:43] by Moderator

Re: Problems with SVN credentials and password parameters after upgrade [message #1010853 is a reply to message #1010851] Mon, 18 February 2013 05:46 Go to previous messageGo to next message
Eclipse UserFriend
We are running under Linux.
Re: Problems with SVN credentials and password parameters after upgrade [message #1011040 is a reply to message #1010853] Mon, 18 February 2013 13:02 Go to previous messageGo to next message
Eclipse UserFriend
I believe you are storing the credentials on a per job basis. If you want to store subversion credentials for all the jobs to use, go to: http://localhost:8080/scm/SubversionSCM/enterCredential which will store the subversion.credentials file at the HUDSON_HOME folder instead of each individual job.
Re: Problems with SVN credentials and password parameters after upgrade [message #1011074 is a reply to message #1011040] Mon, 18 February 2013 14:58 Go to previous messageGo to next message
Eclipse UserFriend
Yes, we do store credentials per job, because this is what we need.
Re: Problems with SVN credentials and password parameters after upgrade [message #1011113 is a reply to message #1011074] Mon, 18 February 2013 17:02 Go to previous messageGo to next message
Eclipse UserFriend
Hi Reinhard, between bundled Jetty and Tomcat, there should not be any difference. But there were two releases of SVN plugin on Jan 23 & Feb 13. We are wondering if your test and production environment switch was some where with in these dates. We are also looking, if we inadvertently introduced an incompatible format for credential store between these releases.
Re: Problems with SVN credentials and password parameters after upgrade [message #1011800 is a reply to message #1011113] Wed, 20 February 2013 04:22 Go to previous messageGo to next message
Eclipse UserFriend
Meanwhile, we fixed our jobs. We noticed that the subversion.credentials files got an additional entry after updating the credentials. The first entry is the old one. So, the URL seems to be stored differently now. Why is this and why isn't this backwards-compatible?

<?xml version='1.0' encoding='UTF-8'?>
<hudson.scm.PerJobCredentialStore>
  <credentials class="hashtable">
    <entry>
      <string>&lt;http://mysvnhost:80&gt; Subversion repository</string>
      <hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
        <userName>...</userName>
        <password>...</password>
      </hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
    </entry>
    <entry>
      <string>http://mysvnhost/path/to/repo</string>
      <hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
        <userName>...</userName>
        <password>...</password>
      </hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
    </entry>
  </credentials>
</hudson.scm.PerJobCredentialStore>



Any clue what could be the problem with password build parameters I had also mentioned?

BTW, for the upgrade I installed Hudson from scratch and then copied over the existing jobs. Maybe this has caused the troubles?
Re: Problems with SVN credentials and password parameters after upgrade [message #1012016 is a reply to message #1011800] Wed, 20 February 2013 12:48 Go to previous messageGo to next message
Eclipse UserFriend
What version of hudson and the svn plugin did you upgrade from? I believe I might have found a bug where the
    <entry>
      <string>&lt;http://mysvnhost:80&gt; Subversion repository</string>
      <hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
        <userName>...</userName>
        <password>...</password>
      </hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
    </entry>
part actually gets stored in the hudson.scm.SubversionSCM.xml file instead of the credentials file where it should be.

[Updated on: Wed, 20 February 2013 12:48] by Moderator

Re: Problems with SVN credentials and password parameters after upgrade [message #1012327 is a reply to message #1012016] Thu, 21 February 2013 06:01 Go to previous messageGo to next message
Eclipse UserFriend
We updated from Hudson 2.1.2 and SVN Plugin 2.0.1.
icon13.gif  Re: Problems with SVN credentials and password parameters after upgrade [message #1383917 is a reply to message #1012327] Tue, 27 May 2014 04:05 Go to previous message
Eclipse UserFriend
Its really out of of my head as this post is still without any resolution or workaround. I updated to the latest war and faced the same issues and its really difficult for us to go back and change things out there. ALSO even we change things from front end it auto revert back and removes the values for password parameter and password itself. Is Hudson really to trust for comparing to jenkins ? Please help

Previous Topic:After I installed the Sonar Plugin there is no Sonar option in Hudson System Configurations
Next Topic:3.2.0 Milestone 1 is available for Testing
Goto Forum:
  


Current Time: Wed Jul 23 09:33:30 EDT 2025

Powered by FUDForum. Page generated in 0.05420 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top