I think the build number is included in the SparkQA message, for example: https://github.com/apache/spark/pull/1788
The build number 17941 is in the URL "https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/17941/consoleFull";. Just need to be careful to match the number. Another solution is to kill running Jenkins jobs if there is a code change. On Tue, Aug 5, 2014 at 8:48 AM, Nicholas Chammas <nicholas.cham...@gmail.com> wrote: >> >> 1. Include the commit hash in the "tests have started/completed" >> > > FYI: Looks like Xiangrui's already got a JIRA issue for this. > > SPARK-2622: Add Jenkins build numbers to SparkQA messages > <https://issues.apache.org/jira/browse/SPARK-2622> > > 2. "Pin" a message to the start or end of the PR > > > Should new JIRA issues for this item fall under the following umbrella > issue? > > SPARK-2230: Improvements to Jenkins QA Harness > <https://issues.apache.org/jira/browse/SPARK-2230> > > Nick --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org For additional commands, e-mail: dev-h...@spark.apache.org
