-
Feature
-
Resolution: Done
-
Major
-
None
-
None
Feature Overview
Quay Bridge operator to support Jenkins
Goals
Existing customers or new prospects already have Jenkins as their CI/CD pipeline. To leverage Quay as the container scanning tool we need the Quay Bridge operator to support Jenkins. From our understanding according to case number 02806796 that combination has not been tested and is not supported. Salesforce opportunity identification (ID): 4154705 .
Requirements
| requirement | Notes | isMvp |
| Ensure that the Quay Bridge operator is compliant with Jenkins. | Currently, Quay Bridge operator is not compliant with Jenkins. It interrupts even a simple activity to initiate a build using a simple Jenkinsfile that does not even interact with an image registry such as Quay – Support Case 02806796 | No |
(Optional) Use Cases
The user is not able to use Jenkins Build Now feature when the Quay Bridge Operator is installed.
All Jenkins users that want to use Quay Bridge Operator are affected by this issue.
It’s an operator that helps integration with external Quay registry and does not affect the OpenShift console user interface directly.
Background, and strategic fit
Please refer to Support Case Number 02806796 for detailed description of the issue. The “Build Now” capability on Jenkins user interface fails when the Quay Bridge Operator is installed.
Assumptions
Quay bridge operator is installed on OCP.
Documentation Considerations
- This will require a documentation addition: release notes and installation
Questions
| Question | Outcome |
- is related to
-
PROJQUAY-1422 Investigate Quay Bridge Operator Breaking Jenkins Builds on OCP
-
- Closed
-