Any chance that the copy was made to a new machine, and that the new
machine does not allow you to create symbolic links?

I thought that the Windows default was to disallow the creation of symbolic
links and a specific action was required to allow symbolic links.

Mark Waite


On Mon, Apr 14, 2014 at 8:24 AM, Eric Wood <[email protected]> wrote:

> I have downloaded and installed a native install of Jenkins ... the
> current LTS version.  I copied the jobs folder from the current instance
> running under Tomcat to the new native install.  When it starts up I get
> the following errors in my log:
>
> SEVERE: Failed Loading job CCI-ctmsecrfwsclient_1.0-Release
> java.lang.NumberFormatException: For input string: ""
> at java.lang.NumberFormatException.forInputString(Unknown Source)
> at java.lang.Integer.parseInt(Unknown Source)
> at java.lang.Integer.parseInt(Unknown Source)
> at jenkins.model.PeepholePermalink.resolve(PeepholePermalink.java:87)
> at hudson.model.Job.getLastSuccessfulBuild(Job.java:833)
> at
> hudson.maven.AbstractMavenProject.createTransientActions(AbstractMavenProject.java:185)
>
> It appears that the "lastStable", "lastSuccessful" folders are no longer
> shortcuts by appear as mere files even though I copied the folder using
> robocopy with the /sl option for symbolic links.
>
> What is the proper upgrade path from a tomcat install to a native install
> and getting the production jobs under the new installation folder?
>
> Thanks, Eric
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Thanks!
Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to