Nexus upgrade

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Nexus upgrade

Ron Wheeler
Nexus has been very good to us over the years and has been no trouble at
all.
As a consequence we are still running 1.4.1.

It would seem to be a good idea to get up to a more current version.

Does anyone have any advice about the best upgrade path.
Should I just upgrade to the current version and let the automatic
procedures fix the database or should I upgrade to a few intermediate
releases on the way.

Ron

--
Ron Wheeler
President
Artifact Software Inc
email: [hidden email]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Nexus upgrade

Alexis Morelle
As far as I know you'll be ok with moving to the one you want (latest
for example) directly as long as you follow the upgrade notes of every
intermediate release.

https://docs.sonatype.com/display/SPRTNXOSS/Upgrading+Nexus

Alexis.

Le 16/02/2014 19:51, Ron Wheeler a écrit :

> Nexus has been very good to us over the years and has been no trouble
> at all.
> As a consequence we are still running 1.4.1.
>
> It would seem to be a good idea to get up to a more current version.
>
> Does anyone have any advice about the best upgrade path.
> Should I just upgrade to the current version and let the automatic
> procedures fix the database or should I upgrade to a few intermediate
> releases on the way.
>
> Ron
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Nexus upgrade

Manfred Moser-4
In reply to this post by Ron Wheeler

Wow.. that is VERY old. I would suggest to at least upgrade to 2.0 to get all the changes until then in and then further to the latest 2.7 version. Given that it is very old I would also look at the release notes from way back then. 

manfred

 

Ron Wheeler wrote on 2014-02-16 10:51:

Nexus has been very good to us over the years and has been no trouble at 
all.
As a consequence we are still running 1.4.1.
It would seem to be a good idea to get up to a more current version.
Does anyone have any advice about the best upgrade path.
Should I just upgrade to the current version and let the automatic 
procedures fix the database or should I upgrade to a few intermediate 
releases on the way.
Ron
-- 
Ron Wheeler
President
Artifact Software Inc
email: [hidden email]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]
--------------------------------------------------------------------- To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: Nexus upgrade

Ron Wheeler
That makes sense. It is a bit more work than jumping from very old to latest in one step but might save some grief.

We are not having any trouble so I am tempted to follow the advice "if it ain't broke, don't fix it" but it is a very old version as you pointed out.
Another one of those little projects that gets in the way of getting the real work done. :-)

Ron

On 17/02/2014 2:56 AM, Manfred Moser wrote:

Wow.. that is VERY old. I would suggest to at least upgrade to 2.0 to get all the changes until then in and then further to the latest 2.7 version. Given that it is very old I would also look at the release notes from way back then. 

manfred

 

Ron Wheeler wrote on 2014-02-16 10:51:

Nexus has been very good to us over the years and has been no trouble at 
all.
As a consequence we are still running 1.4.1.
It would seem to be a good idea to get up to a more current version.
Does anyone have any advice about the best upgrade path.
Should I just upgrade to the current version and let the automatic 
procedures fix the database or should I upgrade to a few intermediate 
releases on the way.
Ron
-- 
Ron Wheeler
President
Artifact Software Inc
email: [hidden email]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]
--------------------------------------------------------------------- To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email]


-- 
Ron Wheeler
President
Artifact Software Inc
email: [hidden email]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
Reply | Threaded
Open this post in threaded view
|

Re: Nexus upgrade

Manfred Moser-4

I would be much more tempted to advise that you want to upgrade in order to get the benefits of all the new features and enhancements as soon as possible. 

Anyway.. one of the things you will have to keep in mind is that you have to upgrade to run Nexus with Java 7. 

manfred

Ron Wheeler wrote on 2014-02-17 06:45:

That makes sense. It is a bit more work than jumping from very old to latest in one step but might save some grief.

We are not having any trouble so I am tempted to follow the advice "if it ain't broke, don't fix it" but it is a very old version as you pointed out.
Another one of those little projects that gets in the way of getting the real work done. :-)

Ron

On 17/02/2014 2:56 AM, Manfred Moser wrote:
 

Wow.. that is VERY old. I would suggest to at least upgrade to 2.0 to get all the changes until then in and then further to the latest 2.7 version. Given that it is very old I would also look at the release notes from way back then. 

manfred

 

Ron Wheeler wrote on 2014-02-16 10:51:

Nexus has been very good to us over the years and has been no trouble at 
all.
As a consequence we are still running 1.4.1.
It would seem to be a good idea to get up to a more current version.
Does anyone have any advice about the best upgrade path.
Should I just upgrade to the current version and let the automatic 
procedures fix the database or should I upgrade to a few intermediate 
releases on the way.
Ron
-- 
Ron Wheeler
President
Artifact Software Inc
email: [hidden email]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

--------------------------------------------------------------------- To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email]
 

-- 
Ron Wheeler
President
Artifact Software Inc
email: [hidden email]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
--------------------------------------------------------------------- To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email]
Reply | Threaded
Open this post in threaded view
|

RE: Nexus upgrade

Grierson, David
In reply to this post by Ron Wheeler

I recently jumped from 1.9.0.1 to 2.7.0-06 (the day before they released 2.7.1 damn-it!) with no significant issues.

 

I was lucky enough to be able to take a complete copy of my hosted repositories and perform a test upgrade against those to identify whether it would go through okay. It did.

 

I'd recommend that you do that if you can afford the disk space.

 

There were some index reformats performed and it appeared to make some (minor) changes to the hosted repositories' configurations – the Release repositories disabled Redeploy where it had previously been set manually. It also changed some of the authorization which had been custom set.

 

That said none of the changes were too bad as they were all in line with changes which I, ultimately, wanted to roll out anyway.


--
David Grierson – SDLC Tools Specialist

Sky Broadcasting - Customer Business Systems - SDLC Tools

Tel: +44 1506 325100 / Email: [hidden email] / Chatter: CBS SDLC Tools

Watermark Building, Alba Campus, Livingston, EH54 7HH

 

From: Ron Wheeler [mailto:[hidden email]]
Sent: 17 February 2014 14:45
To: [hidden email]
Subject: Re: [nexus-user] Nexus upgrade

 

That makes sense. It is a bit more work than jumping from very old to latest in one step but might save some grief.

We are not having any trouble so I am tempted to follow the advice "if it ain't broke, don't fix it" but it is a very old version as you pointed out.
Another one of those little projects that gets in the way of getting the real work done. :-)

Ron

On 17/02/2014 2:56 AM, Manfred Moser wrote:

Wow.. that is VERY old. I would suggest to at least upgrade to 2.0 to get all the changes until then in and then further to the latest 2.7 version. Given that it is very old I would also look at the release notes from way back then. 

manfred

 

Ron Wheeler wrote on 2014-02-16 10:51:

Nexus has been very good to us over the years and has been no trouble at 
all.
As a consequence we are still running 1.4.1.
It would seem to be a good idea to get up to a more current version.
Does anyone have any advice about the best upgrade path.
Should I just upgrade to the current version and let the automatic 
procedures fix the database or should I upgrade to a few intermediate 
releases on the way.
Ron
-- 
Ron Wheeler
President
Artifact Software Inc
email: [hidden email]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

--------------------------------------------------------------------- To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email]




-- 
Ron Wheeler
President
Artifact Software Inc
email: [hidden email]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102

Information in this email including any attachments may be privileged, confidential and is intended exclusively for the addressee. The views expressed may not be official policy, but the personal views of the originator. If you have received it in error, please notify the sender by return e-mail and delete it from your system. You should not reproduce, distribute, store, retransmit, use or disclose its contents to anyone. Please note we reserve the right to monitor all e-mail communication through our internal and external networks. SKY and the SKY marks are trademarks of British Sky Broadcasting Group plc and Sky International AG and are used under licence. British Sky Broadcasting Limited (Registration No. 2906991), Sky-In-Home Service Limited (Registration No. 2067075) and Sky Subscribers Services Limited (Registration No. 2340150) are direct or indirect subsidiaries of British Sky Broadcasting Group plc (Registration No. 2247735). All of the companies mentioned in this paragraph are incorporated in England and Wales and share the same registered office at Grant Way, Isleworth, Middlesex TW7 5QD.
Reply | Threaded
Open this post in threaded view
|

Re: Nexus upgrade

Ron Wheeler
Thanks for the encouraging words.

Ron

On 18/02/2014 5:25 AM, Grierson, David wrote:

I recently jumped from 1.9.0.1 to 2.7.0-06 (the day before they released 2.7.1 damn-it!) with no significant issues.

 

I was lucky enough to be able to take a complete copy of my hosted repositories and perform a test upgrade against those to identify whether it would go through okay. It did.

 

I'd recommend that you do that if you can afford the disk space.

 

There were some index reformats performed and it appeared to make some (minor) changes to the hosted repositories' configurations – the Release repositories disabled Redeploy where it had previously been set manually. It also changed some of the authorization which had been custom set.

 

That said none of the changes were too bad as they were all in line with changes which I, ultimately, wanted to roll out anyway.


--
David Grierson – SDLC Tools Specialist

Sky Broadcasting - Customer Business Systems - SDLC Tools

Tel: +44 1506 325100 / Email: [hidden email] / Chatter: CBS SDLC Tools

Watermark Building, Alba Campus, Livingston, EH54 7HH

 

From: Ron Wheeler [[hidden email]]
Sent: 17 February 2014 14:45
To: [hidden email]
Subject: Re: [nexus-user] Nexus upgrade

 

That makes sense. It is a bit more work than jumping from very old to latest in one step but might save some grief.

We are not having any trouble so I am tempted to follow the advice "if it ain't broke, don't fix it" but it is a very old version as you pointed out.
Another one of those little projects that gets in the way of getting the real work done. :-)

Ron

On 17/02/2014 2:56 AM, Manfred Moser wrote:

Wow.. that is VERY old. I would suggest to at least upgrade to 2.0 to get all the changes until then in and then further to the latest 2.7 version. Given that it is very old I would also look at the release notes from way back then. 

manfred

 

Ron Wheeler wrote on 2014-02-16 10:51:

Nexus has been very good to us over the years and has been no trouble at 
all.
As a consequence we are still running 1.4.1.
It would seem to be a good idea to get up to a more current version.
Does anyone have any advice about the best upgrade path.
Should I just upgrade to the current version and let the automatic 
procedures fix the database or should I upgrade to a few intermediate 
releases on the way.
Ron
-- 
Ron Wheeler
President
Artifact Software Inc
email: [hidden email]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

--------------------------------------------------------------------- To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email]




-- 
Ron Wheeler
President
Artifact Software Inc
email: [hidden email]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102

Information in this email including any attachments may be privileged, confidential and is intended exclusively for the addressee. The views expressed may not be official policy, but the personal views of the originator. If you have received it in error, please notify the sender by return e-mail and delete it from your system. You should not reproduce, distribute, store, retransmit, use or disclose its contents to anyone. Please note we reserve the right to monitor all e-mail communication through our internal and external networks. SKY and the SKY marks are trademarks of British Sky Broadcasting Group plc and Sky International AG and are used under licence. British Sky Broadcasting Limited (Registration No. 2906991), Sky-In-Home Service Limited (Registration No. 2067075) and Sky Subscribers Services Limited (Registration No. 2340150) are direct or indirect subsidiaries of British Sky Broadcasting Group plc (Registration No. 2247735). All of the companies mentioned in this paragraph are incorporated in England and Wales and share the same registered office at Grant Way, Isleworth, Middlesex TW7 5QD.


-- 
Ron Wheeler
President
Artifact Software Inc
email: [hidden email]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102