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

Clarify upgrade advice for bazelisk #22171

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

BetsyMcPhail
Copy link
Contributor

@BetsyMcPhail BetsyMcPhail commented Nov 13, 2024

Towards #22087

When performing upgrades using the semi-automated script, most externals only require the standard pre-merge jobs to test. In the case of bazelisk, however, an unprovisioned Linux job should also be run. Add a reminder to the documentation.


This change is Reviewable

Copy link
Contributor Author

@BetsyMcPhail BetsyMcPhail left a comment

Choose a reason for hiding this comment

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

+@nicolecheetham for review

Reviewable status: LGTM missing from assignee nicolecheetham, needs platform reviewer assigned, needs at least two assigned reviewers, missing label for release notes (waiting on @BetsyMcPhail)

@BetsyMcPhail BetsyMcPhail added the release notes: none This pull request should not be mentioned in the release notes label Nov 13, 2024
Copy link
Contributor

@nicolecheetham nicolecheetham left a comment

Choose a reason for hiding this comment

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

It appears tools/workspace/bazelisk/repository.bzl line 22 is too long so Jenkins jobs fails. The line is 79 characters. Should just need to be a word or two shorter. Also, the instructions are still not clear how to go about manually updating the checksums. Specifically, how to get/create the new checksums.

Reviewable status: LGTM missing from assignee nicolecheetham, needs platform reviewer assigned, needs at least two assigned reviewers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release notes: none This pull request should not be mentioned in the release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants