You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Richard N. Hillegas (Jira)" <ji...@apache.org> on 2020/02/23 18:17:00 UTC
[jira] [Updated] (DERBY-7067) Investigate why jenkins tests on old
release branches were re-animated
[ https://issues.apache.org/jira/browse/DERBY-7067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard N. Hillegas updated DERBY-7067:
---------------------------------------
Description: This happened when I checked in the jars for 10.15.2.0 as starting points of upgrade trajectories. The tests failed because they could not find a JUnit class. I don't know why other old builds did not re-animate. (was: This happened when I checked in the jars for 10.15.2.0 as starting points of upgrade trajectories. The builds failed because they could not find a JUnit class. I don't know why other old builds did not re-animate.)
> Investigate why jenkins tests on old release branches were re-animated
> ----------------------------------------------------------------------
>
> Key: DERBY-7067
> URL: https://issues.apache.org/jira/browse/DERBY-7067
> Project: Derby
> Issue Type: Task
> Components: Build tools
> Affects Versions: 10.12.1.1, 10.13.1.1
> Reporter: Richard N. Hillegas
> Priority: Major
>
> This happened when I checked in the jars for 10.15.2.0 as starting points of upgrade trajectories. The tests failed because they could not find a JUnit class. I don't know why other old builds did not re-animate.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)