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 "Rick Hillegas (JIRA)" <ji...@apache.org> on 2018/11/30 17:55:00 UTC
[jira] [Updated] (DERBY-7011) Set up a new Jenkins job to run the
JUnit tests with a module path
[ https://issues.apache.org/jira/browse/DERBY-7011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-7011:
---------------------------------
Attachment: derby-7011-01-aa-shortCircuitAfterDerbyNetSuite.diff
> 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)