Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update konflux documentation #294

Merged
merged 2 commits into from
Dec 17, 2024

Conversation

AnnaZivkovic
Copy link
Contributor

No description provided.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 25, 2024
@AnnaZivkovic AnnaZivkovic force-pushed the update-konflux-doc branch 5 times, most recently from 362d437 to afb6c35 Compare September 25, 2024 21:48
@@ -1,10 +1,10 @@
### Release the operator (for OCP)

1. Choose a snapshot from the list of snapshots and double check post-submits passed for it.
1. Creat a new branch off of `main`. example `v1.0`, `v0.9`
Copy link
Member

Choose a reason for hiding this comment

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

I think the creation of the branch shouldn't stay here. If we want to release 1.0.z,we should only need to select the snapshot and run the release with it and referring the 1.0 application (and branch).

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I can make step 1 optional if we are doing that. Just wanted to document the branch name, but maybe that is to basic.

@AnnaZivkovic AnnaZivkovic force-pushed the update-konflux-doc branch 2 times, most recently from 4498a44 to 801ff20 Compare September 30, 2024 21:11
@AnnaZivkovic AnnaZivkovic changed the title WIP: Update konflux documentation Update konflux documentation Sep 30, 2024
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 30, 2024
@AnnaZivkovic AnnaZivkovic force-pushed the update-konflux-doc branch 2 times, most recently from 080e6f8 to 54e637b Compare October 9, 2024 00:17
@aleskandro
Copy link
Member

/test integration

@aleskandro
Copy link
Member

/test unit

Copy link

openshift-ci bot commented Oct 14, 2024

@aleskandro: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

  • /test bundle
  • /test ci-index-multiarch-tuning-operator-bundle
  • /test fmt
  • /test generate
  • /test goimports
  • /test images
  • /test images-multi
  • /test lint
  • /test manifests
  • /test ocp416-ci-index-multiarch-tuning-operator-bundle
  • /test ocp416-e2e-gcp
  • /test ocp416-images
  • /test ocp417-ci-index-multiarch-tuning-operator-bundle
  • /test ocp417-e2e-gcp
  • /test ocp417-images
  • /test ocp418-ci-index-multiarch-tuning-operator-bundle
  • /test ocp418-e2e-gcp
  • /test ocp418-images
  • /test sast
  • /test unit
  • /test vendor
  • /test vet

The following commands are available to trigger optional jobs:

  • /test security

Use /test all to run the following jobs that were automatically triggered:

  • pull-ci-openshift-multiarch-tuning-operator-main-ci-index-multiarch-tuning-operator-bundle
  • pull-ci-openshift-multiarch-tuning-operator-main-images
  • pull-ci-openshift-multiarch-tuning-operator-main-ocp416-ci-index-multiarch-tuning-operator-bundle
  • pull-ci-openshift-multiarch-tuning-operator-main-ocp416-images
  • pull-ci-openshift-multiarch-tuning-operator-main-ocp417-ci-index-multiarch-tuning-operator-bundle
  • pull-ci-openshift-multiarch-tuning-operator-main-ocp417-images
  • pull-ci-openshift-multiarch-tuning-operator-main-ocp418-ci-index-multiarch-tuning-operator-bundle
  • pull-ci-openshift-multiarch-tuning-operator-main-ocp418-images

In response to this:

/test integration

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.

docs/ocp-release.md Outdated Show resolved Hide resolved
docs/ocp-release.md Outdated Show resolved Hide resolved
docs/ocp-release.md Outdated Show resolved Hide resolved
docs/ocp-release.md Outdated Show resolved Hide resolved
docs/ocp-release.md Outdated Show resolved Hide resolved
docs/ocp-release.md Outdated Show resolved Hide resolved
docs/ocp-release.md Outdated Show resolved Hide resolved
docs/ocp-release.md Outdated Show resolved Hide resolved
@AnnaZivkovic AnnaZivkovic force-pushed the update-konflux-doc branch 3 times, most recently from 0fc08ca to 14a9da2 Compare October 22, 2024 16:32
docs/ocp-release.md Outdated Show resolved Hide resolved
docs/ocp-release.md Outdated Show resolved Hide resolved
docs/ocp-release.md Outdated Show resolved Hide resolved

### Create a new FBC fragment for a new OCP release
10. Create a new Release for the operator snapshot in the previous step.
Copy link
Member

Choose a reason for hiding this comment

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

I think we also need to update the RPA to allow the new 'tag' (e.g., v1.0.1) and create it in comet.

Copy link

openshift-ci bot commented Dec 16, 2024

@AnnaZivkovic: all tests passed!

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.

@aleskandro
Copy link
Member

Thanks @AnnaZivkovic

feel free to /approve when you can merge it

@aleskandro
Copy link
Member

(I would squash the two commits and rebase first)

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 17, 2024
Copy link

openshift-ci bot commented Dec 17, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aleskandro

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 17, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit 08443ba into openshift:main Dec 17, 2024
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants