[
https://issues.apache.org/jira/browse/OOZIE-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16028680#comment-16028680
]
Clay B. commented on OOZIE-2877:
--------------------------------
Thanks [~andras.piros]! I've never used the Apache Review Board but I have
tried setting up a review at https://reviews.apache.org/r/59620/; please let me
know if I need to do anything to make this more useful.
I've gotten `RAT` happy I am re-submiting for Jenkins to run to see what
findbugs thinks and the `RAW_PATCH_ANALYSIS` issues.
Now the code should be a little cleaner and there is a documentation stub now.
I have added the option for cloning a branch but I can not quite get JGit to
[cooperate|https://dev.eclipse.org/mhonarc/lists/jgit-dev/msg03343.html]. Also
I have provided a few tests:
* {{TestIntegrationGitActionExecutor}} - Which is disabled by default as it
reaches out to Github.COM to download Oozie
* {{TestGitActionExecutor}} - This verifies the XML parsing for the Git action
* {{TestGitMain}} - This implements a unit test case for {{GitMain.gitKeys()}}
> Oozie Git Action
> ----------------
>
> Key: OOZIE-2877
> URL: https://issues.apache.org/jira/browse/OOZIE-2877
> Project: Oozie
> Issue Type: Sub-task
> Components: action
> Reporter: Clay B.
> Labels: action
> Fix For: trunk
>
> Attachments: 0001-OOZIE-2877-Oozie-Git-Action.patch
>
>
> To aide in deploying ASCII artifacts to clusters, let's provide a tie-in for
> a source-code management system. Git would be my preferred choice.
> Ideally, this could handle a user's key material e.g. for an ssh key to pull
> down from a secured repository. This would free users from handling their own
> key staging and clean-up on YARN nodes and only require them to store the key
> secured in HDFS.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
