-
Notifications
You must be signed in to change notification settings - Fork 140
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
Release binary names are not correct #101
Comments
So issues:
|
bazel-io
pushed a commit
to bazelbuild/bazel
that referenced
this issue
Jul 25, 2017
The new pipeline does not support ziping artifact which was a custom hack for Windows, relies on Bazel to generate those zip instead. Step forward fixing bazelbuild/continuous-integration#101 To cherry-pick for #3375. Change-Id: Id566d66bb179096d60c5b535f245d64cea28c5b8 PiperOrigin-RevId: 163054883
buchgr
pushed a commit
to bazelbuild/bazel
that referenced
this issue
Jul 26, 2017
The new pipeline does not support ziping artifact which was a custom hack for Windows, relies on Bazel to generate those zip instead. Step forward fixing bazelbuild/continuous-integration#101 To cherry-pick for #3375. Change-Id: Id566d66bb179096d60c5b535f245d64cea28c5b8 PiperOrigin-RevId: 163054883
abergmeier-dsfishlabs
pushed a commit
to abergmeier-dsfishlabs/bazel
that referenced
this issue
Aug 23, 2017
The new pipeline does not support ziping artifact which was a custom hack for Windows, relies on Bazel to generate those zip instead. Step forward fixing bazelbuild/continuous-integration#101 To cherry-pick for bazelbuild#3375. Change-Id: Id566d66bb179096d60c5b535f245d64cea28c5b8 PiperOrigin-RevId: 163054883
joeleba
pushed a commit
to joeleba/continuous-integration
that referenced
this issue
Jun 17, 2019
Fixes bazelbuild#101 Change-Id: I0b0af821a617b4924ccfba17793387eed6fd2a7e
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Used to be:
Now:
The text was updated successfully, but these errors were encountered: