Anyone understand why we can't seem to publish to apache maven anymore?

-Todd

On Thu, Mar 3, 2011 at 1:35 PM, Apache Hudson Server
<[EMAIL PROTECTED]> wrote:
> See https://hudson.apache.org/hudson/job/Hadoop-Mapreduce-trunk-Commit/621/
>
> ###################################################################################
> ########################## LAST 60 LINES OF THE CONSOLE ###########################
> [...truncated 4464 lines...]
>    [javac] Compiling 11 source files to /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/build-fi/system/test/classes
>    [javac] Note: Some input files use or override a deprecated API.
>    [javac] Note: Recompile with -Xlint:deprecation for details.
>
> jar-test-system:
>
> -do-jar-test:
>      [jar] Building jar: /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/build-fi/system/hadoop-mapred-instrumented-test-0.23.0-SNAPSHOT.jar
>      [jar] Building jar: /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/build-fi/system/hadoop-mapred-instrumented-test-0.23.0-SNAPSHOT-sources.jar
>
> set-version:
>     [copy] Copying 1 file to /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/ivy
>     [copy] Copying 1 file to /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/ivy
>     [copy] Copying 1 file to /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/ivy
>     [copy] Copying 1 file to /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/ivy
>
> clean-sign:
>
> sign:
>
> signanddeploy:
>
> simpledeploy:
> [artifact:install-provider] Installing provider: org.apache.maven.wagon:wagon-http:jar:1.0-beta-2:runtime
> [artifact:deploy] Deploying to https://repository.apache.org/content/repositories/snapshots
> [artifact:deploy] [INFO] Retrieving previous build number from apache.snapshots.https
> [artifact:deploy] Uploading: org/apache/hadoop/hadoop-mapred/0.23.0-SNAPSHOT/hadoop-mapred-0.23.0-20110303.213523-60.jar to apache.snapshots.https
> [artifact:deploy] Uploaded 1741K
> [artifact:deploy] An error has occurred while processing the Maven artifact tasks.
> [artifact:deploy]  Diagnosis:
> [artifact:deploy]
> [artifact:deploy] Error deploying artifact 'org.apache.hadoop:hadoop-mapred:jar': Error deploying artifact: Failed to transfer file: https://repository.apache.org/content/repositories/snapshots/org/apache/hadoop/hadoop-mapred/0.23.0-SNAPSHOT/hadoop-mapred-0.23.0-20110303.213523-60.jar. Return code is: 401
>
> BUILD FAILED
> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/build.xml:1528: Error deploying artifact 'org.apache.hadoop:hadoop-mapred:jar': Error deploying artifact: Failed to transfer file: https://repository.apache.org/content/repositories/snapshots/org/apache/hadoop/hadoop-mapred/0.23.0-SNAPSHOT/hadoop-mapred-0.23.0-20110303.213523-60.jar. Return code is: 401
>
> Total time: 3 minutes 20 seconds
>
>
> =====================================================================> =====================================================================> STORE: saving artifacts
> =====================================================================> =====================================================================>
>
> mv: cannot stat `build/*.tar.gz': No such file or directory
> mv: cannot stat `build/test/findbugs': No such file or directory
> mv: cannot stat `build/docs/api': No such file or directory
> Build Failed
> [FINDBUGS] Skipping publisher since build result is FAILURE
> Recording fingerprints
> Archiving artifacts
> Recording test results
> Publishing Javadoc
> Publishing Clover coverage report...
> No Clover report will be published due to a Build Failure
> Email was triggered for: Failure
> Sending email for trigger: Failure
>
>
>
> ###################################################################################
> ############################## FAILED TESTS (if any) ##############################

Todd Lipcon
Software Engineer, Cloudera

That seems like settings.xml has been modified, but then it'd affect
other builds as well. Unless we are using different machines/users for
different component's builds.

On Thu, Mar 3, 2011 at 13:41, Todd Lipcon <[EMAIL PROTECTED]> wrote:
> Anyone understand why we can't seem to publish to apache maven anymore?
>
> -Todd
>
> On Thu, Mar 3, 2011 at 1:35 PM, Apache Hudson Server
> <[EMAIL PROTECTED]> wrote:
>> See https://hudson.apache.org/hudson/job/Hadoop-Mapreduce-trunk-Commit/621/
>>
>> ###################################################################################
>> ########################## LAST 60 LINES OF THE CONSOLE ###########################
>> [...truncated 4464 lines...]
>>    [javac] Compiling 11 source files to /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/build-fi/system/test/classes
>>    [javac] Note: Some input files use or override a deprecated API.
>>    [javac] Note: Recompile with -Xlint:deprecation for details.
>>
>> jar-test-system:
>>
>> -do-jar-test:
>>      [jar] Building jar: /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/build-fi/system/hadoop-mapred-instrumented-test-0.23.0-SNAPSHOT.jar
>>      [jar] Building jar: /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/build-fi/system/hadoop-mapred-instrumented-test-0.23.0-SNAPSHOT-sources.jar
>>
>> set-version:
>>     [copy] Copying 1 file to /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/ivy
>>     [copy] Copying 1 file to /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/ivy
>>     [copy] Copying 1 file to /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/ivy
>>     [copy] Copying 1 file to /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/ivy
>>
>> clean-sign:
>>
>> sign:
>>
>> signanddeploy:
>>
>> simpledeploy:
>> [artifact:install-provider] Installing provider: org.apache.maven.wagon:wagon-http:jar:1.0-beta-2:runtime
>> [artifact:deploy] Deploying to https://repository.apache.org/content/repositories/snapshots
>> [artifact:deploy] [INFO] Retrieving previous build number from apache.snapshots.https
>> [artifact:deploy] Uploading: org/apache/hadoop/hadoop-mapred/0.23.0-SNAPSHOT/hadoop-mapred-0.23.0-20110303.213523-60.jar to apache.snapshots.https
>> [artifact:deploy] Uploaded 1741K
>> [artifact:deploy] An error has occurred while processing the Maven artifact tasks.
>> [artifact:deploy]  Diagnosis:
>> [artifact:deploy]
>> [artifact:deploy] Error deploying artifact 'org.apache.hadoop:hadoop-mapred:jar': Error deploying artifact: Failed to transfer file: https://repository.apache.org/content/repositories/snapshots/org/apache/hadoop/hadoop-mapred/0.23.0-SNAPSHOT/hadoop-mapred-0.23.0-20110303.213523-60.jar. Return code is: 401
>>
>> BUILD FAILED
>> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/build.xml:1528: Error deploying artifact 'org.apache.hadoop:hadoop-mapred:jar': Error deploying artifact: Failed to transfer file: https://repository.apache.org/content/repositories/snapshots/org/apache/hadoop/hadoop-mapred/0.23.0-SNAPSHOT/hadoop-mapred-0.23.0-20110303.213523-60.jar. Return code is: 401
>>
>> Total time: 3 minutes 20 seconds
>>
>>
>> =====================================================================>> =====================================================================>> STORE: saving artifacts
>> =====================================================================>> =====================================================================>>
>>
>> mv: cannot stat `build/*.tar.gz': No such file or directory
>> mv: cannot stat `build/test/findbugs': No such file or directory
>> mv: cannot stat `build/docs/api': No such file or directory
>> Build Failed
>> [FINDBUGS] Skipping publisher since build result is FAILURE
>> Recording fingerprints
>> Archiving artifacts
>> Recording test results
>> Publishing Javadoc
>> Publishing Clover coverage report...

On Mon, Mar 7, 2011 at 5:06 PM, Greg Roelofs <[EMAIL PROTECTED]> wrote:
> [general@ moved to Bcc; this seems like a pure dev issue now.]
Good call.

>
> If the hypothetical "rm -rf" can be found, perhaps simply changing it to
> nuke only ~/.m2/repository would suffice?  Or does settings.xml live below
> that?

Yea... anyone have any ideas which build might be rming it?

>
> Restoring it as one of the first steps of a Hudson build is probably the
> best approach, though (especially if it's restored from svn or somewhere
> with change-history).

The issue with putting it somewhere with change history is that it
needs to be private, since it contains a password. So, if we move it
to a private part of the SVN, then we have a bootstrapping problem of
where to keep the authentication for SVN :)

For now, how about we put it in
/homes/hudson/hadoop-ci-maven-settings.xml or something, not
versioned, and then add a bit to the nightly build script that cps it
into place?

-Todd
--
Todd Lipcon
Software Engineer, Cloudera

I have temporarily disabled TestBlockPlacementPolicyRaid.
Please see https://issues.apache.org/jira/browse/MAPREDUCE-2711

Regards,
Tsz-Wo
________________________________
From: Apache Jenkins Server <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Sent: Tuesday, July 19, 2011 9:08 AM
Subject: Hadoop-Mapreduce-trunk-Commit - Build # 750 - Failure

See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/750/

###################################################################################
########################## LAST 60 LINES OF THE CONSOLE ###########################
[...truncated 8868 lines...]
    [javac] /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/src/contrib/raid/src/test/org/apache/hadoop/hdfs/server/blockmanagement/TestBlockPlacementPolicyRaid.java:85: blockManager is not public in org.apache.hadoop.hdfs.server.namenode.FSNamesystem; cannot be accessed from outside package
    [javac]     policy = (BlockPlacementPolicyRaid) namesystem.blockManager.replicator;
    [javac]                                                   ^
    [javac] /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/src/contrib/raid/src/test/org/apache/hadoop/hdfs/server/blockmanagement/TestBlockPlacementPolicyRaid.java:272: cannot find symbol
    [javac] symbol  : variable clusterMap
    [javac] location: class org.apache.hadoop.hdfs.server.namenode.FSNamesystem
    [javac]           conf, namesystem, namesystem.clusterMap));
    [javac]                                       ^
    [javac] /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/src/contrib/raid/src/test/org/apache/hadoop/hdfs/server/blockmanagement/TestBlockPlacementPolicyRaid.java:317: blockManager is not public in org.apache.hadoop.hdfs.server.namenode.FSNamesystem; cannot be accessed from outside package
    [javac]       namesystem.blockManager.replicator = policy;
    [javac]                 ^
    [javac] /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/src/contrib/raid/src/test/org/apache/hadoop/hdfs/server/blockmanagement/TestBlockPlacementPolicyRaid.java:317: cannot assign a value to final variable replicator
    [javac]       namesystem.blockManager.replicator = policy;
    [javac]                              ^
    [javac] /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/src/contrib/raid/src/test/org/apache/hadoop/hdfs/server/blockmanagement/TestBlockPlacementPolicyRaid.java:337: cannot find symbol
    [javac] symbol  : variable clusterMap
    [javac] location: class org.apache.hadoop.hdfs.server.namenode.FSNamesystem
    [javac]           conf, namesystem, namesystem.clusterMap));
    [javac]                                       ^
    [javac] /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/src/contrib/raid/src/test/org/apache/hadoop/hdfs/server/blockmanagement/TestBlockPlacementPolicyRaid.java:454: cannot find symbol
    [javac] symbol  : variable clusterMap
    [javac] location: class org.apache.hadoop.hdfs.server.namenode.FSNamesystem
    [javac]       policy.initialize(conf, namesystem, namesystem.clusterMap);
    [javac]                                                     ^
    [javac] /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/src/contrib/raid/src/test/org/apache/hadoop/hdfs/server/blockmanagement/TestBlockPlacementPolicyRaid.java:501: blockManager is not public in org.apache.hadoop.hdfs.server.namenode.FSNamesystem; cannot be accessed from outside package
    [javac]     INodeFile inode = namesystem.blockManager.blocksMap.getINode(block
    [javac]                                 ^
    [javac] Note: Some input files use or override a deprecated API.
    [javac] Note: Recompile with -Xlint:deprecation for details.
    [javac] 8 errors

BUILD FAILED
/grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/build.xml:1189: The following error occurred while executing this line:
/grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/src/contrib/build.xml:39: The following error occurred while executing this line:
/grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/src/contrib/build-contrib.xml:227: Compile failed; see the compiler error output for details.

Total time: 5 minutes 38 seconds
==========================================================================================================================================STORE: saving artifacts
==========================================================================================================================================

mv: cannot stat `build/*.tar.gz': No such file or directory
mv: cannot stat `build/test/findbugs': No such file or directory
Build Failed
[FINDBUGS] Skipping publisher since build result is FAILURE
Archiving artifacts
Publishing Clover coverage report...
No Clover report will be published due to a Build Failure
Recording test results
Publishing Javadoc
Recording fingerprints
Updating MAPREDUCE-2711
Email was triggered for: Failure
Sending email for trigger: Failure

###################################################################################
############################## FAILED TESTS (if any) ##############################
No tests ran.