From dev-return-99774-apmail-lucene-dev-archive=lucene.apache.org@lucene.apache.org Tue Jun 5 17:58:24 2012 Return-Path: X-Original-To: apmail-lucene-dev-archive@www.apache.org Delivered-To: apmail-lucene-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BFB0098D7 for ; Tue, 5 Jun 2012 17:58:24 +0000 (UTC) Received: (qmail 41259 invoked by uid 500); 5 Jun 2012 17:58:23 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 41217 invoked by uid 500); 5 Jun 2012 17:58:23 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 41208 invoked by uid 99); 5 Jun 2012 17:58:23 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Jun 2012 17:58:23 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 2C5D914285F for ; Tue, 5 Jun 2012 17:58:23 +0000 (UTC) Date: Tue, 5 Jun 2012 17:58:23 +0000 (UTC) From: "Steven Rowe (JIRA)" To: dev@lucene.apache.org Message-ID: <516039560.40462.1338919103183.JavaMail.jiratomcat@issues-vm> In-Reply-To: <765635375.17927.1338407543195.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (LUCENE-4092) Check what's Jenkins pattern for e-mailing log fragments (so that it includes failures). 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/LUCENE-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13289581#comment-13289581 ] Steven Rowe commented on LUCENE-4092: ------------------------------------- {quote} BuildLogRegexContent, the content parser for BUILD_LOG_REGEX, matches line-by-line, so regexes targeting multiple lines will fail. [...] I'll try to add an argument to BUILD_LOG_REGEX to enable multi-line content matching, and make a pull request/JIRA issue to get it included in the next release of the plugin. {quote} I made a new content token named BUILD_LOG_MULTILINE_REGEX in my fork of the email-ext-plugin - see [JENKINS-1400|https://issues.jenkins-ci.org/browse/JENKINS-14000]. My pull request ([#40|https://github.com/jenkinsci/email-ext-plugin/pull/40]) was merged into the upstream project a few days ago, so the next release will include this change. (Looks like this plugin releases once a month or so, so the wait before we can use it shouldn't be too long, assuming the plugins on the ASF Jenkins instance are kept up-to-date.) > Check what's Jenkins pattern for e-mailing log fragments (so that it includes failures). > ---------------------------------------------------------------------------------------- > > Key: LUCENE-4092 > URL: https://issues.apache.org/jira/browse/LUCENE-4092 > Project: Lucene - Java > Issue Type: Sub-task > Components: general/test > Reporter: Dawid Weiss > Priority: Trivial > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For additional commands, e-mail: dev-help@lucene.apache.org