flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maximilian Michels (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (FLINK-2699) Flink is filling Spark JIRA with incorrect PR links
Date Thu, 17 Sep 2015 20:58:04 GMT

     [ https://issues.apache.org/jira/browse/FLINK-2699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Maximilian Michels closed FLINK-2699.
    Resolution: Fixed

Hi [~pwendell], 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.

> Flink is filling Spark JIRA with incorrect PR links
> ---------------------------------------------------
>                 Key: FLINK-2699
>                 URL: https://issues.apache.org/jira/browse/FLINK-2699
>             Project: Flink
>          Issue Type: Bug
>            Reporter: Patrick Wendell
>            Priority: Blocker
> I think you guys are using our script for synchronizing JIRA. However, you didn't adjust
the target JIRA identifier so it is still posting to Spark. In the past few hours we've seen
a lot of random Flink pull requests being linked on the Spark JIRA. This is obviously not
desirable for us since they are different projects.
> The JIRA links are being created by the user "Maximilian Michels" ([~mxm]).
> https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mxm
> I saw these as recently as 5 hours ago. There are around 23 links that were created -
if you could go ahead and remove them that would be useful. Thanks!

This message was sent by Atlassian JIRA

View raw message