Shared Projects and Repositories
When a project of type PRIVATE is created on the DevOps Portal, it means that no user can access it without a role assignment. However, as a Project ADMIN, you can manually change the permissions on a single repository or on a complete project. This allows you to grant read-only access to all users which have a Bitbucket license assigned, i.e. all users that can log in to Bitbucket.
In the following example, the steps for changing a complete project are shown.
- Go to the Project settings of the Project in Bitbucket and open the sub-page SECURITY/Project Permissions.
Since the example project has the project key SBOM, you see a user for Jenkins called sbom-git as well as SDCloud Admin, which is used by the portal for managing the projects. All other users have been added by the Portal when somebody assigned a role for them to the project.
Press the button "Add user or group" on the top right. For the name, enter stash-users. Stash is the former name of Bitbucket, and the stash-users group contains all users having access to this Bitbucket. For permission, select Read. It's strictly recommended to not use higher permissions. Then press "Add".
The permission list now contains one more entry.
Now you are done. Please note that a Project Resync in the DevOps Portal will only remove individual users that you have added here, if they have no matching role in the portal. The group assignment is currently ignored by the Portal, and therefore it stays.
If at any time you want to stop sharing your project with all users, simply remove the group again from the permission list. To do this, click on the 3 dot menu in the actions column and then select Remove.
The same approach can be applied to a single repository. To do it, open the Repository settings and go to the sub-page SECURITY/Repository permissions. The remaining steps are the same, as for the project described above.