Jenkins SVN after changing the password the problem of the pit daddy

1. Prerequisites

The company SVN account password and ad account password are bound together, in order to ensure that the code check out is always up-to-date, Jenkins in the code before checking out the latest code from SVN.

Recently, the company asked the ad account must not use the original password, after changing the password, Jenkins in the checkout code when there is a pit Dad problem: Console printing problem is Subversion update has been canceled.

2. Reasons for Analysis

Subversion Update has been CANCELED--SVN code does not update properly, which is obviously a side effect of the SVN password change.

3. The efforts made

3.1 Modifying the configuration of Jenkins itself

After modifying all of Jenkins's account password information with SVN and restarting the Jenkins Service, the checkout code still has an error:Subversion update has been canceled.

These efforts failed, once dared not believe in life. Google for more than 10 minutes, because the company speed is too not to force (can spit trough it?) ), and did not get an answer with a reference value.

Calm down the mood, plan to start from the beginning analysis. Just very tangled: Jenkins the modified configuration has been modified, and ensure that there is no omission, why is not effective?

3.2 Re-analysis

Come up with a code check job carefully analyzed, the brain shows all the work done by Jenkins backstage, see the SVN Checkout strategy: Use' svn update ' as much as possible(usually not too much attention to this so-called strategy, Because the default is it), the tiger is a shock, there is!

This should be the time when Jenkins checked out, using the slave svn itself to check out the function, then I should go to modify the child node svn saved user password and other related data.

3.3 Starting again

Open slave svn client, setting→saved data→ Select "authentication data", click "Clear" → OK.

Enter SVN resp-browser, a box will pop up, let re-enter the account password, enter and tick save.

Build up the work in Jenkins again, and it's good enough!

　　Because the company computer can only be used in the intranet, can not, it is no longer.

4. Experience

① encounter problems should first analyze the possible causes, rather than direct Google. Be confident in yourself and believe in your ability to solve problems independently.

② again realized the advantages of the Jenkins/M architecture--master only responsible for scheduling management, slave responsible for specific implementation. This also provides two dimensions of thinking about the problems that Jenkins presents: The Master level and the slave level.

Jenkins SVN after changing the password the problem of the pit daddy