Skip to content

OCPBUGS-30333: Move Helm to bingo dep and update it #837

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

Merged
merged 7 commits into from
Aug 15, 2024

Conversation

bentito
Copy link
Contributor

@bentito bentito commented Aug 9, 2024

We're adding bingo to the top level of this monorepo. In doing this we are also changing the dependency to a version of Helm that is free of the target bug.

Actual files in need of review:
.bingo/*
Makefile
go.mod
go.sum
scripts/generate_crds_manifests.sh
tools.go

@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 9, 2024
@openshift-ci-robot
Copy link

@bentito: This pull request references Jira Issue OCPBUGS-30333, which is invalid:

  • expected the bug to target either version "4.18." or "openshift-4.18.", but it targets "4.17" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

We're adding bingo to the top level of this monorepo. In doing this we are also changing the dependency to a version of Helm that is free of the target bug.

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.

@openshift-ci openshift-ci bot requested review from dinhxuanvu and tmshort August 9, 2024 18:15
@bentito
Copy link
Contributor Author

bentito commented Aug 9, 2024

/jira refresh

@openshift-ci-robot
Copy link

@bentito: This pull request references Jira Issue OCPBUGS-30333, which is invalid:

  • expected the bug to target either version "4.18." or "openshift-4.18.", but it targets "4.17" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

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.

@bentito
Copy link
Contributor Author

bentito commented Aug 9, 2024

/jira refresh

@openshift-ci-robot
Copy link

@bentito: This pull request references Jira Issue OCPBUGS-30333, which is invalid:

  • expected the bug to target either version "4.18." or "openshift-4.18.", but it targets "4.17" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

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.

@perdasilva
Copy link
Contributor

/jira refresh

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Aug 13, 2024
@openshift-ci-robot
Copy link

@perdasilva: This pull request references Jira Issue OCPBUGS-30333, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.18.0) matches configured target version for branch (4.18.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

In response to this:

/jira refresh

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.

@openshift-ci-robot openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Aug 13, 2024
@grokspawn
Copy link
Contributor

lgtm, but I'll just stick one label on here in case someone else wants to 👀 today. Otherwise I'll try to circle back around and merge.

/approve

Copy link
Contributor

openshift-ci bot commented Aug 13, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bentito, grokspawn

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 Aug 13, 2024
@grokspawn
Copy link
Contributor

/lgtm

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 14, 2024
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 14, 2024
@bentito bentito force-pushed the bingoify-monorepo branch from 1d3453f to 4e3cd64 Compare August 14, 2024 23:58
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Aug 14, 2024
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 14, 2024
@grokspawn
Copy link
Contributor

/lgtm
/label tide/merge-method-squash

@openshift-ci openshift-ci bot added tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. lgtm Indicates that a PR is ready to be merged. labels Aug 15, 2024
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD caef475 and 2 for PR HEAD 4e3cd64 in total

Copy link
Contributor

openshift-ci bot commented Aug 15, 2024

@bentito: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-gcp-olm-flaky 4e3cd64 link false /test e2e-gcp-olm-flaky

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.

@openshift-merge-bot openshift-merge-bot bot merged commit 7915649 into openshift:master Aug 15, 2024
12 of 13 checks passed
@openshift-ci-robot
Copy link

@bentito: Jira Issue OCPBUGS-30333: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-30333 has been moved to the MODIFIED state.

In response to this:

We're adding bingo to the top level of this monorepo. In doing this we are also changing the dependency to a version of Helm that is free of the target bug.

Actual files in need of review:
.bingo/*
Makefile
go.mod
go.sum
scripts/generate_crds_manifests.sh
tools.go

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.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: operator-lifecycle-manager
This PR has been included in build operator-lifecycle-manager-container-v4.18.0-202408150943.p0.g7915649.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: operator-registry
This PR has been included in build operator-registry-container-v4.18.0-202408150943.p0.g7915649.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-operator-framework-tools
This PR has been included in build ose-operator-framework-tools-container-v4.18.0-202408150943.p0.g7915649.assembly.stream.el9.
All builds following this will include this PR.

@m1kola
Copy link
Contributor

m1kola commented Sep 5, 2024

/jira refresh

@openshift-ci-robot
Copy link

@m1kola: Jira Issue OCPBUGS-30333 is in an unrecognized state (MODIFIED) and will not be moved to the MODIFIED state.

In response to this:

/jira refresh

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.

anik120 pushed a commit to anik120/operator-framework-olm that referenced this pull request Sep 5, 2024
* Add bingo for Helm dep

* Add bingo for Helm dep - vendor changes

Signed-off-by: Brett Tofel <[email protected]>

* Rm debug statement

Signed-off-by: Brett Tofel <[email protected]>

* Sync bingo go version with toolchain go version

Signed-off-by: Brett Tofel <[email protected]>

* Some Go debugging lines to debug helm bin path

Signed-off-by: Brett Tofel <[email protected]>

* Add helm dependency to verify target

Signed-off-by: Brett Tofel <[email protected]>

* Move down the bingo include to protect early defs

Signed-off-by: Brett Tofel <[email protected]>

---------

Signed-off-by: Brett Tofel <[email protected]>
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. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants