db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ole Solberg (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3982) Add a facility to override the default set of old versions to be tested in the upgrade tests.
Date Fri, 12 Dec 2008 10:51:44 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655969#action_12655969
] 

Ole Solberg commented on DERBY-3982:
------------------------------------

A short writeup on usage:


a)  -DderbyTesting.oldReleasePath=/usr/local/share/java/derby/lib -DderbyTesting.oldVersionsPath=/usr/local/share/java/derby/lib/versions
     Use jars at /usr/local/share/java/derby/lib and  test upgrade from the versions listed
in /usr/local/share/java/derby/lib/versions
     'versions' might look like this:
# Ignore lines not matching the regexp: "^[\\d]+\\.[\\d]+\\.[\\d]+\\.[\\d]"
10.0.2.1 // 10.0.2.1 (incubator release)
10.1.1.0 // 10.1.1.0 (Aug 3.2005 / SVN 208786)
10.1.2.1 // 10.1.2.1 (Nov 18.2005 / SVN 330608)
10.1.3.1 // 10.1.3.1 (Jun 30.2006 / SVN 417277)
10.2.1.6 // 10.2.1.6 (Oct 02.2006 / SVN 452058)
10.2.2.0 // 10.2.2.0 (Dec 12.2006 / SVN 485682)
10.2.2.1 // (Special test version / SVN 538595)
10.3.1.4 // 10.3.1.4 (Aug 1.2007 / SVN 561794)
10.3.3.0 // 10.3.3.0 (May 12.2008 / SVN 652961)
10.4.1.3 // 10.4.1.3 (April 24.2008 / SVN 648739)
10.4.2.0 // 10.4.2.0 (September 05, 2008 / SVN 693552)
10.4.2.1 // (Special test version / SVN 706043)

b)  -DderbyTesting.oldReleasePath=/usr/local/share/java/derby/lib 
     Use jars at /usr/local/share/java/derby/lib and  test upgrade from the versions listed
as defaults (currently as listed in 'VERSIONS').

c) -DderbyTesting.oldVersionsPath=/usr/local/share/java/derby/lib/versions
    Use jars fetched from 'http://svn.apache.org/repos/asf/db/derby/jars' and test upgrade
from the versions listed in /usr/local/share/java/derby/lib/versions.
    Will warn that 10.2.2.1 and 10.4.2.1 are not available

d) None of -DderbyTesting.oldReleasePath and -DderbyTesting.oldReleasePath are given
    Use jars fetched from 'http://svn.apache.org/repos/asf/db/derby/jars' and  test upgrade
from the versions listed as defaults (currently as listed in 'VERSIONS').


> Add a facility to override the default set of old versions to be tested in the upgrade
tests.
> ---------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3982
>                 URL: https://issues.apache.org/jira/browse/DERBY-3982
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions: 10.5.0.0
>            Reporter: Ole Solberg
>            Assignee: Ole Solberg
>            Priority: Minor
>         Attachments: DERBY-3982_diff.txt, DERBY-3982_stat.txt
>
>
> In my testing I have seen a need for performing upgrade testing from local/internal non-public
"versions" of Derby.
> That is, having local/internal changes to some older branch and allowing upgrade testing
from this (not yet public) version.
> One solution is to locally modify the 'VERSIONS' table of the upgradetests '_Suite',
but this means modifying the source for each such case.
> A more flexible solution is to override the default versions (given in 'VERSIONS') by
using a property giving a file which lists the versions to test upgrade from. The location
to local version jars can currently be given by the 'derbyTesting.oldReleasePath' property.
The list of versions could be given by a property 'derbyTesting.oldVersionsPath'.
> This will also easily allow us to skip testing upgrade from a specific version. (This
can already be done by not having the version jars available.)
> The list of versions given via the property should be used whether versions (jars) are
available locally (as given by the 'derbyTesting.oldReleasePath' property or fetched from
the Apache Derby svn repository ('http://svn.apache.org/repos/asf/db/derby/jars').
> I have a patch for this which I will submit for review.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message