You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@archiva.apache.org by "Shelley, Ryan" <Ry...@disney.com> on 2010/09/08 01:35:28 UTC
Upgrading from 1.1
Hey folks,
I'm reading up on how to upgrade from 1.1 to 1.3.1. We currently have a problem where snapshots aren't being removed and I read that a bug was fixed to address this.
However, the documentation to upgrade to 1.3 is a little vague regarding updating the field lengths in the derby DB. I'm following the documentation here:
http://archiva.apache.org/docs/1.3.1/adminguide/upgrade.html
"If upgrading from a version lower than 1.2.2, you might also need to alter the lengths of the above fields as there is no upgrade task currently available for this."
How is it recommended that I do this? I've got the Derby "ij" console running but the JNDI configuration in jetty.xml reads:
<Set name="url">jdbc:derby:<SystemProperty name="appserver.base" default=".."/>/data/databases/archiva</Set>
There is no port, so I've tried a few options, but so far I always get "Connection refused". These are the connect driver/urls I've tried (where "<server>" is the hostname to my server running Archiva):
ij> connect 'jdbc:derby://<server>/data/databases/archiva';
ij> connect 'jdbc:derby://<server>:1527/data/databases/archiva';
Any suggestions? Thanks!
Ryan Shelley
RE: Upgrading from 1.1
Posted by "Shelley, Ryan" <Ry...@disney.com>.
Thanks Brett... I appreciate the clarification!
-----Original Message-----
From: Brett Porter [mailto:brett@porterclan.net] On Behalf Of Brett Porter
Sent: Tuesday, September 07, 2010 9:03 PM
To: users@archiva.apache.org
Subject: Re: Upgrading from 1.1
>From http://archiva.apache.org/docs/1.3.1/adminguide/repositories.html:
> Please take note that the by number of days old criteria is activated by default (set to 100 days). In order to de-activate it and use the by retention count criteria, you must set the Repository Purge By Days Older field to 0. Another thing to note here is that if the by number of days old criteria is activated, the retention count would still be respected (See the Repository Purge By Days Older section below for more details) but not the other way around.
So in your case, it'll keep the greater of the last 30 days worth, or the last 5 snapshots.
- Brett
On 08/09/2010, at 11:26 AM, Shelley, Ryan wrote:
> Ok, I'll give that a try. One last question. If we have the repository scan set to delete snapshots older than 30 days or 5 snapshots, which takes precedence? Say I have 100 snapshots evenly spaced out across 40 days. I'm assuming after the purge, I'd have 30 days worth of snapshots and the 5 snapshot count doesn't come into play? I'm thinking we have our snapshot retention set too high, as well.
>
> Thanks from the prompt response, Wendy. Much appreciated!
>
> -Ryan
>
> -----Original Message-----
> From: Wendy Smoak [mailto:wsmoak@gmail.com]
> Sent: Tuesday, September 07, 2010 6:04 PM
> To: users@archiva.apache.org
> Subject: Re: Upgrading from 1.1
>
> On Tue, Sep 7, 2010 at 8:39 PM, Shelley, Ryan <Ry...@disney.com> wrote:
>> Would I have to re-configure everything after the upgrade? Repositories and Users, etc?
>
> No, that's stored elsewhere. There is a separate user database, don't
> delete that one. The configuration is in archiva.xml in newer
> versions. I'm not that familiar with 1.1 to be honest.
>
> The database has the info for the .../browse/... urls, which it can
> re-construct when it scans all the poms.
>
> Now that I think of it, you'll probably want to delete the indexes
> also (in the .index directory?) and let it rebuild those as well.
>
> --
> Wendy
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
Re: Upgrading from 1.1
Posted by Brett Porter <br...@apache.org>.
From http://archiva.apache.org/docs/1.3.1/adminguide/repositories.html:
> Please take note that the by number of days old criteria is activated by default (set to 100 days). In order to de-activate it and use the by retention count criteria, you must set the Repository Purge By Days Older field to 0. Another thing to note here is that if the by number of days old criteria is activated, the retention count would still be respected (See the Repository Purge By Days Older section below for more details) but not the other way around.
So in your case, it'll keep the greater of the last 30 days worth, or the last 5 snapshots.
- Brett
On 08/09/2010, at 11:26 AM, Shelley, Ryan wrote:
> Ok, I'll give that a try. One last question. If we have the repository scan set to delete snapshots older than 30 days or 5 snapshots, which takes precedence? Say I have 100 snapshots evenly spaced out across 40 days. I'm assuming after the purge, I'd have 30 days worth of snapshots and the 5 snapshot count doesn't come into play? I'm thinking we have our snapshot retention set too high, as well.
>
> Thanks from the prompt response, Wendy. Much appreciated!
>
> -Ryan
>
> -----Original Message-----
> From: Wendy Smoak [mailto:wsmoak@gmail.com]
> Sent: Tuesday, September 07, 2010 6:04 PM
> To: users@archiva.apache.org
> Subject: Re: Upgrading from 1.1
>
> On Tue, Sep 7, 2010 at 8:39 PM, Shelley, Ryan <Ry...@disney.com> wrote:
>> Would I have to re-configure everything after the upgrade? Repositories and Users, etc?
>
> No, that's stored elsewhere. There is a separate user database, don't
> delete that one. The configuration is in archiva.xml in newer
> versions. I'm not that familiar with 1.1 to be honest.
>
> The database has the info for the .../browse/... urls, which it can
> re-construct when it scans all the poms.
>
> Now that I think of it, you'll probably want to delete the indexes
> also (in the .index directory?) and let it rebuild those as well.
>
> --
> Wendy
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
RE: Upgrading from 1.1
Posted by "Shelley, Ryan" <Ry...@disney.com>.
Ok, I'll give that a try. One last question. If we have the repository scan set to delete snapshots older than 30 days or 5 snapshots, which takes precedence? Say I have 100 snapshots evenly spaced out across 40 days. I'm assuming after the purge, I'd have 30 days worth of snapshots and the 5 snapshot count doesn't come into play? I'm thinking we have our snapshot retention set too high, as well.
Thanks from the prompt response, Wendy. Much appreciated!
-Ryan
-----Original Message-----
From: Wendy Smoak [mailto:wsmoak@gmail.com]
Sent: Tuesday, September 07, 2010 6:04 PM
To: users@archiva.apache.org
Subject: Re: Upgrading from 1.1
On Tue, Sep 7, 2010 at 8:39 PM, Shelley, Ryan <Ry...@disney.com> wrote:
> Would I have to re-configure everything after the upgrade? Repositories and Users, etc?
No, that's stored elsewhere. There is a separate user database, don't
delete that one. The configuration is in archiva.xml in newer
versions. I'm not that familiar with 1.1 to be honest.
The database has the info for the .../browse/... urls, which it can
re-construct when it scans all the poms.
Now that I think of it, you'll probably want to delete the indexes
also (in the .index directory?) and let it rebuild those as well.
--
Wendy
RE: Upgrading from 1.1
Posted by "Shelley, Ryan" <Ry...@disney.com>.
Thanks Wendy and Brett!
-----Original Message-----
From: Wendy Smoak [mailto:wsmoak@gmail.com]
Sent: Wednesday, September 08, 2010 5:30 PM
To: users@archiva.apache.org
Subject: Re: Upgrading from 1.1
On Wed, Sep 8, 2010 at 8:22 PM, Shelley, Ryan <Ry...@disney.com> wrote:
> Is there documentation on doing this? I didn't see much in the way of upgrading aside from 1.0 to 1.1 and 1.1 to 1.2.
http://archiva.apache.org/docs/1.3.1/adminguide/standalone.html
--
Wendy
Re: Upgrading from 1.1
Posted by Wendy Smoak <ws...@gmail.com>.
On Wed, Sep 8, 2010 at 8:22 PM, Shelley, Ryan <Ry...@disney.com> wrote:
> Is there documentation on doing this? I didn't see much in the way of upgrading aside from 1.0 to 1.1 and 1.1 to 1.2.
http://archiva.apache.org/docs/1.3.1/adminguide/standalone.html
--
Wendy
RE: Upgrading from 1.1
Posted by "Shelley, Ryan" <Ry...@disney.com>.
Is there documentation on doing this? I didn't see much in the way of upgrading aside from 1.0 to 1.1 and 1.1 to 1.2.
-----Original Message-----
From: Brett Porter [mailto:brett@porterclan.net] On Behalf Of Brett Porter
Sent: Wednesday, September 08, 2010 5:20 PM
To: users@archiva.apache.org
Subject: Re: Upgrading from 1.1
If you're using the standalone bundle, I recommend following the steps to separate the configuration so that upgrades in future don't require copying the data around too.
Cheers,
Brett
On 09/09/2010, at 4:00 AM, Shelley, Ryan wrote:
> Just to follow-up, I have completed my upgrade from 1.1 to 1.3.1 without problems.
>
> I shut down Archiva, backed up my data directory, removed the "archiva" database directory, removed the ".index" directories in the repositories, untarred the new archiva release, copied only the "archiva.xml" configuration over, moved the data directory over, then restarted Archiva. After restart, I re-ran the Repository Scans and Database Scan to rebuild the indexes and clean things up. Maven builds seem to be running just fine against the new version.
>
> Thanks for your input Wendy!
>
> -Ryan
>
> -----Original Message-----
> From: Wendy Smoak [mailto:wsmoak@gmail.com]
> Sent: Tuesday, September 07, 2010 6:04 PM
> To: users@archiva.apache.org
> Subject: Re: Upgrading from 1.1
>
> On Tue, Sep 7, 2010 at 8:39 PM, Shelley, Ryan <Ry...@disney.com> wrote:
>> Would I have to re-configure everything after the upgrade? Repositories and Users, etc?
>
> No, that's stored elsewhere. There is a separate user database, don't
> delete that one. The configuration is in archiva.xml in newer
> versions. I'm not that familiar with 1.1 to be honest.
>
> The database has the info for the .../browse/... urls, which it can
> re-construct when it scans all the poms.
>
> Now that I think of it, you'll probably want to delete the indexes
> also (in the .index directory?) and let it rebuild those as well.
>
> --
> Wendy
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
Re: Upgrading from 1.1
Posted by Brett Porter <br...@apache.org>.
If you're using the standalone bundle, I recommend following the steps to separate the configuration so that upgrades in future don't require copying the data around too.
Cheers,
Brett
On 09/09/2010, at 4:00 AM, Shelley, Ryan wrote:
> Just to follow-up, I have completed my upgrade from 1.1 to 1.3.1 without problems.
>
> I shut down Archiva, backed up my data directory, removed the "archiva" database directory, removed the ".index" directories in the repositories, untarred the new archiva release, copied only the "archiva.xml" configuration over, moved the data directory over, then restarted Archiva. After restart, I re-ran the Repository Scans and Database Scan to rebuild the indexes and clean things up. Maven builds seem to be running just fine against the new version.
>
> Thanks for your input Wendy!
>
> -Ryan
>
> -----Original Message-----
> From: Wendy Smoak [mailto:wsmoak@gmail.com]
> Sent: Tuesday, September 07, 2010 6:04 PM
> To: users@archiva.apache.org
> Subject: Re: Upgrading from 1.1
>
> On Tue, Sep 7, 2010 at 8:39 PM, Shelley, Ryan <Ry...@disney.com> wrote:
>> Would I have to re-configure everything after the upgrade? Repositories and Users, etc?
>
> No, that's stored elsewhere. There is a separate user database, don't
> delete that one. The configuration is in archiva.xml in newer
> versions. I'm not that familiar with 1.1 to be honest.
>
> The database has the info for the .../browse/... urls, which it can
> re-construct when it scans all the poms.
>
> Now that I think of it, you'll probably want to delete the indexes
> also (in the .index directory?) and let it rebuild those as well.
>
> --
> Wendy
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
RE: Upgrading from 1.1
Posted by "Shelley, Ryan" <Ry...@disney.com>.
Just to follow-up, I have completed my upgrade from 1.1 to 1.3.1 without problems.
I shut down Archiva, backed up my data directory, removed the "archiva" database directory, removed the ".index" directories in the repositories, untarred the new archiva release, copied only the "archiva.xml" configuration over, moved the data directory over, then restarted Archiva. After restart, I re-ran the Repository Scans and Database Scan to rebuild the indexes and clean things up. Maven builds seem to be running just fine against the new version.
Thanks for your input Wendy!
-Ryan
-----Original Message-----
From: Wendy Smoak [mailto:wsmoak@gmail.com]
Sent: Tuesday, September 07, 2010 6:04 PM
To: users@archiva.apache.org
Subject: Re: Upgrading from 1.1
On Tue, Sep 7, 2010 at 8:39 PM, Shelley, Ryan <Ry...@disney.com> wrote:
> Would I have to re-configure everything after the upgrade? Repositories and Users, etc?
No, that's stored elsewhere. There is a separate user database, don't
delete that one. The configuration is in archiva.xml in newer
versions. I'm not that familiar with 1.1 to be honest.
The database has the info for the .../browse/... urls, which it can
re-construct when it scans all the poms.
Now that I think of it, you'll probably want to delete the indexes
also (in the .index directory?) and let it rebuild those as well.
--
Wendy
Re: Upgrading from 1.1
Posted by Wendy Smoak <ws...@gmail.com>.
On Tue, Sep 7, 2010 at 8:39 PM, Shelley, Ryan <Ry...@disney.com> wrote:
> Would I have to re-configure everything after the upgrade? Repositories and Users, etc?
No, that's stored elsewhere. There is a separate user database, don't
delete that one. The configuration is in archiva.xml in newer
versions. I'm not that familiar with 1.1 to be honest.
The database has the info for the .../browse/... urls, which it can
re-construct when it scans all the poms.
Now that I think of it, you'll probably want to delete the indexes
also (in the .index directory?) and let it rebuild those as well.
--
Wendy
RE: Upgrading from 1.1
Posted by "Shelley, Ryan" <Ry...@disney.com>.
Would I have to re-configure everything after the upgrade? Repositories and Users, etc?
-Ryan
-----Original Message-----
From: Wendy Smoak [mailto:wsmoak@gmail.com]
Sent: Tuesday, September 07, 2010 5:37 PM
To: users@archiva.apache.org
Subject: Re: Upgrading from 1.1
On Tue, Sep 7, 2010 at 7:35 PM, Shelley, Ryan <Ry...@disney.com> wrote:
> Hey folks,
>
> I'm reading up on how to upgrade from 1.1 to 1.3.1. We currently have a problem where snapshots aren't being removed and I read that a bug was fixed to address this.
> However, the documentation to upgrade to 1.3 is a little vague regarding updating the field lengths in the derby DB. I'm following the documentation here:
> http://archiva.apache.org/docs/1.3.1/adminguide/upgrade.html
By far the easiest thing to do is just delete the database and let
Archiva re-create it. (I think you need to delete the entire
directory, not just the contents.) Will that work for you?
--
Wendy
Re: Upgrading from 1.1
Posted by Wendy Smoak <ws...@gmail.com>.
On Tue, Sep 7, 2010 at 7:35 PM, Shelley, Ryan <Ry...@disney.com> wrote:
> Hey folks,
>
> I'm reading up on how to upgrade from 1.1 to 1.3.1. We currently have a problem where snapshots aren't being removed and I read that a bug was fixed to address this.
> However, the documentation to upgrade to 1.3 is a little vague regarding updating the field lengths in the derby DB. I'm following the documentation here:
> http://archiva.apache.org/docs/1.3.1/adminguide/upgrade.html
By far the easiest thing to do is just delete the database and let
Archiva re-create it. (I think you need to delete the entire
directory, not just the contents.) Will that work for you?
--
Wendy