On 28.05.2013 18:59, Knut Anders Hatlen wrote: > I ended up with this scheme for now (had to back-port DERBY-6078 to > 10.9 first): Derby-10.10-suites.All is set up to run with > derby.tests.basePort=1530, and Derby-10.9-suites.All with > derby.tests.basePort=1560. This way, they won't conflict with each > other or with the derbyall jobs when running on the same node. We > cannot configure the port used by derbyall, so I changed the poll > interval instead. Both Derby-10.9-derbyall and Derby-10.10-derbyall > used to check the Subversion repository for updates at midnight (in > some time zone). Now 10.9 is checked at midnight and 10.10 at midday. > That will hopefully bring them far enough apart so that they don't > overlap, even if they happen to run on the same node.
Brilliant! Thanks, Dag
