Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 33 additions & 0 deletions konflux-ci/release-snapshot.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
# Applying this manifest will create a snapshot in Konflux with specific images for the operator and the bundle
# Since images could be built in different PRs there could be some misalignment between the bundle and the operator images
# Retrieve the specific images SHA and last revision:
# * from the Konflux UI:
# in the Application > Components > [component]
# Latest build > Build container image
# Latest image > image label
# * from the CLI:
# $ oc get component deployment-validation-operator -o yaml | yq .status.lastPromotedImage
# $ oc get component deployment-validation-operator -o yaml | yq .status.lastBuiltCommit
---
apiVersion: appstudio.redhat.com/v1alpha1
kind: Snapshot
metadata:
name: manual-release-snapshot
namespace: dvo-obsint-tenant
labels:
test.appstudio.openshift.io/type: override
spec:
application: deployment-validation-operator
components:
- name: deployment-validation-operator
containerImage: quay.io/redhat-user-workloads/dvo-obsint-tenant/deployment-validation-operator/deployment-validation-operator@sha256:0e312d3edc28b931b721eb5ddc59feea4f9141707925224f6b936401b479b4b1
source:
git:
url: https://github.com/app-sre/deployment-validation-operator
revision: b861deee00c1afc3ba91ffac56932d24870358c9
- name: deployment-validation-operator-bundle
containerImage: quay.io/redhat-user-workloads/dvo-obsint-tenant/deployment-validation-operator-bundle@sha256:a96eb0ba48f11f163d243cead0519dd58de726e64963ed5e5ddcc19f253ba201
source:
git:
url: https://github.com/app-sre/deployment-validation-operator
revision: b861deee00c1afc3ba91ffac56932d24870358c9
19 changes: 19 additions & 0 deletions konflux-ci/release-staging.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
# Applying this manifest will trigger a new release.
# Temporary or automatic konflux snapshots may deliver a failed release
# To check the process and logs, connect to the UI and navigate to Application > Releases > [release-name] > PipelineRun
---
apiVersion: appstudio.redhat.com/v1alpha1
kind: Release
metadata:
name: staging-release-test-pxmtl
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this a temporary name? I am wondering if the test-pxmtl suffix makes sense.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah the file is a stub, I usually match the suffix with the one from the snapshot. That's why it looks arbitrary. As this is applied in the cluster directly there is no way of creating another entity with the same name (the system won't let you).
I included them in the repo to have this work saved somewhere, despite the fact that we will need to change the image digests and the names when we properly release it on prod.

namespace: dvo-obsint-tenant
spec:
releasePlan: release-plan-staging
snapshot: deployment-validation-operator-pxmtl
data:
releaseNotes:
topic: Test Release
synopsis: Test to debug Release process
description: Test to debug Release process
solution: ""
references: ""