CODEWITHSUNDEEP
jenkinssvnjobssvn-checkout
Joaquín
Joaquín

Reputation: 336

Jenkins job disables itself when svn checkout fails

My jenkins jobs started to disable by themselves when the svn checkout fails. I explored previous builds and they never disabled when failed. This new behaviour is not desired for me.

The message in the new build log is as follows:

...
One or more repository locations do not exist anymore for myJob1, project will be disabled.
The project has been disabled
ERROR: Failed to parse svn info for 'repourl'
...

I downgraded the jenkins Subversion plugin which was recently updated, and the multi scm plugin as well. However, the problem remains.
Any suggestion?

Upvotes: 2

Views: 1080

Answers (2)

Blue
Blue

Reputation: 887

I think this is an undocumented(?) behavior of the Subversion Plugin to automatically disable a job if the SVN URL is not valid (anymore). This behavior seems to be implemented for several years now, as this discussion from 2012 indicates. I just learned about this behavior only after moving a SVN project to a different folder which caused my project to be disabled. I did not find any information on how to disable this behavior.

Update 2021/09:

The behavior is apparently still present and there seems to be no way to disable it. There is a corresponding feature request on the Jenkins JIRA though: JENKINS-10922

Please vote for this feature request!

Upvotes: 0

Jeanne Boyarsky
Jeanne Boyarsky

Reputation: 12266

That message is coming from the Blame Subversion Plugin. Is it possible you recently installed that plugin? Or that you recently turned on SVN blame as an option?

Upvotes: 2

Related Questions