Skip to content

go/tools/bazel_testing: add BazelCmd and BazelOutput#2222

Merged
jayconrod merged 1 commit intobazel-contrib:masterfrom
jayconrod:bazelcmd
Sep 18, 2019
Merged

go/tools/bazel_testing: add BazelCmd and BazelOutput#2222
jayconrod merged 1 commit intobazel-contrib:masterfrom
jayconrod:bazelcmd

Conversation

@jayconrod
Copy link
Copy Markdown
Collaborator

Fixes #2189

@jayconrod jayconrod merged commit 2b5ae12 into bazel-contrib:master Sep 18, 2019
@jayconrod jayconrod deleted the bazelcmd branch September 18, 2019 17:24
jayconrod pushed a commit that referenced this pull request Dec 4, 2019
yushan26 pushed a commit to yushan26/rules_go that referenced this pull request Jun 16, 2025
Before this PR the users could not override how the hermetic toolchain
is downloaded when in `bzlmod`. However, the same APIs would be
available to users using `WORKSPACE`. With this we also allow root
modules to restrict which toolchain versions the non-root modules, which
may be helpful when optimizing the CI runtimes so that we don't waste
time downloading multiple `micro` versions of the same `3.X` python
version, which most of the times have identical behavior.

Whilst at it, tweak the `semver` implementation to allow for testing of
absence of values in the original input.

Work towards bazel-contrib#2081 and this should be one of the last items that are
blocking bazel-contrib#1361 from the API point of view.

Replaces bazel-contrib#2151.

---------

Co-authored-by: Richard Levasseur <richardlev@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bazel_testing: more flexibility for running commands

2 participants