Hi Niklaus,

I had the same problem months ago. You cannot use the environment variables 
-Dusername and -Dpassword any longer while releasing a plugin.

Edit your Maven settings.xml and add a new server section to it:
<server>
    <id>maven.jenkins-ci.org</id>
     <username>niklaus_giger</username>
     <password>cleartext_pw</password>
 </server>

See https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins (section 
Releasing to jenkins-ci.org) for more details on how to modify your 
settings.xml.

Kind regards
Björn

Am 11.05.2014 um 17:14 schrieb Niklaus Giger <[email protected]>:

> Hi
> 
> I am trying to release my first jenkins plugin. I successfully pushed all my 
> changes to https://github.com/jenkinsci/git-parameter-plugin
> 
> Calling 
> mvn release:prepare release:perform -Dusername=niklaus_giger 
> -Dpassword=cleartext_pw
> always resulted in 
> [INFO] Scanning for projects...
> [INFO]                                                                        
>  
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Building Git Parameter Plug-In 0.3
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] 
> [INFO] --- maven-release-plugin:2.2.2:prepare (default-cli) @ git-parameter 
> ---
> [INFO] Resuming release from phase 'scm-tag'
> [INFO] Tagging release with the label git-parameter-0.3...
> [INFO] Executing: /bin/sh -c cd /opt/src/git-parameter.jenkins.ci && git tag 
> -F /tmp/maven-scm-790953102.commit git-parameter-0.3
> [INFO] Working directory: /opt/src/git-parameter.jenkins.ci
> [INFO] Executing: /bin/sh -c cd /opt/src/git-parameter.jenkins.ci && git push 
> ssh://niklaus_giger:[email protected]:jenkinsci/git-parameter-plugin.git
>  git-parameter-0.3
> [INFO] Working directory: /opt/src/git-parameter.jenkins.ci
> [INFO]                                                                        
>  
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Skipping Git Parameter Plug-In
> [INFO] This project has been banned from the build due to previous failures.
> [INFO] 
> ------------------------------------------------------------------------
> 
> Can anybody tell me why this plugin is banned or whether I must (and then 
> how) resolve the push problem.
> 
> Best regards in advance.
> 
> Niklaus Giger
> 
> P.S. The pom.xml already defines 0.3 (instead of 0.3-SNAPSHOT) as version, as 
> I corrected a few things in the pom.xml.
> 
> 
> -- 
> 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 [email protected].
> For more options, visit https://groups.google.com/d/optout.

-- 
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to