This repository has been archived by the owner on Oct 2, 2023. It is now read-only.
Update puller and loader locations and sequencing in cloudbuild #1608
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The location and naming of go binary artifacts changed when rules_go was updated in bazelbuild@db48e7c. This is likely due to the changes in bazel-contrib/rules_go@695da59 and bazel-contrib/rules_go@7a2ed94. Since builds on all platforms now place the artifacts in the same location, the darwin build can only begin once the linux uploads are complete.
|
/assign @smukherj1 |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cgdolan, smukherj1 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/gcbrun |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The location and naming of go binary artifacts changed when rules_go was updated in db48e7c. This is likely due to the changes in bazel-contrib/rules_go@695da59 and bazel-contrib/rules_go@7a2ed94.
Since builds on all platforms now place the artifacts in the same location, the darwin build can only begin once the linux uploads are complete.