[
https://issues.apache.org/jira/browse/HADOOP-12129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14698122#comment-14698122
]
Sean Busbey commented on HADOOP-12129:
--------------------------------------
{noformat}
-## @returns ${JIRACLI} exit code
+## @returns ${CURL} exit code
{noformat}
so long as we're changing, replace with "exit code from posting to jira" so
that we don't leak how we talk to jira?
{noformat}
+ for bug in ${BUGSYSTEMS}; do
+ if declare -f ${bug}_write_comment >/dev/null; then
+ "${bug}_write_comment" "${commentfile}"
+ fi
+ done
{noformat}
How will this play out for ASF projects that have github integration in place?
I think we'll write to github and jira, and then github will write to jira. can
we add a flag that picks one and defaults to "all"?
> rework test-patch bug system support
> ------------------------------------
>
> Key: HADOOP-12129
> URL: https://issues.apache.org/jira/browse/HADOOP-12129
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: yetus
> Affects Versions: HADOOP-12111
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Priority: Blocker
> Attachments: HADOOP-12129.HADOOP-12111.00.patch,
> HADOOP-12129.HADOOP-12111.01.patch, HADOOP-12129.HADOOP-12111.02.patch,
> HADOOP-12129.HADOOP-12111.03.patch, HADOOP-12129.HADOOP-12111.04.patch
>
>
> WARNING: this is a fairly big project.
> See first comment for a brain dump on the issues.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
