You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Patrick Wendell (JIRA)" <ji...@apache.org> on 2014/08/11 06:43:11 UTC
[jira] [Updated] (SPARK-2912) Jenkins should include the commit
hash in his messages
[ https://issues.apache.org/jira/browse/SPARK-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Wendell updated SPARK-2912:
-----------------------------------
Assignee: Nicholas Chammas
> Jenkins should include the commit hash in his messages
> ------------------------------------------------------
>
> Key: SPARK-2912
> URL: https://issues.apache.org/jira/browse/SPARK-2912
> Project: Spark
> Issue Type: Sub-task
> Components: Build
> Reporter: Nicholas Chammas
> Assignee: Nicholas Chammas
>
> When there are multiple test cycles within a PR, it is not obvious what cycle applies to what set of changes. This makes it more likely for committers to merge a PR that has had new commits added since the last PR.
> Requirements:
> * Add the commit hash to Jenkins's messages so it's clear what the test cycle corresponds to.
> * While you're at it, polish the formatting a bit.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org