-
Notifications
You must be signed in to change notification settings - Fork 9
Grant JFrog Access
Burke Mamlin edited this page Aug 16, 2020
·
1 revision
By default, JFrog access should not be granted. https://talk.openmrs.org/t/urgent-maven-repo-credentials/19290/1
If a person wants to do a community release, it's better to grant Bamboo access. Our wiki has docs on how to configure a new Bamboo release and how to use the Bamboo release
If it's a team/organisation deploying community modules, it would be ideal to attempt to setup their CI to release.
For personal modules, users should follow https://wiki.openmrs.org/x/zIMmAQ and not deploy it to our jfrog.
If a user still requires a personal JFrog account (e.g. to do any maven artefact manipulation for community modules):
- User names should match OpenMRS IDs.
- Admins should have a dedicated admin account with "-admin" suffix and use a regular account for deployment purposes.
- There are 3 groups of regular users. First is Modules, who can deploy modules, the second is Snapshots, who can deploy snapshots, the third is Anything, who can deploy any type of artifacts. Most users will need to be assigned to Modules and Snapshots. Only some users, who do OpenMRS core and platform releases, will need to be assigned to Anything.
Read this before updating this wiki.