db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3045) Write a tool to do a binary search of past trunk builds to find the source of regressions
Date Wed, 05 Sep 2007 02:38:44 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524952
] 

Kathey Marsden commented on DERBY-3045:
---------------------------------------

The location I mention only has jars since the last branch, so by trunk jars from previous
releases I guess I just meant old trunk jars, but I agree it makes more sense for the tool
to svn update and build so we can zero in on the exact change causing the issue and remove
the external dependency.

Kathey


> Write a tool to do a binary search of past trunk builds to find the source of regressions

> ------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3045
>                 URL: https://issues.apache.org/jira/browse/DERBY-3045
>             Project: Derby
>          Issue Type: Task
>          Components: Build tools
>    Affects Versions: 10.4.0.0
>            Reporter: Kathey Marsden
>
> Often we have to backtrack to find the source of a regression.   It would be useful to
have a tool which would run a java program against archived builds and do a binary search
for the build that caused the failure.  Trunk builds for the current release are stored at
http://dbtg.thresher.com/derby/bits/trunk/ but in order for the tool to be most useful we
would need to start keeping the trunk jars from previous releases.

-- 
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