From derby-dev-return-119260-archive-asf-public=cust-asf.ponee.io@db.apache.org Thu Oct 4 03:13:04 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id E9F5218065B for ; Thu, 4 Oct 2018 03:13:03 +0200 (CEST) Received: (qmail 29826 invoked by uid 500); 4 Oct 2018 01:13:03 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 29816 invoked by uid 99); 4 Oct 2018 01:13:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Oct 2018 01:13:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 792311A1693 for ; Thu, 4 Oct 2018 01:13:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id zovNfcXt9VKw for ; Thu, 4 Oct 2018 01:13:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 1F1F65F523 for ; Thu, 4 Oct 2018 01:13:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 64759E006D for ; Thu, 4 Oct 2018 01:13:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 090CB25546 for ; Thu, 4 Oct 2018 01:13:00 +0000 (UTC) Date: Thu, 4 Oct 2018 01:13:00 +0000 (UTC) From: "Rick Hillegas (JIRA)" To: derby-dev@db.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (DERBY-7011) Set up a new Jenkins job to run the JUnit tests with a module path MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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 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 > 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)