[
https://issues.apache.org/jira/browse/DERBY-7011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16705078#comment-16705078
]
Rick Hillegas commented on DERBY-7011:
--------------------------------------
Attaching derby-7011-01-aa-shortCircuitAfterDerbyNetSuite.diff. This patch
tries to short-circuit the JUnit tests when running with a modulepath under
Jenkins.
The derbynet suite raised errors during the latest Jenkins test run with a
modulepath. This patch should short-circuit the Jenkins modulepath runs after
that suite. Hopefully, that will allow us to get more information on the errors.
I will run tests using the classpath and modulepath.
Touches the following files:
{noformat}
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/suites/AllPackages.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/junit/BaseTestCase.java
{noformat}
> Set up a new Jenkins job to run the JUnit tests with a module path
> ------------------------------------------------------------------
>
> Key: DERBY-7011
> URL: https://issues.apache.org/jira/browse/DERBY-7011
> Project: Derby
> Issue Type: Task
> Components: Build tools
> Affects Versions: 10.15.0.0
> Reporter: Rick Hillegas
> Priority: Major
> Attachments: derby-7011-01-aa-shortCircuitAfterDerbyNetSuite.diff
>
>
> I have set up a new Jenkins job (Derby-trunk-test-junit-all-with-modulepath)
> to run the JUnit tests with a module path. This issue is a place to collect
> feedback on how to finish setting up this job.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
