[ https://issues.apache.org/jira/browse/SPARK-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14086513#comment-14086513 ]
Xiangrui Meng commented on SPARK-2622: -------------------------------------- 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. > 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.2#6252) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org