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

WIP Feature/cert pipeline #284

Merged
merged 7 commits into from
Nov 8, 2021
Merged

WIP Feature/cert pipeline #284

merged 7 commits into from
Nov 8, 2021

Conversation

dacleyra
Copy link
Contributor

@dacleyra dacleyra commented Nov 3, 2021

To pass certification checks

  • annotations.yaml needs
    • openshift.versions
      • CHANNELS, DEFAULT_CHANNELS with default; must be set to generate their required associated annotations
  • remove the operator service account yaml, this should be created by OLM & fails a cert check
    • didn't seem to be a great way to remove it via a kustomize option; make bundle vs. make install needing the sa

@dacleyra dacleyra requested a review from zach-source November 3, 2021 14:08
Copy link

@zach-source zach-source left a comment

Choose a reason for hiding this comment

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

Minor nits.

cd $TMP_DIR/certified-operators-preprod
git add --all
git commit -m $VERSION
git push

Choose a reason for hiding this comment

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

Can you use branches or it has to be a main commit&push?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

they actually just changed the repo in the instructions, and the default branch was stage, now it is main
we can set this to our choice of branch, the git_branch is specified in the tekton run
let me know how you want to handle it

Choose a reason for hiding this comment

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

Let's create a branch named for the release off the version and pass that. It'll let us keep stuff separate. Maybe at some point we can trigger actions on merge. If that's too complicated to do right now we can do follow on. First priority is a release of 2.4.0

v2/hack/certify/certify.sh Show resolved Hide resolved
v2/hack/certify/certify.sh Show resolved Hide resolved
v2/hack/certify/certify.sh Outdated Show resolved Hide resolved
v2/hack/certify/certify.sh Outdated Show resolved Hide resolved
Copy link

@zach-source zach-source left a comment

Choose a reason for hiding this comment

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

Satisfied with the feedback.

Copy link

@zach-source zach-source left a comment

Choose a reason for hiding this comment

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

Still WIP

@dacleyra dacleyra merged commit 06e6515 into release/2.4.1 Nov 8, 2021
@zach-source zach-source deleted the feature/certPipeline branch April 14, 2022 14:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants