[
https://issues.apache.org/jira/browse/SPARK-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14804499#comment-14804499
]
Maximilian Michels commented on SPARK-2622:
-------------------------------------------
Hi [~nchammas]], I'm really sorry for bothering. I was trying out the Spark
Pull Request Dashboard with all the settings (settings.cfg) adapted to the
Flink JIRA and Flink Github repository. Only when it was too late, I saw that
there were some hard-coded URLs in the the source code that also needed to be
adapted. This caused some unexpected behavior (Flink issue number in Flink pull
requests being associated with Spark issues numbers). I've removed all comments
and links and apologize very much for the inconvenience this caused. I've
definitely learned a lesson out of this one.
> 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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
