Wiki source code of Shared Projects and Repositories
Version 3.2 by Boris Folgmann on 2025/05/22 14:24
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | When a project is created on the DevOps Portal of type PRIVATE, it means that no user can access it without a role assignment. | ||
| 2 | |||
| 3 | However, as a Project ADMIN, you can manually change the permissions on a single repository or on a complete project. | ||
| 4 | |||
| 5 | 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. | ||
| 6 | |||
| 7 | In the following example the steps for changing a complete project are shown. | ||
| 8 | |||
| 9 | 1. Go to the Project settings of the Project in Bitbucket and open the sub page SECURITY/Project Permissions. | ||
| 10 | [[image:1747923524767-792.png]]((( | ||
| 11 | 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. | ||
| 12 | ))) | ||
| 13 | 1. ((( | ||
| 14 | 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 containers all users having access to this Bitbucket. For permission select Read. It's strictly recommend to not use higher permssions. Then press "Add". | ||
| 15 | [[image:1747923859647-669.png||height="215" width="440"]] | ||
| 16 | ))) | ||
| 17 | 1. ((( | ||
| 18 | The permission list now contains one more entry. | ||
| 19 | |||
| 20 | ))) | ||
| 21 | |||
| 22 |