Reputation: 3734
Note: since I'm the only one searching for it it feels like I want to use bad practice.
I want to create a deploy-user. Its only purpose is to be configured in the settings.xml as a server-entity:
<servers>
<server>
<id>nexus</id>
<username>deploy-user</username>
<password>somepassword</password>
</server>
</servers>
The user only needs permission to upload artifacts to all the repositories hosted on the Nexus 3.0 server. I've created a role "Deployment" and need to know which privileges need to be applied.
Upvotes: 17
Views: 20919
Reputation: 29
For nexus 3.x, create a new role (e.g. "deploy") and assign it the add, edit and read permissions (nx-repository-view-<repo_type>-<repo_name>-add/edit/read
).
This suffices for maven; other clients may need more privileges.
Upvotes: 1
Reputation: 2006
The User must have Artifact Upload
privilege, which can be searched in privileges
tab.
Role
for your user, add Artifact Upload
privilege to the Role.Below is an example of nexus 2.x
:
And this is for nexus 3.x
:
Upvotes: 8
Reputation: 7859
With Nexus 3.15.2-01
, I could successfully deploy a maven site with a user that had a role with the following Privileges:
nx-repository-view-<RepoType>-<RepoName>-add
andnx-repository-view-<RepoType>-<RepoName>-edit
e.g. nx-repository-view-raw-Cloudogu-Docs-add
.
See cloudogu/continuous-delivery-slides-example for an example.
A good exmplanation of nx-repository-view
vs nx-repository-admin
can be found in this answer.
Upvotes: 11
Reputation: 147
Recently edited on Aug-26...
Steps required for uploading to Nexus server.
Upvotes: -1