NE-2191: Adding int pipeline run + custom pipeline definition #301
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@Thealisyed: This pull request references NE-2191 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.21.0" version, but no target version was set. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Thealisyed
force-pushed
the
intpipeline
branch
from
87846c6 to
8c1f4d7
Compare
Thealisyed
force-pushed
the
intpipeline
branch
from
e3cfdb0 to
df79ab1
Compare
Thealisyed
force-pushed
the
intpipeline
branch
from
96520bb to
1670f55
Compare
openshift-merge-robot
added
needs-rebase
Thealisyed
force-pushed
the
intpipeline
branch
from
fb9fe7a to
bee5448
Compare
openshift-merge-robot
added
the
needs-rebase
Thealisyed
force-pushed
the
intpipeline
branch
from
bee5448 to
de2c062
Compare
openshift-merge-robot
removed
the
needs-rebase
Thealisyed
force-pushed
the
intpipeline
branch
from
acb33cb to
e7cfa7d
Compare
alebedev87
left a comment
alebedev87
left a comment
There was a problem hiding this comment.
Another look. The pipeline deploys the operator, it's very good, let's fix the pushing of the artifacts now.
|
|
||
| # Copy the EDO FBC catalog (OCP version-based) | ||
| COPY catalog/v4.21/catalog.yaml /configs/external-dns-operator/catalog.yaml | ||
| COPY catalog/v4.19/catalog.yaml /configs/external-dns-operator/catalog.yaml |
There was a problem hiding this comment.
This change is not needed anymore. The test is supposed to be run on 4.19 as ITS is not linked to 4.19 FBC.
adding the secret to push artifacts
| # /bin/opm (with a serve subcommand) and /bin/grpc_health_probe | ||
| # Note: The base image version should match the targeted OCP version | ||
| FROM registry.redhat.io/openshift4/ose-operator-registry-rhel9:v4.21 | ||
| FROM registry.redhat.io/openshift4/ose-operator-registry-rhel9:v4.19 |
There was a problem hiding this comment.
Why this change? ITS is linked to 4.19 FBC.
| value: main | ||
| - name: pathInRepo | ||
| value: stepactions/fail-if-any-step-failed/0.1/fail-if-any-step-failed.yaml | ||
| - name: verify-image-sources |
There was a problem hiding this comment.
We can remove this task for the moment because all we needed was done in deploy-operator task.
| - name: pathInRepo | ||
| value: .tekton/pipelines/deploy-fbc-operator.yaml | ||
| - name: CREDENTIALS_SECRET_NAME | ||
| value: ext-dns-optr-fbc-v9-19-pull |
There was a problem hiding this comment.
| value: ext-dns-optr-fbc-v9-19-pull | |
| value: ext-dns-optr-fbc-v4-21-pull |
|
@Thealisyed: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
5 participants
Adding the integration test pipeline run + a customized pipeline definition to external-dns-operator for the FBC Integration testing
Pipeline run from konflux-ci
Pipelines deploy yaml from Konflux ci