Wiki source code of Shared Projects and Repositories
Version 2.4 by Boris Folgmann on 2025/05/22 14:21
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
1.2 | 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 | |||
| |
1.5 | 3 | However, as a Project ADMIN, you can manually change the permissions on a single repository or on a complete project. |
| |
1.3 | 4 | |
| |
1.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 | |||
| |
1.11 | 7 | In the following example the steps for changing a complete project are shown. |
| 8 | |||
| |
2.2 | 9 | 1. Go to the Project settings of the Project in Bitbucket and open the sub page SECURITY/Project Permissions. |
| |
2.3 | 10 | [[image:1747923524767-792.png]]((( |
| |
2.4 | 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. |
| |
2.3 | 12 | ))) |
| |
2.4 | 13 | 1. ((( |
| 14 | Press the button "Add user or group" on | ||
| 15 | ))) | ||
| |
1.11 | 16 | |
| 17 |