| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
RELNOTES: Add instrumented file provider support to Skylark rules.
--
MOS_MIGRATED_REVID=114255963
|
|
|
|
|
|
|
| |
workspace file in the repo.
--
MOS_MIGRATED_REVID=113822978
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Issue that caused the rollback (#819) is resolved
*** Original change description ***
Automated [] rollback of [].
*** Reason for rollback ***
Prerequisite for rolling back j2objc base workspace change
*** Original change description ***
Remove base_workspace from bazel setup
I also removed a couple places the documentation referred to it incorrectly.
There are still a couple of blog posts that mention it, but that seemed okay.
RELNOTES: A bazelrc with --package_path set is no longer required for Bazel to
find its tools. This also means that building //......
--
MOS_MIGRATED_REVID=113259357
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is to avoid confusion between rule(), which declares a new build
rules, and native.rule(), which can only be used in macros to inspect
the BUILD file processed so far.
native.{rule,rules} is maintained and marked deprecated to smooth the
transition for early adopters.
--
MOS_MIGRATED_REVID=113250194
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Prerequisite for rolling back j2objc base workspace change
*** Original change description ***
Remove base_workspace from bazel setup
I also removed a couple places the documentation referred to it incorrectly.
There are still a couple of blog posts that mention it, but that seemed okay.
RELNOTES: A bazelrc with --package_path set is no longer required for Bazel to
find its tools. This also means that building //... should work to build
everything in the workspace without including Bazel's own targets.
--
MOS_MIGRATED_REVID=113164089
|
|
|
|
|
|
|
| |
I thought Jekyll would translate these, but apparently not?
--
MOS_MIGRATED_REVID=112977415
|
|
|
|
|
|
|
|
| |
Apropos issue #776. This hint in the doc would have saved me from filing a bogus bug.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/778
MOS_MIGRATED_REVID=112972220
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112766331
|
|
|
|
|
|
|
|
|
|
|
|
| |
I also removed a couple places the documentation referred to it incorrectly.
There are still a couple of blog posts that mention it, but that seemed okay.
RELNOTES: A bazelrc with --package_path set is no longer required for Bazel to
find its tools. This also means that building //... should work to build
everything in the workspace without including Bazel's own targets.
--
MOS_MIGRATED_REVID=112604261
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112598805
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112573386
|
|
|
|
|
|
|
| |
Fixes #790
--
MOS_MIGRATED_REVID=112563137
|
|
|
|
|
|
|
|
| |
Because `appengine_war` is not defined by default, `bazel build` fails unless loading. It would be nice to add the code to load the rule in the tutorial.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/794
MOS_MIGRATED_REVID=112415835
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
rule.
Add native.rules(), which returns all previously defined rules.
These primitives can be used to write Skylark extensions that aggregate over the contents of a BUILD file, eg.
def instantiate_if_needed(name):
n = name + "_wrapped"
if not native.rule(n):
py_test(name = n , ... )
def archive_cc_src_files(tag):
all_src = []
for r in native.rules().values():
if tag in r["tags"] and r["kind"] == "cc_library":
all_src.append(r["srcs"])
native.genrule(cmd = "zip $@ $^", srcs = all_src, outs = ["out.zip"])
RELNOTES: Support aggregation over existing rules in Skylark extensions
through native.rules and native.rule.
--
MOS_MIGRATED_REVID=112249050
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112248853
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112231484
|
|
|
|
|
|
|
| |
It isn't necessary anymore.
--
MOS_MIGRATED_REVID=112132272
|
|
|
|
|
|
|
|
| |
See https://groups.google.com/forum/#!topic/bazel-discuss/xPe-oaqWZ6s
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/787
MOS_MIGRATED_REVID=112129205
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112099756
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112039216
|
|
|
|
|
|
| |
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/764
MOS_MIGRATED_REVID=111832176
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=111607647
|
|
|
|
|
|
|
|
|
| |
threads!
Fixes #748
--
MOS_MIGRATED_REVID=111468883
|
|
|
|
|
|
|
| |
to aid in diagnosing issue #748.
--
MOS_MIGRATED_REVID=111360258
|
|
|
|
|
|
|
|
|
|
|
|
| |
This was originally written before sandboxing was enabled and I didn't notice
that src/ contained a header.
I've also removed the -Iexternal/gtest lines, since they're no longer needed.
Fixes #734.
--
MOS_MIGRATED_REVID=110790783
|
|
|
|
|
|
|
| |
Fixes #587.
--
MOS_MIGRATED_REVID=110785300
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110770240
|
|
|
|
|
|
|
| |
targets.
--
MOS_MIGRATED_REVID=110275427
|
|
|
|
|
|
|
|
| |
I got the "command not found" error for add-apt-repository on a clean Ubuntu installation and I think that the docs can be friendlier if they specify this :)
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/691
MOS_MIGRATED_REVID=110062139
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=109881691
|
|
|
|
|
|
|
|
|
|
| |
- Add mitigation of the common problem to the documentation
- Add indication on how to activate sandboxing on some machine (GKE nodes for example)
Fixes #433
--
MOS_MIGRATED_REVID=109879921
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In particular:
- Separate the implementation of maven_server into a RepositoryFunction and one that creates the MavenServerValue (ideally, maven_server wouldn't exist but we'll have to make to for the time being)
- Refactor the logic of determining whether an external repository needs to be re-fetched to RepositoryDelegatorFunction
- Make RepositoryFunctions not be SkyFunctions anymore (they are called from RepositoryDelegatorFunction, though, who *is* a SkyFunction)
- Add a Skyframe dirtiness checker that makes --nofetch RepositoryValues not be cached
- Add a bunch of test cases and javadoc
There is only one wart that I know of that remains: changes to BUILD files of new_* repository rules that weren't refetched when their RepositoryValue was initiall created on server restart won't take effect. This is because we don't add those BUILD files to the created RepositoryValue. This will fix itself once the ExternalFilesHelper refactoring is submitted.
--
MOS_MIGRATED_REVID=109768345
|
|
|
|
|
|
|
| |
target patterns and are thus neither built nor tested by invocations like "blaze test //my/project/..."
--
MOS_MIGRATED_REVID=109251573
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108717933
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108347869
|
|
|
|
|
|
|
|
|
| |
target pattern.
Apart from the tests, I also tested this manually running "bazel query //..." in a tree with convenience symlinks.
--
MOS_MIGRATED_REVID=108325454
|
|
|
|
|
|
|
|
|
|
| |
I filed #546 because I didn't notice --host_crosstool_top does what I
want.
--
Change-Id: Ib219753ad69c3026f1aa6d1889a0e7fac4449b2b
Reviewed-on: https://bazel-review.googlesource.com/#/c/2261/
MOS_MIGRATED_REVID=108267036
|
|
|
|
|
|
|
| |
Also, fix said documentation.
--
MOS_MIGRATED_REVID=108247791
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108145081
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=107957505
|
|
|
|
|
|
|
|
|
| |
As mentioned in mailing list: https://groups.google.com/forum/#!msg/bazel-discuss/Lmmny9foXW0/_tf2ti8KCAAJ
--
Change-Id: I8ec654b3cb8a5df28113d1136c511334c1ea99e9
Reviewed-on: https://bazel-review.googlesource.com/#/c/2340/
MOS_MIGRATED_REVID=107923683
|
|
|
|
|
|
|
|
|
| |
through to the JVM instead of (almost certainly incorrectly) splitting the options along spaces.
This allows us to pass non-quote-delimited strings to the JVM, which is necessary for things like -XX:OnOutOfMemoryError="kill -3 %p" (normally bash strips those quotes, but they're not stripped when passed via --host_jvm_args).
--
MOS_MIGRATED_REVID=107820087
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
"DONT_FOLLOW_SYMLINKS_WHEN_TRAVERSING_THIS_DIRECTORY_VIA_A_RECURSIVE_TARGET_PATTERN" will *not* be traversed for transitive target patterns. The motivation here is to allow directories that intentionally contain wonky symlinks (e.g. foo/bar -> foo) to opt out of being consumed by Blaze. For example, given
<workspace>/foo
bar
bad -> .
DONT_FOLLOW_SYMLINKS_WHEN_TRAVERSING_THIS_DIRECTORY_VIA_A_RECURSIVE_TARGET_PATTERN
the 'bad' symlink will *not* be traversed by the pattern '//foo/...'.
--
MOS_MIGRATED_REVID=107738930
|
|
|
|
|
|
|
|
| |
Ubuntu 14.10 has reached end-of-life for several
months now.
--
MOS_MIGRATED_REVID=107473533
|
|
|
|
|
|
|
|
|
| |
bazel-discuss group, not the contribution instructions.
RELNOTES:
--
MOS_MIGRATED_REVID=106995833
|
|
|
|
|
|
|
| |
Fixes #529
--
MOS_MIGRATED_REVID=106883457
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
previous commit
Document and test how rules can run without the sandbox.
The only documentation about usable tags values was in a weird place,
along with duplicated information about flaky tests.
--
Change-Id: Ib98a0a5c582890512161ecf9f5d89c8e78d9ad68
Reviewed-on: https://bazel-review.googlesource.com/#/c/2220
MOS_MIGRATED_REVID=106858070
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106092764
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=105952522
|
|
|
|
| |
MOS_MIGRATED_REVID=105884504
|