| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We'll just replace them with either native support for running tests inside
Docker containers on CI or with VMs running the operating system.
This gets rid of the "let's download 8 GB of Docker images" step when running
`bazel build //...`.
RELNOTES: None.
Closes #4506.
PiperOrigin-RevId: 183078052
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 178892596
|
|
|
|
|
|
|
|
| |
This is because I want to add another remote execution related tool, the remote_client, which will use the Remote Execution API to fetch blobs from a remote cache. I will use this tool as part of end-to-end tests for remote execution.
TESTED=remote integration tests, presubmit
RELNOTES: None
PiperOrigin-RevId: 177995895
|
|
|
|
|
| |
Change-Id: Iabc89286a10dd4d3314f3480f87ac74b34aee969
PiperOrigin-RevId: 167855167
|
|
|
|
|
| |
Change-Id: Id31ff0fcf72388fe1e5697b57e67385c6c27824b
PiperOrigin-RevId: 164720069
|
|
|
|
|
|
|
|
|
|
|
|
| |
This will make it easier to work on Bazel's core tools like buildjar,
singlejar and the JUnit test runner.
Also correctly mark their tests as test code in the project.
RELNOTES: None.
Change-Id: Id79810b4c78b73d92b9c01b1d33f77b7504eab3d
PiperOrigin-RevId: 162472964
|
|
|
|
|
|
| |
Happy dance \o/
PiperOrigin-RevId: 160412092
|
|
|
|
|
|
|
|
| |
Without this change you can't work on any code that's not in src/{main,test} in IntelliJ, e.g. tools like the remote_worker.
Closes #3224.
PiperOrigin-RevId: 159812248
|
|
--
Change-Id: Iedbdf32a80e0a4390ff8084a67eba191f544517f
Reviewed-on: https://cr.bazel.build/7770
PiperOrigin-RevId: 141771456
MOS_MIGRATED_REVID=141771456
|