On Mon, May 9, 2011 at 5:54 AM, Josch <ARit...@gmx.net> wrote:
> Ok, I've completely undeployed the hudson and deployed the jenkins ci.
> It works and I can login. But the most of my projects are invisible.
Try updating your plugins, then restart.
-Jesse
--
There are 10 types of people in this world, those
that can read binary and those that can not.
On Wed, May 11, 2011 at 8:43 AM, Josch <ARit...@gmx.net> wrote:
>
> After two years a "never touch a running system" it was a bigger
> update session:
>
> Glassfish 3 to 3.1,
> Artifactory 2.1->2.3.x,
> Hudson to #Jenkins,
> new JDK (with jenkins auto install),
> Maven2 -> Maven3 (with jenkins auto install),
That's a lot of moving targets, but it sounds fun!
> Plugin updates and many restarts.
> Now the CI prod server back alive.
Aside from the many restarts required, I'm glad to hear it.
Congratulations, your users thank you.
If it helps anyone...
1. Upgraded glassfish from 3 to 3.1 (side-by-side upgrade)
- stopped the domains on glassfish 3 and created the domains on 3.1
- redeployed applications to 3.1 domains
2. Updated the user environment who will run Jenkins
- changed HUDSON_HOME to JENKINS_HOME and where to point to
- changed HUDSON_URL to JENKSIN_URL and where to point to
3. Deployed the jenkins war file to the jenkins domain
- At first, I deployed the hudson.war file and then updated using jenksins.war by renaming the file to hudson.war
but this wasn't a clean solution for me because I didn't want someone else or me to keep on renaming the war file
to take an upgrade. So the context path is now /jenkins instead of /hudson w/jenkins software.
4. Fixed any configuration (Configure System) within Jenkins that referenced hudson to be jenkins
- Example: Jenkins URL and Jenkins URL within email ext
5. Upgraded the plug-ins and restarted the jenkins domain. I first uninstalled any plug-ins that I don't use completely (removing
any disabled plug-ins directory within the $JENKINS_HOME/plugins directory. Having too many plug-ins disabled or not is
overwhelming for someone when managing (when to upgrade a plug-in) your plug-ins.
5. There wasn't really a smooth way in Glassfish to do a redirect for users who have /hudson saved in there
Bookmarks without creating a web app with a context path of /hudson. So I create a web app called hudsonRedirectToJenkins with
a context path of /hudson to redirect to /jenkins. I think I might go towards apache...
Jay