| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
| |
This group was not up to date and the mailing list contains way more
than that. Replaced by a mailing list where I invited the current list.
--
MOS_MIGRATED_REVID=139910623
|
|
|
|
|
|
|
| |
--
Change-Id: I024cc6062bf2a167e38fdb5cacde63eb062a9703
Reviewed-on: https://cr.bazel.build/7430
MOS_MIGRATED_REVID=139887482
|
|
|
|
|
|
|
| |
This is just a quick update before revamping the roadmap for 2017
--
MOS_MIGRATED_REVID=139886797
|
|
|
|
|
|
|
| |
--
Change-Id: I86660a0101261b42a06bb94afe0bc9f0bc5e5528
Reviewed-on: https://cr.bazel.build/6697
MOS_MIGRATED_REVID=139574326
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Skylark already has ctx.configuration.coverage_enabled to determine if coverage data collection is on for an entire run. But that does not reveal which targets specifically are supposed to be instrumented (based on the values of --instrumentation_filer and --instrument_test_targets). This is inefficient for languages which add coverage instrumentation at compile-time, though correct coverage output can still be produced by instrumenting everything and filtering later.
By default, this function returns whether the rule represented by ctx should be instrumented. If a Skylark Target (e.g. from a label or label_list attribute in ctx.attr) is passed to the function, it instead returns whether that Target is a rule whose sources should be instrumented. Rules that directly incorporate source-files from their dependencies before compilation (e.g. header files) may need to know if those source files need to be instrumented when compiled.
Expanded the documentation of instrumented_files to be a more general section on implementing code coverage instrumentation in Skylark.
Also tweaked the code comment and variable names for the version of shouldIncludeLocalSources that takes a TransitiveInfoCollection.
RELNOTES: Add ctx.coverage_instrumented function to Skylark, to indicate whether a specific targets should be instrumented for code coverage data collection.
--
MOS_MIGRATED_REVID=139460989
|
|
|
|
|
|
|
|
|
|
| |
The attribute for the source list is "srcs", not "src".
Closes #2098.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/2098
MOS_MIGRATED_REVID=139380743
|
|
|
|
|
|
|
| |
References to the Build Encyclopedia overview was incorrect and regex value were referencing wrong groups.
--
MOS_MIGRATED_REVID=139073937
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138974884
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
https://be.bazel.build/c-cpp/cc_binary will now redirect to the cc_binary rules, as well as https://be.bazel.build/c-cpp#cc_binary
https://be.bazel.build will now redirect to the documentation index
https://cr.bazel.build will now redirect to the gerrit dashboard
https://cr.bazel.build/42 will now redirect to the gerrit code review 42
--
MOS_MIGRATED_REVID=138904300
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Change the installation instructions to be compatible with
the upcoming distribution artifact change. For compiling from
source, we recommend two ways,
- using the distribution archive and calling ./compile.sh, and
- using a bootstrap version of bazel already installed and calling
bazel build //src:bazel.
The third way, of having the precise version of protoc needed already
installed is still possible but not recommended as it is very fragile.
So do not mention it.
--
Change-Id: I2f41913b37bcb0058a28e6b49c496611ae4b1908
Reviewed-on: https://bazel-review.googlesource.com/#/c/7132
MOS_MIGRATED_REVID=138871245
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138822436
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138752213
|
|
|
|
| |
MOS_MIGRATED_REVID=138643916
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138636874
|
|
|
|
|
|
|
| |
Add doc for the "read only" error message.
--
MOS_MIGRATED_REVID=138194709
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138184866
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138054554
|
|
|
|
|
|
|
|
|
|
|
|
| |
This
- makes the `tools/*.ps1` generation more sane
- supports generating a package for RCs
Closes #2005.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/2005
MOS_MIGRATED_REVID=138052483
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138003998
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137981481
|
|
|
|
|
|
|
|
|
|
| |
Make it explicit that the user only needs VC++
with Windows SDK.
Fixes https://github.com/bazelbuild/bazel/issues/1564
--
MOS_MIGRATED_REVID=137709665
|
|
|
|
|
|
|
|
|
|
|
|
| |
The C++ client now talks to the Java server through protobuf messages
using the RPC mechanism provided by grpc, so this AF_UNIX socket file is
not used anymore for the communication between them since commit
a3c4833dc24b: ("Remove support for using AF_UNIX...").
--
Change-Id: Ic71e4c65ebb6bb2e661128635c2440007feaf5f6
Reviewed-on: https://bazel-review.googlesource.com/#/c/7030/
MOS_MIGRATED_REVID=137679905
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137500893
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137494506
|
|
|
|
|
|
|
|
|
| |
example.
RELNOTES:none
--
MOS_MIGRATED_REVID=137369185
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137293859
|
|
|
|
|
|
|
| |
--
Change-Id: I218ae41da9a139ac1a613e0fcef0adf062845ef5
Reviewed-on: https://bazel-review.googlesource.com/6891
MOS_MIGRATED_REVID=137193672
|
|
|
|
|
|
|
|
|
|
| |
- Add debugging tips
- Give more visibility to tools/build_defs/g3doc/
- Mention Standalone Skylark
- Remove some mentions of build extensions
--
MOS_MIGRATED_REVID=137175010
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137128701
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137004410
|
|
|
|
|
|
|
|
|
|
|
|
| |
Release 0.0.2 is too old and doesn't work any more.
I'll make the same change in the tutorial repo.
Closes #1962.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/1962
MOS_MIGRATED_REVID=136825134
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=136666421
|
|
|
|
|
|
|
|
| |
Closes #1938.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/1938
MOS_MIGRATED_REVID=136603317
|
|
|
|
|
|
|
|
|
| |
#1943
--
Change-Id: Ic7b4378acb4d3661a1b61ff887c9cc8592df9f7e
Reviewed-on: https://bazel-review.googlesource.com/c/6131/
MOS_MIGRATED_REVID=136154990
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With bazel sources depending on checked-in binaries for the
supported platforms, porting bazel to a new platform is hard;
that approach also doesn't scale well if we want to support
users on more platforms.
This design document suggests an alternative approach based
on creating a zip-archive that, besides all sources, also
contains the generated output of the protoc actions. From
this archive, bazel can be bootstrapped without depending
on the right protoc on the target platform.
--
Change-Id: I401452435ed4189ea95260961d981ccc99a98560
Reviewed-on: https://bazel-review.googlesource.com/#/c/6530
MOS_MIGRATED_REVID=135891242
|
|
|
|
|
|
|
|
|
|
|
| |
And refer it from the various release pages.
Also:
- Adds the sig file to the release candidate page
- Fix a typo
--
MOS_MIGRATED_REVID=135793241
|
|
|
|
|
|
|
| |
As discovered in #1919.
--
MOS_MIGRATED_REVID=135677514
|
|
|
|
|
|
|
|
| |
Closes #1915.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/1915
MOS_MIGRATED_REVID=135676413
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=135474033
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=135472917
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=135382903
|
|
|
|
|
|
|
|
|
|
|
| |
- Instead of a script for freezing the client environment, an info key was added.
- Mark as implemented.
--
Change-Id: I1928031bbe535fef2ffdedba4485fa9a37f4c1ec
Reviewed-on: https://bazel-review.googlesource.com/#/c/6494
MOS_MIGRATED_REVID=135356539
|
|
|
|
|
|
|
| |
--
Change-Id: I12cc96ee23e5a35d197e867813dfcedf3620b536
Reviewed-on: https://bazel-review.googlesource.com/#/c/6339
MOS_MIGRATED_REVID=134773226
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Roll-forward with appropriate fixes: --action_env is a "build" option,
not a "common" option. Moreover, also inherit the corresponding variables
for tests from the effective action environment.
Also fix the corresponding error in the design document.
*** Original change description ***
Automated [] rollback of commit 96d46280bc5a4803ba2242a4ad16939f85a3b212.
*** Reason for rollback ***
Broke installation on latest release.
Fixes #1846
*** Original change description ***
Reintroduce .bazelrc and set --action_env defaults
Shipping a .bazelrc was removed in 009b48bcfaf4ebb17f9ab03bea9036cfa3c12ff0.
However, as per our "Specifying environment variables for actions" design
document, we want to ship a global rc file specifying the common environment
variables to be inherited. So revert that change and add the desired entries
to the global bazelrc file we're shipping.
***
--
MOS_MIGRATED_REVID=134769063
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. Throw an error if Bash-on-Windows is found instead of MSYS bash
2. Introduce BAZEL_VS environment variable
3. Output more information
Fix https://github.com/bazelbuild/bazel/issues/1847
--
Change-Id: Ic4571c6c792d9b81df4cd800b8f19d121cc44c33
Reviewed-on: https://bazel-review.googlesource.com/#/c/6330
MOS_MIGRATED_REVID=134531295
|
|
|
|
|
|
|
| |
--
Change-Id: I699d605b3dc923a60516d70dc5d0144a9be49b0b
Reviewed-on: https://bazel-review.googlesource.com/#/c/6310/1
MOS_MIGRATED_REVID=134466041
|
|
|
|
|
|
|
|
|
| |
This entails adding a read-locking mechanism to Mutability contexts.
RELNOTES[INC]: Updating list/dicts while they are being looped over is not allowed. Use an explicit copy if needed ("for x in list(mylist):").
--
MOS_MIGRATED_REVID=134442701
|
|
|
|
|
|
| |
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/1742
MOS_MIGRATED_REVID=134283632
|
|
|
|
|
|
|
| |
Fixes https://github.com/bazelbuild/bazel/issues/1786
--
MOS_MIGRATED_REVID=134271340
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=133959741
|