| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
| |
on Windows
--
Change-Id: I0048202b431ca05b88f67153389ca40c1542b1d5
Reviewed-on: https://bazel-review.googlesource.com/#/c/3371
MOS_MIGRATED_REVID=119861292
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** 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
|
|
|
|
|
|
|
|
|
|
|
| |
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 immmediate reason for this change is that we also need to add gRPC support to the proto rules, and we don't want to also support gRPC in a half-baked way.
This makes the Bazel binary much smaller and avoid giving false signals that we (for now) support protobuf compilation. The protobuf rules are only for compiling Bazel itself.
RELNOTES[INC]: Bazel does not embed protocol buffer-related rules anymore.
--
MOS_MIGRATED_REVID=119516246
|
|
|
|
|
|
|
|
| |
This target include all non tests targets of Bazel to do integration tests of
bootstrapping.
--
MOS_MIGRATED_REVID=115830741
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Quotation mark character is significant for Win32's CreateProcess.
It should always be properly escaped when occuring inside arguments.
We might devise a common solution in GenRule for that, but for now
this change fixes the only genrule we use that runs into this issue.
Needed for #276.
--
MOS_MIGRATED_REVID=114881441
|
|
|
|
|
|
|
|
|
|
| |
Instead bundle ijar's zipper binary so the skylark rules that depends on it
can use it from @bazel_tools.
A commit introducing windows config settings broke our appengine tutorial.
--
MOS_MIGRATED_REVID=114857080
|
|
|
|
|
|
|
| |
Needed for #276.
--
MOS_MIGRATED_REVID=114693711
|
|
|
|
|
|
|
|
| |
We might revisit what the default toolchain for Windows should be, but
this CL uses msys to simplify bootstrapping.
--
MOS_MIGRATED_REVID=113665255
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112027454
|
|
|
|
|
|
|
|
|
| |
modifications to remove deprecation warnings, to create deterministic apks (removes timestamps), and to make calling ApkBuilder more convenient.
RELNOTES: Timestamps within Android apks are removed to make apks deterministic.
--
MOS_MIGRATED_REVID=111890659
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Roll-forward with fix
*** Original change description ***
Automated [] rollback of [].
*** Reason for rollback ***
Broke tests on Mac: https://google.com/url?sa=D&q=http%3A%2F%2Fci.bazel.io%2Fjob%2FBazel%2FJAVA_VERSION%3D1.8%2CPLATFORM_NAME%3Ddarwin-x86_64%2F269%2Fconsole
*** Original change description ***
Speed-up bootstrap on OS X by removing tool compilation.
--
MOS_MIGRATED_REVID=111833617
|
|
|
|
|
|
|
| |
For bazel on non-darwin architectures, this will simply be a stub, and should never be invoked. On darwin arcitectures, the tool will map xcode version to xcode path on the host system.
--
MOS_MIGRATED_REVID=111651147
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Broke tests on Mac: https://google.com/url?sa=D&q=http%3A%2F%2Fci.bazel.io%2Fjob%2FBazel%2FJAVA_VERSION%3D1.8%2CPLATFORM_NAME%3Ddarwin-x86_64%2F269%2Fconsole
*** Original change description ***
Speed-up bootstrap on OS X by removing tool compilation.
--
MOS_MIGRATED_REVID=110785493
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110704529
|
|
|
|
|
|
|
|
|
| |
The code changes are mostly due to dslomov, not me, although I refactored
the Jvm class a bit based on his changes. I set dslomov as the author.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/688
MOS_MIGRATED_REVID=109536553
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=109305952
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108985661
|
|
|
|
|
|
|
|
|
| |
tools/jdk are not necessary anymore.
Fixes #508.
--
MOS_MIGRATED_REVID=108123264
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108029812
|
|
|
|
|
|
|
| |
The -X option removes UID/GID information from the zip file, which of course is non-hermetic. There is still some weirdness with install_base_key, but I couldn't figure out what that is: the files that are checksummed are always the same and they are in the same order.
--
MOS_MIGRATED_REVID=107484288
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106605250
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106493557
|
|
|
|
|
|
|
|
|
| |
This makes Android builds slightly faster and avoids the "Modification date is in the future" warnings by javac and removes the sources of devtools/common/options from the binary.
incrementaldeployment is not pre-compiled yet.
--
MOS_MIGRATED_REVID=106391321
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
repository:
http://ci.bazel.io/job/Tutorial/PLATFORM_NAME=linux-x86_64/65/console
The build files for options were refactored, which broke part of the hack that
assembles the default_android_tools repository, causing idlclass_lib to fail to build.
src/main/java/com/google/devtools/common/options/BUILD was added, and the idlclass_lib dependency was changed from //src/main/java:options to
//src/main/java/com/google/devtools/common/options, but the code that assembles the default_android_tools repository was only globbing the java sources, and added a build file to src/main/java, so idlclass_lib would look for the options at the deeper path, which didn't exist inside default_android_tools.
--
MOS_MIGRATED_REVID=106306493
|
|
|
|
|
|
|
|
|
| |
back to getpwuid())
Also a minor compatibility fix in a sed invocation.
--
MOS_MIGRATED_REVID=106291639
|
|
|
|
|
|
|
|
|
| |
embedded tools.
The previous change got the order of the parameters of package-bazel.sh wrong, thus building a non-functional bazel binary.
--
MOS_MIGRATED_REVID=105742752
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Broke bazel on mac
*** Original change description ***
Add a //src:bazel-notools target that is the same as the Bazel binary except without the embedded tools.
Its use requires the addition of a local_workspace(name = "bazel_tools", path=...) to the WORKSPACE file. It is useful if you don't care about the set of embedded tools (because you provide them to Bazel in another way anyway) but you do care about the size of the Bazel binary (it's 16 MB compared to 56 MB with the tools).
--
MOS_MIGRATED_REVID=105553886
|
|
|
|
|
|
|
|
|
| |
without the embedded tools.
Its use requires the addition of a local_workspace(name = "bazel_tools", path=...) to the WORKSPACE file. It is useful if you don't care about the set of embedded tools (because you provide them to Bazel in another way anyway) but you do care about the size of the Bazel binary (it's 16 MB compared to 56 MB with the tools).
--
MOS_MIGRATED_REVID=105499508
|
|
|
|
|
|
|
| |
This is currently unused deadweight, but will be used pretty soon to access the tools directory instead the menagerie of various odd mechanism we currently use.
--
MOS_MIGRATED_REVID=104737151
|
|
|
|
|
|
|
| |
BuildJar's JarHelper so that it too can be embedded.
--
MOS_MIGRATED_REVID=104539260
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Follow redirects when downloading files:
The github provided file lies after several redirect, giving a bad jars
(see http://ci.bazel.io/job/Bazel/JAVA_VERSION=1.7,PLATFORM_NAME=linux-x86_64/144/console).
- Remove building tools as part of the determinism tests:
With recent update, JavaBuilder can no longer be built with Java 7,
so we use a pre-built binary from version 0.1.0. However, the
determinism test was still using it as a point of comparison. Removing
tools from the determinism test prevent building JavaBuilder without
giving up on testing actual determinism (building Bazel already contains
all the edge-cases).
Tested with `bash -c 'export JAVA_VERSION=1.7; source scripts/ci/build.sh; bazel_build'`
--
MOS_MIGRATED_REVID=104480161
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change deprecate JDK 7 as JavaBuilder follow changes in Java 9
and might use Java 8 features. We will maintain a build with the
JDK 7 as long as possible but this build won't include updates
in JavaBuilder.
RELNOTES[INC]: Bazel requires JDK 8 to run.
--
MOS_MIGRATED_REVID=103069207
|
|
|
|
|
|
|
|
| |
Seems like a better location for it (easier for people to run than
src/main/java/com/google/devtools/build etc).
--
MOS_MIGRATED_REVID=102354250
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is not really nice, there are several hacks there. This
repository will get removed in the future and linked to a
remote one instead. I tested it against the tutorial and
it works like a charm. mobile-install seems like to work,
maybe that's also fixing the last issue reported in #392.
Known issue: Java compilation output errors about files being
modified in the future.
--
MOS_MIGRATED_REVID=102282979
|
|
|
|
|
|
|
| |
--
Change-Id: I4e65cc583e758d2f7e45209ffcb37f6a871e2ed7
Reviewed-on: https://bazel-review.git.corp.google.com/#/c/1840
MOS_MIGRATED_REVID=101462155
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This packager can be called by the release scripts to generate
a self-extractable bash installer for Bazel. This script was
tested by hand as extra arguments can be specified to change
the default install of Bazel (default is system-wide and
with the argument you can make a user install).
This will be the only packager for now since GitHub is offering
the possibility to download the source tree as a ZIP. Hopefully,
before the end of the year we could build some more package kind.
--
Change-Id: I1a2d0cd39b9e4adcaf6c984ec4c855a04213b61a
Reviewed-on: https://bazel-review.googlesource.com/1581
MOS_MIGRATED_REVID=99258828
|
|
|
|
|
|
|
| |
Adds a jar output to Java and Android rules which contains the class files for source files generated from Java annotation processors. For a java_binary foo, the jar will be foo-gen.jar, and for a java_library foo the jar will be libfoo-gen.jar, and similarly for Android. Also adds a binary serialized proto manifest file output to Java and Android rules which describes the contents of the output class jar of those rules, which is used to create the -gen.jar. See src/main/protobuf/java_compilation.proto.
--
MOS_MIGRATED_REVID=97793715
|
|
|
|
|
|
|
| |
Fixes #261.
--
MOS_MIGRATED_REVID=96967085
|
|
|
|
|
|
|
|
|
| |
Now that we are using the error-prone javac, there is no need
to impose Java 8. However, because some of our tests are targetting
Java 8, developer should still use a JDK 8 to tests.
--
MOS_MIGRATED_REVID=96400914
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now the blessed Bazel binary is self-hosted and correctly labeled.
All tools are also built using Bazel and labeled with the release.
At the end of the compilation, the output folder only host the
Bazel binary now. We use temporary folders to store the intermediate
artifacts.
Also integrated ./bootstrap_test.sh in compile.sh so there is only
one script for everything regarding bootstraping Bazel.
--
Change-Id: Idadbd075e7b8ecb6e306b919b7a73c647c5cfbae
Reviewed-on: https://bazel-review.googlesource.com/#/c/1460/
MOS_MIGRATED_REVID=95625880
|
|
|
|
|
|
|
| |
Fixes #211.
--
MOS_MIGRATED_REVID=94919859
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Using this change, changing the target and source version of
//tools/jdk:toolchain, and setting the Java Langtools
(--java_langtools) to a JDK 8 compliant tools.jar, Bazel can
target JDK 7.
A compliant tools.jar to compile with targeting JDK 7 can be found
at http://search.maven.org/#artifactdetails%7Ccom.google.errorprone%7Cjavac%7C1.9.0-dev-r2644-1%7Cjar
--
MOS_MIGRATED_REVID=94591419
|
|
|
|
|
|
|
|
|
|
|
| |
It is not necessary as we can depend directly on
//src/main/tools:namespace-sandbox, like we do for dependencies in this
file.
--
Change-Id: I20d2c082603d280caf30b056ad103ec6f129ebde
Reviewed-on: https://bazel-review.googlesource.com/1310
MOS_MIGRATED_REVID=93711825
|
|
|
|
|
|
|
|
|
| |
This script enable shell completion for Bazel inside the Bourne-again shell.
Fixes #38
--
MOS_MIGRATED_REVID=90745457
|
|
|
|
|
|
|
|
|
| |
It is a first batch of integration tests for Bazel. They tests some
basic behaviors and nominal cases of Bazel rules (especially they tests
the behavior of the examples provided in //examples).
--
MOS_MIGRATED_REVID=89440074
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=88742425
|
|
|
|
|
|
|
| |
This is needed for taking the runfiles prefix from the WORKSPACE file instead of hardcoding it.
--
MOS_MIGRATED_REVID=87347883
|
|
--
MOE_MIGRATED_REVID=85702957
|