Error in Build process using Release Manager Plugin

[boby...@gmail.com]

Hello Folks,

I have an issue in compiling the code and I am not sure on which revision error was introduced or committed on SVN. For debugging the issue i wanted to perform the build per revision.

As I have the revision where last build was successful. Below was my approach to find the issue.

1. Tag the revision and re-try building the entire project and see results. This approach is very Lengthy, Space and Time Consuming.

2. Use Release Manager Plugin to build the project per revision. This is much faster approach as i can see all the revision on Jenkins i want to build from.

I Have below two issues.

1. My build needs SVN_URL parameter which is not pulled automatically they way build process does if i do build using normal configuration.

2. I tried fixing this issue by declaring the variable SVN_URL in Global parameter section but i am getting below error right in middle of checkout. Can someone help me please.

My Subversion version is 1.7 and 1.5 Jenkins.

FATAL: org.tmatesoft.svn.core.wc.SVNEvent.getExternalInfo()Lorg/tmatesoft/svn/core/internal/wc/SVNExternal;
java.lang.NoSuchMethodError: org.tmatesoft.svn.core.wc.SVNEvent.getExternalInfo()Lorg/tmatesoft/svn/core/internal/wc/SVNExternal;
	at hudson.scm.SubversionReleaseUpdateEventHandler.handleEvent(SubversionReleaseUpdateEventHandler.java:56)
	at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.handleEvent(SvnOperationRunner.java:61)
	at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.handleEvent(SvnOperationRunner.java:66)
	at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.handleExternalItemChange(SvnNgAbstractUpdate.java:369)
	at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.handleExternalsChange(SvnNgAbstractUpdate.java:310)
	at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.handleExternals(SvnNgAbstractUpdate.java:246)
	at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.updateInternal(SvnNgAbstractUpdate.java:224)
	at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.update(SvnNgAbstractUpdate.java:72)
	at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.checkout(SvnNgAbstractUpdate.java:802)
	at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:26)
	at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:11)
	at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20)
	at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21)
	at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1259)
	at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294)
	at org.tmatesoft.svn.core.wc.SVNUpdateClient.doCheckout(SVNUpdateClient.java:777)
	at org.tmatesoft.svn.core.wc.SVNUpdateClient.doCheckout(SVNUpdateClient.java:662)
	at hudson.scm.SubversionReleaseSCM$CheckOutTask.invoke(SubversionReleaseSCM.java:493)
	at hudson.scm.SubversionReleaseSCM$CheckOutTask.invoke(SubversionReleaseSCM.java:414)
	at hudson.FilePath.act(FilePath.java:989)
	at hudson.FilePath.act(FilePath.java:967)
	at hudson.scm.SubversionReleaseSCM.checkout(SubversionReleaseSCM.java:407)
	at hudson.scm.SubversionReleaseSCM.checkout(SubversionReleaseSCM.java:356)
	at hudson.model.AbstractProject.checkout(AbstractProject.java:1270)
	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:609)
	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:531)
	at hudson.model.Run.execute(Run.java:1741)
	at hudson.matrix.MatrixBuild.run(MatrixBuild.java:306)
	at hudson.model.ResourceController.execute(ResourceController.java:98)
	at hudson.model.Executor.run(Executor.java:374)
Finished: FAILURE

[Andrey Belyaevskiy]

Hi! 

I faced to same issue. But I use Jenkins 2.1. One thing I do not understand how subversion release manager plugin pick up credentials to access repository. Nothing ask me about login/password for it. And one more strange thing that I see continuously launched builds with message:

Workspace doesn't contain <my repo link>. Need a new build
Done. Took 49 ms

Does anyone know another way to view and select available revisions from jenkins?