Mailing-List: contact issues-help@spark.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 17 Sep 2015 21:38:04 +0000 (UTC)
From: "Nicholas Chammas (JIRA)" <jira@apache.org>
To: issues@spark.apache.org
Message-ID: <JIRA.12728900.1406047892000.5672.1442525884105@Atlassian.JIRA>
In-Reply-To: <JIRA.12728900.1406047892000@Atlassian.JIRA>
References: <JIRA.12728900.1406047892000@Atlassian.JIRA>
 <JIRA.12728900.1406047892682@arcas>
Subject: [jira] [Commented] (SPARK-2622) Add Jenkins build numbers to
 SparkQA messages
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/SPARK-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14804559#comment-14804559 ] 

Nicholas Chammas commented on SPARK-2622:
-----------------------------------------

No worries. Thanks for quickly finding and resolving the issue. I appreciate it!

> Add Jenkins build numbers to SparkQA messages
> ---------------------------------------------
>
>                 Key: SPARK-2622
>                 URL: https://issues.apache.org/jira/browse/SPARK-2622
>             Project: Spark
>          Issue Type: Improvement
>          Components: Build
>    Affects Versions: 1.0.1
>            Reporter: Xiangrui Meng
>            Priority: Minor
>
> It takes Jenkins 2 hours to finish testing. It is possible to have the following:
> {code}
> Build 1 started.
> PR updated.
> Build 2 started.
> Build 1 finished successfully.
> A committer merged the PR because the last build seemed to be okay.
> Build 2 failed.
> {code}
> It would be nice to put the build number in the SparkQA message so it is easy to match the result with the build.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org