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

Various fixes to initial GitHub Actions #1818

Merged
merged 3 commits into from Sep 17, 2022

Conversation

jarrpa
Copy link
Member

@jarrpa jarrpa commented Sep 16, 2022

...that merged too early in #1814 ;)

The golangci-lint changes were tricky, but basically it comes down to some weirdness in running it using Go 1.19 versus Go 1.18 for golangci-lint v1.49.0. Specifically, it was this change in 1.48.0 that was causing us so much pain: golangci/golangci-lint#3002

In addition, the original configuration listed both go-version and go-version-file configuration options, and go-version was being taken as the preferred one. Unfortunately, our code still fails against Go 1.19 for some reason, so for the time being we're forcing the Action to target Go 1.18 across the job's config matrix. I kept the matrix at ["1.18","1.19"] just so we don't have to change it later when we do start moving to 1.19.

Signed-off-by: Jose A. Rivera jarrpa@redhat.com

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 16, 2022
@@ -69,7 +73,7 @@ jobs:
strategy:
fail-fast: false
matrix:
go: ["1.17", "1.18"]
go: ["1.18", "1.19"]
make-target: ["verify-deps", "verify-generated", "verify-latest-csv", "verify-operator-bundle", "verify-latest-deploy-yaml"]
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we need this make-target matrix any more?

Copy link
Member Author

Choose a reason for hiding this comment

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

Good catch!

Copy link
Member Author

Choose a reason for hiding this comment

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

Removed, and also fixed some of the jobs that had wrong targets 😂

...that merged too early ;)

Signed-off-by: Jose A. Rivera <jarrpa@redhat.com>
Signed-off-by: Jose A. Rivera <jarrpa@redhat.com>
Signed-off-by: Jose A. Rivera <jarrpa@redhat.com>
Copy link
Contributor

@malayparida2000 malayparida2000 left a comment

Choose a reason for hiding this comment

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

/lgtm

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

openshift-ci bot commented Sep 17, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jarrpa, malayparida2000

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-merge-robot openshift-merge-robot merged commit b229287 into red-hat-storage:main Sep 17, 2022
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.

None yet

3 participants