Jenkins - Failed to check out svn

[Roberto Schneiders]

I have a problem in Jenkins. When performing Build the following error is occurring:

ERROR: Failed to check out svn://svn.sysmo.com.br/trein/Jabox/project1/trunk/project1
org.tmatesoft.svn.core.SVNException: svn: E195012: Unable to find repository location for 'svn://svn.sysmo.com.br/trein/Jabox/project1/trunk/project1' in revision '61.243'

Draws attention to information "in revision 61.243"! This information seems to be wrong.. Project folders were created by Jabox in revision 61.244.
From where Jenkins fetches this information?
I found a setting in the project, SCM Repository Browser with the following value: "Redmine". 

If I change this property to AUTO, it works! But do not know what side effects it will cause.

The Jenkins looks for the revision number by Redmine?

Redmine should have a repository configured?  I do not have configured repositories.

Note: I'm using a version of Jabox with Jenkins, Sonar and Nexus updated due to compatibility with SVN 1.7. Could not update the Redmine because Jabox search this repository: http://www.jabox.org/repository/releases/org/redmine/redmine/  

https://github.com/jabox/jabox/pull/36

[Roberto Schneiders]

Firstly, the Jabox not create the repository in Redmine because the option (addRepositoryConfiguration) was unchecked in the server settings. There is a bug that does not let me change the server eRedMine. I corrected this problem and managed to change it. Unfortunately I faced another problem.

There are two files that have this setting: addRepositoryConfiguration.

.jabox\config.xml

.jabox\config\servers\Redmine.xml

What is the difference of these files? They have redundant information.

When editing the server, the changes the Jabox Redmine.xml.

When creating a new project, Jabox uses the config.xml.

I managed to create the project with the repository manually changing config.xml.

I can fix this, but I'm not sure what the difference between these files.

Once you get to create the project with the repository in Redmine, I found that this is not what causes the problem in Jenkins. The build is still failing.

The problem seems to be in the configuration settings in the SVN version of Jenkins. By default this property is 1.4, and I need it to be 1.7.

Could you tell me which class is responsible for recording this information in Jenkins?

What do you think to add a field in the configuration page to identify the Subversion repository version?