| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change implements a remote worker that executes work (build or test).
Bazel will be a client of the remote worker. The communication uses gRPC
and Netty as transport.
A single remote worker has little advantage over running locally. Additional
infrastructure is needed to run workers on multiple machines and distributing
the work among them.
This change provides the basic building blocks for a distributed build farm.
(Mainly reformatting changes compared to https://bazel-review.googlesource.com/3110, some BUILD file changes.)
--
Change-Id: If7d285444ef42a6823b59443af17b61b04b9ce6a
Reviewed-on: https://bazel-review.googlesource.com/#/c/3110/
MOS_MIGRATED_REVID=122376861
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The simple replacement scripts for for build-runfiles and
process-wrapper do not use any bash-specific feature. Hence
we can make then scripts for /bin/sh which has the advatange
that that path is POSIX mandated, wheras bash could be installed
anywhere on the system.
--
Change-Id: I933d04be89e3c9ffc5673d8778b4754782cc4bdd
Reviewed-on: https://bazel-review.googlesource.com/#/c/3601
MOS_MIGRATED_REVID=122046251
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=122031687
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
local instance of bazel.io site.
* Add a new genrule rule that runs the new jekyll-tree.sh to do the following:
* Combine the generated docs for the Build Encyclopedia and Skylark Library
with the static site docs
* Combine the README.md files for the Docker and Packaging rules with the
Jekyll tree
* Process the generated docs, replaces instances of "blaze" with "bazel",
etc.
* Add scripts/serve-docs.sh script that can be used to bring up a local
instance of the bazel.io website.
As of this patch, it is possible to construct the full Bazel.io site tree from
the master branch.
--
MOS_MIGRATED_REVID=121813688
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously we were not removing a potential existing symlink.
If this is a directory then the rm will fail, leading to
a failure of the installer, whereas we would create a
wrong symlink with the previous code.
Fixes #1219.
--
MOS_MIGRATED_REVID=121262370
|
|
|
|
|
|
|
|
|
|
| |
RELNOTES: Bazel's workspace name is now io_bazel. If you are using Bazel's
source as an external repository, then you may want to update the name you're
referring to it as or you'll begin seeing warnings about name mismatches in your
code.
--
MOS_MIGRATED_REVID=120926179
|
|
|
|
|
|
|
|
| |
Fixing uncovered issues takes longer than expected: diabling tests to
reduce CI noise.
--
MOS_MIGRATED_REVID=120898842
|
|
|
|
|
|
|
|
|
| |
Fixes #1187.
--
Change-Id: I36e87d86926a38785dcd98c841db826c518cc575
Reviewed-on: https://bazel-review.googlesource.com/3463
MOS_MIGRATED_REVID=120710112
|
|
|
|
|
|
|
| |
Helps with #1182.
--
MOS_MIGRATED_REVID=120695171
|
|
|
|
|
|
|
| |
Helps with #1182.
--
MOS_MIGRATED_REVID=120686181
|
|
|
|
|
|
|
|
| |
I was confused about the bulleted list on 0.2.2, so I figured it
would be nice tell people what the commit list is.
--
MOS_MIGRATED_REVID=120577721
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120574676
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120545193
|
|
|
|
|
|
|
| |
9e4c78fb5752fa554db82815f7336255831a95ab
--
MOS_MIGRATED_REVID=120540000
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
commit 790d2f6009d47fe92cf0cd92a1473bbf0141f32e.
*** Reason for rollback ***
Broke non-Bazel projects on ci.bazel.io
Fixes #1168
*** Original change description ***
Move the runfiles for external repositories to under the x.runfiles/ directory
This also sets the Bazel workspace name to io_bazel_source.
Fixes #848.
Relevant to #1116, #1124,
RELNOTES[INC]: All repositories are now directly under the x.runfiles directory in the runfiles tree (previously, external repositories were at x.runfiles/main-repo/external/other-repo. This simplifies handling remote repository runfiles considerably, but will break existing references to external repository runfiles....
***
--
MOS_MIGRATED_REVID=120535721
|
|
|
|
|
|
|
|
| |
Once and for all, I tested it and re-tested should
be good.
--
MOS_MIGRATED_REVID=120381352
|
|
|
|
|
|
|
| |
I properly tested it this time.
--
MOS_MIGRATED_REVID=120339101
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Along the path, fix the build for JDK 7 and get rid of
most ugliness in the JDK 7 build. Now simply setting
JAVA_VERSION to 1.7 will build a JDK 7 compatible version.
Fixes #1159.
--
Change-Id: I9599283844a57d9e053f12d37445907f22a9232e
Reviewed-on: https://bazel-review.googlesource.com/#/c/3452
MOS_MIGRATED_REVID=120332747
|
|
|
|
|
|
|
| |
This test is now failing on ci.bazel.io
--
MOS_MIGRATED_REVID=120328587
|
|
|
|
|
|
|
| |
--
Change-Id: I5377f694bd6dc426d41feef75cd35145c3b47c2f
Reviewed-on: https://bazel-review.googlesource.com/#/c/3450/
MOS_MIGRATED_REVID=120323262
|
|
|
|
|
|
|
|
|
|
|
| |
This avoids problems when some of the universe doesn't build, and should
make the IDE setup script a bit faster. Also use --keep_going in query
so that any future breakages don't break IDE setup.
--
Change-Id: If9bf30ca5d63f9d9a3455cbbb78b7139a3e5324d
Reviewed-on: https://bazel-review.googlesource.com/3430
MOS_MIGRATED_REVID=120250626
|
|
|
|
|
|
|
| |
--
Change-Id: I6a2f9026fda578905ccb72b317223eaca16b882b
Reviewed-on: https://bazel-review.googlesource.com/#/c/3440
MOS_MIGRATED_REVID=120228541
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This also sets the Bazel workspace name to io_bazel_source.
Fixes #848.
Relevant to #1116, #1124,
RELNOTES[INC]: All repositories are now directly under the x.runfiles directory in the runfiles tree (previously, external repositories were at x.runfiles/main-repo/external/other-repo. This simplifies handling remote repository runfiles considerably, but will break existing references to external repository runfiles.
---
Furthermore, if a Bazel project does not provide a workspace name in the WORKSPACE file, Bazel will now default to using __main__ as the workspace name (instead of "", as previously). The repository's runfiles will appear under x.runfiles/__main__/.
--
MOS_MIGRATED_REVID=120224534
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change disables --java_langtools, --javabuilder_top, --singlejar_top,
--genclass_top, and --ijar_top, and finishes replacing them with
java_toolchain.{javac,javabuilder,singlejar,genclass,ijar}.
RELNOTES: Replace --java_langtools, --javabuilder_top, --singlejar_top,
--genclass_top, and --ijar_top with
java_toolchain.{javac,javabuilder,singlejar,genclass,ijar}
--
MOS_MIGRATED_REVID=120154954
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Note that the presence of server/grpc_port does not guarantee that the server actually listens to it and we can't guarantee it, either, because it can always be kill -9'd.
I haven't decided yet how the transition between AF_UNIX and gRPC will work. For now, I'm happy that we can start up a Java server.
The way to get the kernel-chosen port is truly awful, but it is apparently impossible to do so in a different way:
https://github.com/grpc/grpc-java/issues/72
--
MOS_MIGRATED_REVID=119828354
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks ci.bazel.io
While the basics for fixing the build is easy (just a few typos in packages building), fixing the test is a bit more tricky. I see only one solution for fixing the test: use a select statement that would select the good bazel version but that would always pull JavaBuilder as an external dependency when we do test.
Better roll this back then check the JavaBuilder 0.1.0 as a binary in third_party before rolling forward (a similar change is still needed to decouple running the test and building the binary for JDK 7)
*** Original change description ***
Refactor build for JDK 7
Now the JDK 7 tuning happens all in Bazel, removing logic
from the CI script. It uses remote repositories to access
JDK 7 dependencies.
--
MOS_MIGRATED_REVID=119773123
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
src/main/java/com/google/devtools/build/lib/exec/SymlinkTreeHelper.java:
enable --windows_compatible flag on Windows to make build-runfiles.exe work.
scritps/bootstrap/compile.sh:
--windows_compatible will also be passed to a dummy build-runfiles.exe defined in complie.sh.
Which is actully a batch script, modify it to make it work.
-----
With the changes above, we are able to build bazel with bazel. But when you try to
run ./compile.sh compile /path/to/bazel again without clean up tmp directory, it will fail with
a permission deny error. The reason seems to be that you can't use build-runfile.exe to build the
same hard link twice, still trying to solve that.
--
Change-Id: I93340b1ba9fa415f6db963b106e264799e33ede3
Reviewed-on: https://bazel-review.googlesource.com/#/c/3334
MOS_MIGRATED_REVID=119751076
|
|
|
|
|
|
|
|
|
|
|
| |
Now the JDK 7 tuning happens all in Bazel, removing logic
from the CI script. It uses remote repositories to access
JDK 7 dependencies.
--
Change-Id: Iff590c6642ca5b2343aa15096f8fd837d1c80787
Reviewed-on: https://bazel-review.googlesource.com/#/c/3327
MOS_MIGRATED_REVID=119634530
|
|
|
|
|
|
|
| |
The code doesn't do anything yet and it's unused code for now. This change only serves to add all the necessary dependencies to BUILD files that gRPC needs.
--
MOS_MIGRATED_REVID=119628697
|
|
|
|
|
|
|
| |
Now that --package_path isn't needed, this script can be removed.
--
MOS_MIGRATED_REVID=117965624
|
|
|
|
|
|
|
| |
This was actually not breaking the build, just outputing an error
--
MOS_MIGRATED_REVID=117481375
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bazel expects to be told the width of the terminal; during
bootstrap, we do not have a good mechanism of determining it,
so we have to resort to a hard-coded value. However, 97 is a
not very well motivated value (and actually not a very useful
value either) which is hard to guess that this is a default value.
Resorting to Bazel's built-in default of 80 is only slightly
more useful, but, at least, it is easily recognizable as a default
value, as 80 is the width of the famous VT100, the standard punch
card, etc.
--
Change-Id: I62403ca37ee74a090067a5a4248028e3d624b7c6
Reviewed-on: https://bazel-review.googlesource.com/#/c/3082
MOS_MIGRATED_REVID=117346018
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For the process wrapper the value '-' has a special meaning
as file name to which stdout/stderr are to be redirected: do
not redirect. However, the simple shell script that serves
as process wrapper during the bootstrap phase was not aware
of this special meaning, resulting in loss of useful process
output, which is especially annoying during bootstrap. Fix this.
--
Change-Id: Ifcf84e9000d74dafc69b675f192c1fc1cce484e8
Reviewed-on: https://bazel-review.googlesource.com/#/c/3081
MOS_MIGRATED_REVID=117338558
|
|
|
|
|
|
|
|
|
|
|
| |
All Bazel should now contain the latest version with a date
modifier to ensure we can track all Bazel builds out there.
It is especially important for #1014.
--
Change-Id: I8d17d9e1660b104c2b8623d5a8a06d010d044ea7
Reviewed-on: https://bazel-review.googlesource.com/3070
MOS_MIGRATED_REVID=117120584
|
|
|
|
|
|
|
| |
Fixes #739.
--
MOS_MIGRATED_REVID=116257685
|
|
|
|
|
|
|
|
| |
This is a temporary workaround to enable the use
of a cc_configure() rules to auto-configure C++ toolchain.
--
MOS_MIGRATED_REVID=116140726
|
|
|
|
|
|
|
|
| |
This target include all non tests targets of Bazel to do integration tests of
bootstrapping.
--
MOS_MIGRATED_REVID=115830741
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rename run_silent to run and add a global VERBOSE variable that tunes
whether the run function prints its output or not.
This is for better debugging possibilities of Bazel's self-build, though
compile.sh remains silent as before and only displays the command's output
in case of an error.
--
MOS_MIGRATED_REVID=115599355
|
|
|
|
|
|
|
|
|
|
| |
As part of this, change atexit to receive the name of a function instead of
just a chunk of code. This way, we can also control the return value of
each individual atexit function and report it to the user, should these
routines fail when the program apparently succeeded.
--
MOS_MIGRATED_REVID=115575895
|
|
|
|
|
|
|
|
|
| |
explicitly create it.
Turns out, mktemp doesn't like being passed a non-existent directory.
--
MOS_MIGRATED_REVID=115454169
|
|
|
|
|
|
|
|
|
|
|
| |
It seems like the change introduced in pull request #785 does not
function universally. On some releases of Debian and Ubuntu, it looks
like packages are declared as providing java{7,8}-sdk.
Fixes #961.
--
MOS_MIGRATED_REVID=115338913
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix three issues, one cosmetic, with setup-intellij.sh: running bazel
query "deps(${target}, 1)" on generated java files with a visibility
specification was returning two targets, one of which was the
visibility. Filtering for rules fixes that.
Bazel uses the javac langtools in third_party/ in preference to the
SDK's, but that wasn't reflected in the order of dependencies in the
module. This requires a small hack, since the SDK should appear before
some other jars in the dependencies.
Finally, remove some apparently dead code related to ijar that was just
printing errors when the script was run.
--
Change-Id: Iba5ae5a46c720282d99f193cd098ea14cc5eef52
Reviewed-on: https://bazel-review.googlesource.com/2990
MOS_MIGRATED_REVID=115246698
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=115207057
|
|
|
|
|
|
|
|
|
| |
Jenkins setup is not done yet, but it appears doable.
Work towards #927.
--
MOS_MIGRATED_REVID=115059680
|
|
|
|
|
|
|
| |
This should fix the current ci.bazel.io breakage.
--
MOS_MIGRATED_REVID=114892993
|
|
|
|
|
|
|
| |
Needed for #276.
--
MOS_MIGRATED_REVID=114693711
|
|
|
|
|
|
|
|
|
| |
So that bazel can read it.
Fixes #894.
--
MOS_MIGRATED_REVID=114689351
|
|
|
|
|
|
|
| |
Fixes #887.
--
MOS_MIGRATED_REVID=114681512
|
|
|
|
|
|
|
|
| |
The recent change in the bootstrap process was causing a warning
about sandboxing not being activated.
--
MOS_MIGRATED_REVID=114106185
|
|
|
|
|
|
|
| |
--
Change-Id: Ideb2011d23da470276420afcc8b5a71f1470f391
Reviewed-on: https://bazel-review.googlesource.com/#/c/2771
MOS_MIGRATED_REVID=113639747
|