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

Fetch rolling releases from GCS #228

Closed
fweikert opened this issue Apr 1, 2021 · 4 comments · Fixed by #319
Closed

Fetch rolling releases from GCS #228

fweikert opened this issue Apr 1, 2021 · 4 comments · Fixed by #319

Comments

@fweikert
Copy link
Member

fweikert commented Apr 1, 2021

Bazelisk currently fetches rolling releases from GitHub. However, GCS generally has higher availability, so we should just download release binaries from GCS.

Note: This request is currently blocked by the fact that we don't actually publish rolling releases yet.

@davido
Copy link
Contributor

davido commented Jun 2, 2021

Just noticed:

  $ cat .bazelversion
  5.0.0-pre.20210510.2rc1

Doesn't seem to work:

  $ bazelisk build gerrit
2021/06/02 13:03:32 could not resolve the version '5.0.0-pre.20210510.2rc1' to an actual version number: Invalid version '5.0.0-pre.20210510.2rc1'

@fweikert
Copy link
Member Author

fweikert commented Jun 2, 2021

We currently don’t support release candidates of rolling releases. Right now there’s only a single rolling release, 5.0.0-pre.20210510.2.2, which will be fetched from GitHub (please make sure that you have the latest Bazelisk version).

Our release infra still has some rough edges when it comes to rolling releases - I want to polish it next week and also publish better documentation.

@davido
Copy link
Contributor

davido commented Jun 2, 2021

Thanks for clarifying.

It worked with: 5.0.0-pre.20210510.2.2 with Bazelisk@HEAD.

keith added a commit to keith/bazelisk that referenced this issue May 20, 2022
keith added a commit to keith/bazelisk that referenced this issue May 21, 2022
@keith
Copy link
Member

keith commented May 21, 2022

Here's a PR for this original issue #319

fweikert pushed a commit that referenced this issue Jun 3, 2022
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 a pull request may close this issue.

3 participants