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

build: use bazelisk avoid unexpected Bazel version upgrades #1163

Merged
merged 11 commits into from
Dec 19, 2022

Conversation

suztomo
Copy link
Member

@suztomo suztomo commented Dec 19, 2022

" ci / build (8) " has been failing in #1156. Creating an empty pull request to see the build failures.

This PR changes:

  • The unit tests in Bazel and "coverage" on it have been removed. @blakeli0 intends to remove it in another PR anyway.
  • GitHub Actions to use bazelisk command that keeps the Bazel version stable.
  • The client library generation job is separated from the build job.

As per https://github.com/actions/runner-images/blob/main/images/linux/Ubuntu2204-Readme.md, ubuntu-latest has bazelisk installed.

@suztomo suztomo requested review from a team as code owners December 19, 2022 21:18
@suztomo
Copy link
Member Author

suztomo commented Dec 19, 2022

Bazel version 6.0.0 is suspicious.

Screen Shot 2022-12-19 at 4 21 58 PM

Indeed, I'm able to reproduce the issue in Bazel 6.0.0.

https://github.com/bazelbuild/bazel/releases 6.0.0 was released today.

@suztomo suztomo changed the title chore: test ci build: use googleapis's container to avoid unexpected Bazel version upgrade Dec 19, 2022
@suztomo suztomo changed the title build: use googleapis's container to avoid unexpected Bazel version upgrade build: use bazelisk avoid unexpected Bazel version upgrades Dec 19, 2022
@@ -75,20 +52,63 @@ jobs:
retention-days: 5

- name: Java Linter
run: bazel --batch run //:google_java_format_verification
run: bazelisk --batch run //:google_java_format_verification
Copy link
Collaborator

Choose a reason for hiding this comment

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

I think we can remove Java linter as well if it's already included in the Maven build.

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.

@suztomo suztomo added the automerge Merge the pull request once unit tests and other checks pass. label Dec 19, 2022
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@gcf-merge-on-green gcf-merge-on-green bot merged commit 71f0df1 into main Dec 19, 2022
@gcf-merge-on-green gcf-merge-on-green bot deleted the empty_change branch December 19, 2022 23:24
@gcf-merge-on-green gcf-merge-on-green bot removed the automerge Merge the pull request once unit tests and other checks pass. label Dec 19, 2022
emmileaf pushed a commit that referenced this pull request Dec 20, 2022
" ci / build (8) " has been failing in https://togithub.com/googleapis/gapic-generator-java/pull/1156. Creating an empty pull request to see the build failures.

This PR changes:

- The unit tests in Bazel and "coverage" on it have been removed. @blakeli0 intends to remove it in another PR anyway.
- GitHub Actions to use bazelisk command that keeps the Bazel version stable.
- The client library generation job is separated from the build job.

As per https://togithub.com/actions/runner-images/blob/main/images/linux/Ubuntu2204-Readme.md, ubuntu-latest has bazelisk installed.
emmileaf added a commit that referenced this pull request Dec 20, 2022
This PR updates spring branch with CI fix from #1163 - with commit 71f0df1 cherry-picked from main branch.
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