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 support for AArch64 release artifacts #12319

Closed
wants to merge 1 commit into from

Conversation

koleini
Copy link
Contributor

@koleini koleini commented Oct 20, 2020

kokoro scripts are updated to support:

  1. bazelisk v1.7.2
  2. AArch64 release artifacts

@google-cla
Copy link

google-cla bot commented Oct 20, 2020

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.


What to do if you already signed the CLA

Individual signers
Corporate signers

ℹ️ Googlers: Go here for more info.

@google-cla google-cla bot added the cla: no label Oct 20, 2020
@koleini
Copy link
Contributor Author

koleini commented Oct 22, 2020

@googlebot I signed it!

@google-cla google-cla bot added cla: yes and removed cla: no labels Oct 22, 2020
@jin jin added area-EngProd Bazel CI, infrastructure, bootstrapping, release, and distribution tooling team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website labels Oct 26, 2020
@philwo
Copy link
Member

philwo commented Jun 16, 2021

Hi @koleini,

I'm very sorry that this wasn't merged yet. I must have overlooked it during multiple passes of reviewing my backlog :(

We can probably merge this, but I wonder - is there anything in particular you think would be achieved by this PR? The scripts that you patch are currently unused by our release infrastructure. They were created to prototype building on a new release infra, but we haven't gotten around to do the switch. So, while we can certainly merge this, it would not change anything visibly yet.

Would that be OK for you (maybe you're using these scripts for something internally)? Or do you need something else, too?

Cheers,
Philipp

@bazel-io bazel-io closed this in 912fa90 Jun 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-EngProd Bazel CI, infrastructure, bootstrapping, release, and distribution tooling cla: yes team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants