This is a clone of issue OCPBUGS-42228. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-42227. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-42226. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-42225. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-42217. The following is the description of the original issue:
—
Description of problem:
The instructions for disabling a build by strategy instruct admins to _add_ permissions to create builds for the other build strategies. This is dead wrong.
Version-Release number of selected component (if applicable):
4.12
How reproducible:
Always
Steps to Reproduce:
0. Create sample BuildConfigs using the Docker and Source build strategies, and start a build.
1. Follow instructions on https://docs.openshift.com/container-platform/4.12/cicd/builds/securing-builds-by-strategy.html#builds-disabling-build-strategy-globally_securing-builds-by-strategy end to end, for the Docker and Source strategy.
2. Try to create a Docker, Source, or Custom strategy BuildConfig
3. Try to start a build for the respective strategy
4. Try to create a Custom strategy build as a regular developer/edit user
Actual results:
Developers can create Custom strategy builds. Source strategy build is not disabled.
Expected results:
Source and Docker strategy builds are disabled globally. Customers can't create or start builds with these strategies.
Additional info:
Doc link: https://docs.openshift.com/container-platform/4.12/cicd/builds/securing-builds-by-strategy.html#builds-disabling-build-strategy-globally_securing-builds-by-strategy
- blocks
-
OCPBUGS-42230 Instructions for Disabling Build Strategy Incorrect
-
- Closed
-
- clones
-
-
- Closed
-
- is blocked by
-
-
- Closed
-
- is cloned by
-
-
- Closed
-
- links to