[
https://issues.apache.org/jira/browse/DERBY-7011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16637669#comment-16637669
]
Rick Hillegas commented on DERBY-7011:
--------------------------------------
Here is an email which I sent to derby-dev after the initial setup:
------------------------------
> I am trying to set up a new Jenkins task which will run the JUnit All
> suite with a module path when a checkin is submitted. This is my first
> attempt to create a Jenkins task from scratch (I used the
> Derby-trunk-suites.All task as a template). Please pardon the noise
> while I figure this out.
>
> I think I have figured out how to make Jenkins run the correct ant
> target. But I'm unclear on whether I have correctly configured the
> post-build action so that it will generate email when the target fails.
> I would appreciate advice from any Jenkins experts who have time to
> eyeball the new task:
> https://builds.apache.org/job/Derby-trunk-test-junit-all-with-modulepath/
>
> Unfortunately, I only have the console log to use as evidence of
> failures. The fancy JUnit xml-style reports are not available. That is
> because the <junit> ant task is not module-aware. That, in turn, is
> because our JUnit version is not module-aware. Therefore the
> test-junit-all-with-modulepath target has to run JUnit by hand via a
> <java> task.
>
> Thanks,
>
> -Rick
>
> 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
>
> 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)
