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

Add simple cloudbuild config #4

Merged
merged 5 commits into from
Feb 10, 2023
Merged

Conversation

AlCutter
Copy link
Contributor

@AlCutter AlCutter commented Feb 9, 2023

No description provided.

@AlCutter
Copy link
Contributor Author

AlCutter commented Feb 9, 2023

CodeQL error is "error, no code to QL"

cloudbuild.yaml Outdated
args: ["golangci-lint","run"]

- id: 'unit tests'
name: 'golang:1.20'
Copy link
Contributor

Choose a reason for hiding this comment

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

Any reason for 1.20 here? The go.mod is 1.19 so I'd be tempted to sync them?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sure, 0.01 less golang done!

@AlCutter
Copy link
Contributor Author

hmm, the lint wants there to be a go module to check... perhaps we should check in an "empty"/minimal module?

@mhutchinson
Copy link
Contributor

I'll just check in the code I have I guess. I've tested it locally. Seems easier than other messing about.

cloudbuild.yaml Outdated

steps:
- id: 'lint'
name: "golangci/golangci-lint"
Copy link
Contributor

Choose a reason for hiding this comment

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

Will this just run whatever is the latest version? We will want something hermetic or incoming PRs will be blocked on fixing up incidental changes because the ruleset has changed.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Pinned to 1.51.

Broadly agree about random drive-by blockings, but I think it is helpful to be aware of when the codebase needs bringing into line with latest best practices (and it was certainly useful that we got the returned-errors-being-ignored warning here), but perhaps there's a better path for that which won't randomly ding PRs.

Sadly dependabot doesn't currently support updating build steps in GCB.

Copy link
Contributor

Choose a reason for hiding this comment

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

I'm totally supportive of following the latest version, but it should be done with a config file checked into the repo. Shame that dependabot has a blind spot here.

@mhutchinson
Copy link
Contributor

Rebase and give this another go?

@AlCutter AlCutter merged commit f3c0373 into transparency-dev:main Feb 10, 2023
@AlCutter AlCutter deleted the cloudbuild branch February 10, 2023 15:31
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