Reinstall jenkins (upgrade)...

[Scott Bell]

We recently had an old Hudson-Jenkins install (running on Windows Server 2k8 R2) go bad (Jenkins service refusing to start - copying back war file did not resolve as it used to when this would happen) and were unable to resolve the issue.

This installation pre-dates anyone currently on this project and I have to admit I am clueless as to how it is setup and works, so troubleshooting has been difficult.  I installed a fresh version of Jenkins (windows installer, latest) and moved over our jobs folder but am not able to get packages to build.  Jenkins starts, it sees the previous jobs and their properties seem intact, and Jenkins can see our SVN repositories and seems to be able to read them.  However, when we try to build it just doesn't see changes and doesn't output any builds. 

I tried several means of 'upgrading' - installing new version fresh and moving over the jobs folder - installing new version on top of old version in its location, and various degrees of switching war files and other folders and files back on top of a new install.  All yield the same result - Jenkins runs, sees the SVN repository, has the jobs info - but produces no builds.

Any suggestions?  If you had a bad install (old version, probably 2+ years) and wanted to just install fresh and move the stuff over what all needs to move (jobs folder, obviously ... but what else)?

[Curtis Kline]

Scott,

>> However, when we try to build it just doesn't see changes and doesn't output any builds.

I think troubleshooting this problem is going to require a console log from the affected jobs. Can you sanitize one and send it to this list?

>>  If you had a bad install (old version, probably 2+ years) and wanted to just install fresh and move the stuff over what all needs to move (jobs folder, obviously ... but what else)?

I would move the whole Jenkins home directory (the one above the jobs folder) into the new install. There are lots of xml files in there that define the system/plugin config.  On an older install this could be a huge amount of disk space, but most of that should be in the jobs folder. In there, only the config.xml files are crucial.

Curtis

--
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 jenkinsci-use...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Scott Bell]

I am sensitizing a console log now - will post shortly.  One the other suggestion - I pretty much tried all possible variations of fresh install and then copying back files and folders and the results are the same - jobs are there (am always moving the whole 'jobs' folder back in), it connects to SVN, no building.  I even tried installing new Jenkins right on top of the old installation, no joy.

[Scott Bell]

Attached

[Scott Bell]

Also, for the sake of adding more information - it looks like the original installation was done manually - there was a .hudson folder and Hudson folder in root of C: and a folder for ANT at C:\apache-ant-1.8.4 - before the 'clean' install I backed up all those then removed then - so now the clean install is at C:\Hudson.  The old XML files from the previous installation (at what was C:Hudson) are shown below:

(note shown, but there - Jenkins.xml, Hudson.xml, config.xml, and nodemonitor.xml)

I am going to try moving all files form the old directory back on top of this fresh install leaving just the new jenkins.war and jenkins.exe - will advise but I believe I tried that already to no avail.

[Scott Bell]

OK, I fixed it by doing the following ...

1) Clean install of latest Jenkins to same location as old install (in my case C:\Hudson)

2) Shut down Jenkins service, deleted all files in C:Hudson (post install)

3) Restored all Hudson-Jenkins files/folders from my backup (C:\.Hudson, C:\Hudson, C:\apache-ant-1.8.4)

4) Started Jenkins service and working normally again.

I am guessing that there is something the installer does, perhaps JAVA based, that manually uninstalling and reinstalling the service wasn't catching.