[ 
https://issues.apache.org/jira/browse/OOZIE-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16077515#comment-16077515
 ] 

Hadoop QA commented on OOZIE-2877:
----------------------------------

Testing JIRA OOZIE-2877

Cleaning local git workspace

----------------------------

{color:green} 1 PATCH_APPLIES{color}
{color:green} 1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.    {color:green} 1{color} the patch does not introduce any @author tags
.    {color:red}-1{color} the patch contains 1 line(s) with tabs
.    {color:green} 1{color} the patch does not introduce any trailing spaces
.    {color:red}-1{color} the patch contains 5 line(s) longer than 132 
characters
.    {color:green} 1{color} the patch does adds/modifies 3 testcase(s)
{color:green} 1 RAT{color}
.    {color:green} 1{color} the patch does not seem to introduce new RAT 
warnings
{color:green} 1 JAVADOC{color}
.    {color:green} 1{color} the patch does not seem to introduce new Javadoc 
warnings
.    {color:red}WARNING{color}: the current HEAD has 1 Javadoc warning(s)
{color:green} 1 COMPILE{color}
.    {color:green} 1{color} HEAD compiles
.    {color:green} 1{color} patch compiles
.    {color:green} 1{color} the patch does not seem to introduce new javac 
warnings
{color:green} 1{color} There are no new bugs found in total.
{color:green} 1 BACKWARDS_COMPATIBILITY{color}
.    {color:green} 1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.    {color:green} 1{color} the patch does not modify JPA files
{color:green} 1 TESTS{color}
.    Tests run: 1967
.    Tests rerun: 79
.    Tests failed at first run: 
org.apache.oozie.action.hadoop.TestJavaActionExecutor,org.apache.oozie.jms.TestJMSJobEventListener,org.apache.oozie.action.hadoop.TestLauncherAM,
{color:green} 1 DISTRO{color}
.    {color:green} 1{color} distro tarball builds with the patch 

----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}

{color:red}. There is at least one warning, please check{color}

The full output of the test-patch run is available at

. https://builds.apache.org/job/oozie-trunk-precommit-build/3958/

> 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, 
> 0002-OOZIE-2877-Oozie-Git-Action.patch, 
> 0003-OOZIE-2877-Oozie-Git-Action.patch, 0004-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.4.14#64029)

Reply via email to