Here follows a settings.xml example to enable artifacts and site deployment on Cloudbees Maven private repositories
</settings> <servers> <server> <id>cloudbees-my-snapshots</id> <username>[account_id]</username> <password>{s0m3We1RdcHa5s=}</password> </server> <server> <id>cloudbees-my-releases</id> <username>[account_id]</username> <password>{s0m3We1RdcHa5s=}</password> </server> <server> <id>cloudbees-my-private</id> <username>[account_id]</username> <password>{s0m3We1RdcHa5s=}</password> </server> <!-- Next server conf is used to deploy this site on Sourcesense github; above server conf is the one provided by Cloudbees. --> <server> <id>github</id> <username>git</username> <password></password> </server> </servers> </settings>
It is strongly advised to encrypt your Maven passwords.
~/.m2/settings.xml and ~/.m2/security-settings.xml must be copied into the private Cloudbees WebDAV drive, in order to respect the build configurations
You can use any WebDAV client to access your private repo, but the content should look something like this.