Changes for page Shared Projects and Repositories
Last modified by Boris Folgmann on 2025/05/22 14:38
From version 2.3
edited by Boris Folgmann
on 2025/05/22 14:20
on 2025/05/22 14:20
Change comment:
There is no comment for this version
To version 1.3
edited by Boris Folgmann
on 2025/05/22 14:10
on 2025/05/22 14:10
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 1 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,14 +1,5 @@ 1 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 2 3 -However, as a Project ADMIN,you can manually change the permissionson a single repository or on a complete project.3 +However, as a project ADMIN you can manually change the permission on a single repository or on a complete project. 4 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 used by the portal for 12 -))) 13 - 14 14
- 1747923524767-792.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -xwiki:XWiki.borisfolgmannt-systemscom - Size
-
... ... @@ -1,1 +1,0 @@ 1 -282.4 KB - Content