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

Hadoop QA commented on HADOOP-12520:
------------------------------------

| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 7s 
{color} | {color:blue} docker + precommit patch detected. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s 
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m 
0s {color} | {color:green} The patch appears to include 1 new or modified test 
files. {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 0s 
{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 0s 
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m 
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m 1s 
{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m 
20s {color} | {color:green} Patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 0m 34s {color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.7.1 Server=1.7.1 
Image:test-patch-base-hadoop-date2015-10-28 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12769129/HADOOP-12520.001.patch
 |
| JIRA Issue | HADOOP-12520 |
| Optional Tests |  asflicense  site  mvnsite  unit  xml  |
| uname | Linux cd10933ea417 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT Wed 
Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/home/jenkins/jenkins-slave/workspace/PreCommit-HADOOP-Build/patchprocess/apache-yetus-2392ab4/dev-support/personality/hadoop.sh
 |
| git revision | trunk / 68ce93c |
| Default Java | 1.7.0_79 |
| Multi-JDK versions |  /usr/lib/jvm/java-8-oracle:1.8.0_60 
/usr/lib/jvm/java-7-openjdk-amd64:1.7.0_79 |
| JDK v1.7.0_79  Test Results | 
https://builds.apache.org/job/PreCommit-HADOOP-Build/7959/testReport/ |
| modules | C: . hadoop-tools/hadoop-azure U: . |
| Max memory used | 33MB |
| Powered by | Apache Yetus   http://yetus.apache.org |
| Console output | 
https://builds.apache.org/job/PreCommit-HADOOP-Build/7959/console |


This message was automatically generated.



> Use XInclude in hadoop-azure test configuration to isolate Azure Storage 
> account keys for service integration tests.
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-12520
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12520
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: azure, test
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>         Attachments: HADOOP-12520.001.patch
>
>
> The hadoop-azure tests support execution against the live Azure Storage 
> service if the developer specifies the key to an Azure Storage account.  The 
> configuration works by overwriting the src/test/resources/azure-test.xml 
> file.  This can be an error-prone process.  The azure-test.xml file is 
> checked into revision control to show an example.  There is a risk that the 
> tester could overwrite azure-test.xml containing the keys and then 
> accidentally commit the keys to revision control.  This would leak the keys 
> to the world for potential use by an attacker.  This issue proposes to use 
> XInclude to isolate the keys into a separate file, ignored by git, which will 
> never be committed to revision control.  This is very similar to the setup 
> already used by hadoop-aws for integration testing.



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

Reply via email to