| commit | 9c62401ba71b7760040797ee063d20d05cd5172d | [log] [tgz] |
|---|---|---|
| author | Samuel Giddins <segiddins@squareup.com> | Thu Apr 02 23:29:45 2020 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Apr 02 23:30:53 2020 -0700 |
| tree | 40851e17918ce4706e62b312752ddbbe78244ee2 | |
| parent | c47223aef658db9921d466fdd66d32d2aad2a64b [diff] |
Don't consider a workspace directory a marker of being in a workspace Jenkins workers tend to place all of their Jenkins workspaces in a directory named `workspace`. On a case-insensitive filesystem, Bazel would consider anything run by Jenkins as being in a Bazel workspace, because of that `workspace` directory being in the filesystem hierarchy of the cwd. Avoid this by only looking for _files_ named `workspace` when determining if a directory is potentially a Bazel workspace. Closes #10947. PiperOrigin-RevId: 304553522
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
See CONTRIBUTING.md
