This is because the username has to be set in ~/.m2/settings.xml. I've added a comment to explain this.

On 04/15/2014 07:32 AM, Jesse Glick wrote:
Mainly for @Kohsuke.

I ran release:{prepare,perform} on this. I think the actual plugin
release was fine:

http://repo.jenkins-ci.org/public/org/jenkins-ci/tools/maven-hpi-plugin/1.107/

But the last step failed (Linux, mvn 3.1.0, JDK 7u51, Git 1.8.3.2):

[INFO] [INFO] --- maven-site-plugin:3.3:deploy (default-deploy) @
maven-hpi-plugin ---
[INFO] [INFO] Parent project loaded from repository:
org.jenkins-ci:jenkins:pom:1.32
[INFO] scm:git:ssh://github.com/jenkinsci/maven-hpi-plugin.git/ -
Session: Opened
[INFO] [INFO] Pushing
/space/src/jenkinsci/maven-hpi-plugin/target/checkout/target/site
[INFO] [INFO]    >>> to
scm:git:ssh://github.com/jenkinsci/maven-hpi-plugin.git/./
[INFO] Uploading: ./ to scm:git:ssh://github.com/jenkinsci/maven-hpi-plugin.git/
[INFO]
[INFO] [INFO] Executing: /bin/sh -c cd
/space/src/jenkinsci/maven-hpi-plugin/target/checkout/. && git
ls-files
[INFO] [INFO] Working directory:
/space/src/jenkinsci/maven-hpi-plugin/target/checkout/.
[INFO] [INFO] Executing: /bin/sh -c cd
/tmp/wagon-scm1270777913.checkout && git init
[INFO] [INFO] Working directory: /tmp/wagon-scm1270777913.checkout
[INFO] [INFO] Executing: /bin/sh -c cd
/tmp/wagon-scm1270777913.checkout && git remote add origin
ssh://github.com/jenkinsci/maven-hpi-plugin.git
[INFO] [INFO] Working directory: /tmp/wagon-scm1270777913.checkout
[INFO] [INFO] Executing: /bin/sh -c cd
/tmp/wagon-scm1270777913.checkout && git pull origin
refs/heads/gh-pages
[INFO] [INFO] Working directory: /tmp/wagon-scm1270777913.checkout
[INFO]  Transfer error: org.apache.maven.scm.ScmException: Unable to
commit file. The git-pull command failed. Permission denied
(publickey).
[INFO] fatal: Could not read from remote repository.
[INFO]
[INFO] Please make sure you have the correct access rights
[INFO] and the repository exists.
[INFO]
[INFO] scm:git:ssh://github.com/jenkinsci/maven-hpi-plugin.git/ -
Session: Disconnecting
[INFO] scm:git:ssh://github.com/jenkinsci/maven-hpi-plugin.git/ -
Session: Disconnected
[INFO] [INFO] 
------------------------------------------------------------------------
[INFO] [INFO] BUILD FAILURE
[INFO] [INFO] 
------------------------------------------------------------------------
[INFO] [INFO] Total time: 1:07.205s
[INFO] [INFO] Finished at: Tue Apr 15 10:20:22 EDT 2014
[INFO] [INFO] Final Memory: 46M/620M
[INFO] [INFO] 
------------------------------------------------------------------------
[INFO] [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.3:deploy (default-deploy)
on project maven-hpi-plugin: Error uploading site: Error checking out:
Unable to commit file. The git-pull command failed. Permission denied
(publickey).
[INFO] [ERROR] fatal: Could not read from remote repository.
[INFO] [ERROR]
[INFO] [ERROR] Please make sure you have the correct access rights
[INFO] [ERROR] and the repository exists.

It is odd that I would be getting a permission problem on the repo
when I can clearly push code changes to it.

I would suggest just getting rid of

   <distributionManagement>
     <site>
       <id>github.com</id>
       <url>gitsite:g...@github.com/jenkinsci/maven-hpi-plugin.git</url>
     </site>
   </distributionManagement>
         <plugin>
           <artifactId>maven-site-plugin</artifactId>
           <version>3.3</version>
           <dependencies>
             <dependency>
               <groupId>com.github.stephenc.wagon</groupId>
               <artifactId>wagon-gitsite</artifactId>
               <version>0.4.1</version>
             </dependency>
           </dependencies>
         </plugin>
     <extensions>
       <extension>
         <groupId>org.apache.maven.wagon</groupId>
         <artifactId>wagon-ssh</artifactId>
         <version>1.0-beta-7</version>
       </extension>
     </extensions>

on the grounds that site deployment is more trouble than it is worth.
If anyone really uses the Maven generated sites, it would be better to
have a CI job which runs mvn site and publishes the result somewhere
using stored credentials, so regular folks just trying to cut a
release are not stymied by it—making the Maven release plugin work
even in the simplest cases is enough trouble.



--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Jenkins Enterprise, our professional version of Jenkins

--
You received this message because you are subscribed to the Google Groups "Jenkins 
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to