mvn deploy vs mvn release:prepare release:perform

[Rajeev Ranjan]

Hi team,

I was trying to release "https://github.com/jenkinsci/uipath-automation-package-plugin" with "mvn release:prepare release:perform -Dusername=...  -Dpassword =... ", however I was facing facing permission denied because of credentials.

After that I followed the steps as per the doc to start an ssh-agent and import private key, and ran mvn deploy.

After that I can see the plugin in "https://repo.jenkins-ci.org/releases/". 

I am just curious, do I need to do mvn release againg or mvn deploy only. What's the difference between the two?

Also I was under the impression that, plugins will go to "https://repo.jenkins-ci.org/public/". What is this reo for?

Regards,

Rajeev Ranjan

[Jesse Glick]

On Tue, Apr 23, 2019 at 3:19 AM Rajeev Ranjan <rajeevr...@gmail.com> wrote:
> do I need to do mvn release againg or mvn deploy only. What's the difference between the two?

`release:perform` internally runs `deploy`, after `release:prepare`
has done a lot of preparation. A naked `mvn deploy` is generally only
good for uploading snapshots, not releases, except for advanced use
cases I will not discuss.


If you were getting permission denied errors releasing, then there may
have been something wrong in

https://github.com/jenkins-infra/repository-permissions-updater/pull/1103

such as a mistyped (LDAP) login ID, or maybe there was something wrong
with GitHub. You did not quote the actual error message so it is not
possible to help you much.