You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Josh Rosen (JIRA)" <ji...@apache.org> on 2016/01/05 20:43:40 UTC

[jira] [Resolved] (SPARK-1070) Add check for JIRA ticket in the Github pull request title/summary with CI

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

Josh Rosen resolved SPARK-1070.
-------------------------------
    Resolution: Won't Fix

Resolving as "Won't Fix." Most contributors now submit PRs with JIRAs, so the cost of infrequently reminding new folks to file them isn't high enough to justify automation here.

> Add check for JIRA ticket in the Github pull request title/summary with CI
> --------------------------------------------------------------------------
>
>                 Key: SPARK-1070
>                 URL: https://issues.apache.org/jira/browse/SPARK-1070
>             Project: Spark
>          Issue Type: Task
>          Components: Build
>            Reporter: Henry Saputra
>            Assignee: Mark Hamstra
>            Priority: Minor
>
> As part of discussion in the dev@ list to add audit trail of Spark's Github pull requests (PR) to JIRA, need to add check maybe in the Jenkins CI to verify that the PRs contain JIRA ticket number in the title/ summary.
>  
> There are maybe some PRs that may not need ticket so probably add support for some "magic" keyword to bypass the check. But this should be done in rare cases.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org