| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
This a first step toward supporting platform that does not requires
to generate released artifacts.
--
MOS_MIGRATED_REVID=102999025
|
|
|
|
|
|
|
| |
Fixes #440
--
MOS_MIGRATED_REVID=102739492
|
|
|
|
|
|
|
|
|
|
|
| |
github-release actually takes a glob, not a list of file and tmpdir
was not global so because errexit was set it leads to the job failing.
Tested by simulating a release environment on my machine but we cannot
fully test it until the next release.
--
MOS_MIGRATED_REVID=102642172
|
|
|
|
| |
MOS_MIGRATED_REVID=102637361
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102567966
|
|
|
|
|
|
|
|
|
| |
android_{ndk,sdk}_repository rules themselves.
This is to that the Android tests also work on OS X (otherwise, we'd end up creating a file called "BUILD" in its root, which doesn't work, because it already has a directory called "build")
--
MOS_MIGRATED_REVID=102484286
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102343488
|
|
|
|
|
|
|
|
| |
This will make the user experience a bit nicer as it should make
the first run of bazel faster.
--
MOS_MIGRATED_REVID=102338873
|
|
|
|
|
|
|
| |
How comes this is ok on linux???
--
MOS_MIGRATED_REVID=102338200
|
|
|
|
|
|
|
| |
Without those check, a wrong call can wipe unwanted stuff
--
MOS_MIGRATED_REVID=102337203
|
|
|
|
|
|
|
|
|
|
|
|
| |
With this script, the easiest way to run the test suite is now:
bash -c "export ANDROID_SDK_PATH=$HOME/bin/android-sdk-linux; \
export ANDROID_NDK_PATH=$HOME/bin/android-ndk-r10e; \
source ./scripts/ci/build.sh; \
bazel_build output/ci"
--
MOS_MIGRATED_REVID=102334239
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102124504
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102022958
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101960679
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101929112
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101926016
|
|
|
|
|
|
|
|
| |
This file is a dummy and cannot be extracted from the Bazel workspace
so create it.
--
MOS_MIGRATED_REVID=101925956
|
|
|
|
|
|
|
|
|
|
| |
fmt behaves totally differently depending on the version and on the
OS, use fold instead that has a consistent behaviour accross platform.
Tested with bazel test //scripts/release/... on OSX and Linux.
--
MOS_MIGRATED_REVID=101567574
|
|
|
|
|
|
|
| |
--
Change-Id: I4e65cc583e758d2f7e45209ffcb37f6a871e2ed7
Reviewed-on: https://bazel-review.git.corp.google.com/#/c/1840
MOS_MIGRATED_REVID=101462155
|
|
|
|
|
|
|
|
|
|
|
|
| |
use non-declared inputs) and safety (spawns can no longer affect the host system, e.g. accidentally wipe your home directory). This implementation works on Linux only and uses Linux containers ("namespaces").
The strategy works with all actions that Bazel supports (C++ / Java compilation, genrules, test execution, Skylark-based rules, ...) and in tests, Bazel could successfully bootstrap itself and pass the whole test suite using sandboxed execution.
This is not the default behavior yet, but can be activated explicitly by using:
bazel build --genrule_strategy=sandboxed --spawn_strategy=sandboxed //my:stuff
--
MOS_MIGRATED_REVID=101457297
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
that Bazel finds Android tools and update the tools themselves to handle their new location.
This paves the way for eventually referencing every tool this way.
We have to figure out if android_http_tools_repository is the right way to distribute the Android tools, but now that we don't have a binary distribution yet, it's not an immediate problem.
This will break existing users of Android support in Bazel, whom I'll inform over bazel-discuss.
Fixes #384.
--
MOS_MIGRATED_REVID=101456190
|
|
|
|
|
|
|
| |
It rotted somewhere along the way and tried to build Objective C tools on Linux, and unsurprisingly, failing.
--
MOS_MIGRATED_REVID=101445358
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=100915378
|
|
|
|
|
|
|
|
| |
Moving it to scripts/ci let that unchanged and that results in an error
in the CI system.
--
MOS_MIGRATED_REVID=100825881
|
|
|
|
|
|
|
| |
--
Change-Id: I424db210611f94b986eda872626a97415221fcea
Reviewed-on: https://bazel-review.googlesource.com/1800
MOS_MIGRATED_REVID=100806076
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It provides method to build, package and deploy artifacts, as
well as constructing announcement mails:
- bazel_build build bazel with the good label, execute the tests,
build the packages and copy the artifacts into a release directory.
- bazel_release deploy the relase to GCS and Github and send an
announcement mail.
--
Change-Id: I68f5a600c0718fac5fa12423d1cb8e0cc86728b5
Reviewed-on: https://bazel-review.googlesource.com/#/c/1811
MOS_MIGRATED_REVID=100805636
|
|
|
|
|
|
|
| |
--
Change-Id: Ia70ca1b8482e10bc1ac91799aa238f8613e5c824
Reviewed-on: https://bazel-review.googlesource.com/#/c/1801
MOS_MIGRATED_REVID=100476467
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
exec(3) under mingw converts every command line argument that looks like Unix path
into Windows path when executing non-mingw images (criteria for non-mingw image is
that the image does not depend on msys-<version>.dll). This affects bazel labels
(`//foo:bar` becomes `/foo:bar` for example).
This CL:
1) Replaces usage of execv(3) with Windows-native CreateProcess.
2) Converts all command line arguments that are indeed paths into Windows paths.
--
MOS_MIGRATED_REVID=100386350
|
|
|
|
|
|
|
| |
Fixes #341
--
MOS_MIGRATED_REVID=99458831
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=99383290
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Those scripts are made to handle the soon to be Bazel
release process. It is still missing the CI part that
deploys built artifacts and sends announcement mails.
It uses the RELNOTES: tag (RELNOTES for a simple change,
RELNOTES[NEW] for a new feature, RELNOTES[INC] for an
incompatible change) to create the CHANGELOG.md file.
The main entry point is scripts/release/release.sh
and should be the only script called directly.
--
Change-Id: I6e066fda4d862ce793cc03dc8bdf0b8cb34f7c2c
Reviewed-on: https://bazel-review.googlesource.com/#/c/1580/
MOS_MIGRATED_REVID=99282250
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
Also removed tools/jdk/jdk check (as it's not created anymore) added dash to the excluded dirs.
Fixes #295.
--
MOS_MIGRATED_REVID=99175421
|
|
|
|
|
|
|
|
|
|
|
| |
For some strange reason fmt do not try to fill the line by default
under GNU/Linux. This is using a wrapper around fmt to fix
//scripts/release:relnotes_test on Linux.
Fixes #331.
--
MOS_MIGRATED_REVID=99165254
|
|
|
|
|
|
|
|
|
|
| |
Progress messages here mostly consist of package loading messages that aren't
very interesting in this context.
--
Change-Id: Ifee2ce5979ea47eb06cff199670fc5ed2218c139
Reviewed-on: https://bazel-review.googlesource.com/#/c/1730/
MOS_MIGRATED_REVID=99163320
|
|
|
|
|
|
|
|
|
|
|
|
| |
This script uses the RELNOTES: tag (RELNOTES for a
simple change, RELNOTES[NEW] for a new feature,
RELNOTES[INC] for an incompatible change) to create
the CHANGELOG.md file.
--
Change-Id: If457a0a85f4a9ceddf822393d0aeb8b60c54136b
Reviewed-on: https://bazel-review.googlesource.com/#/c/1583/
MOS_MIGRATED_REVID=99020942
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=99015580
|
|
|
|
|
|
|
|
|
| |
Ordering of message were confusing if the zip step was failing.
Fixes #319
--
MOS_MIGRATED_REVID=98932569
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=98815600
|
|
|
|
|
|
|
| |
src/tools/android/java/com/google/devtools/build/android:android_builder_lib to depend on src/main/java:options.
--
MOS_MIGRATED_REVID=98772591
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is just based on what I had to do to get IntelliJ working with
Bazel at head, but I think it makes things simpler as well.
Main changes:
* External jars are supported (I think);
* Protobufs are imported en masse via a "directory" module library;
* We now include all Android files unless it looks like we won't be
able to compile them.
--
Change-Id: Ib2ce59f6636f0d262b05f89d57837d7018a0fbfc
Reviewed-on: https://bazel-review.googlesource.com/1611
MOS_MIGRATED_REVID=98118522
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
As a drive-by fix, add correct deps to //src/test/java:skylarkshell . Why don't we build that in our tests?
--
MOS_MIGRATED_REVID=97404777
|
|
|
|
|
|
|
| |
Fixes #272
--
MOS_MIGRATED_REVID=97402007
|
|
|
|
|
|
|
| |
This fixes #267 to some degree. An update to the tools/ directory will still be required.
--
MOS_MIGRATED_REVID=97228079
|
|
|
|
|
|
|
|
|
|
| |
Also give advice for some changes to make to the script depending on the
environment and events triggering the script.
--
Change-Id: Ic230d96c29785c8df392b72fc4809eb7703fafff
Reviewed-on: https://bazel-review.googlesource.com/#/c/1570/
MOS_MIGRATED_REVID=97118314
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This script looks at the files changed in git against origin/master and
queries for all build and test targets associated with those files.
Running this script on a CI server should allow you to only test the
things that have changed since the last time your merged.
--
Change-Id: I30d33e21eff370b795e1055c7150906f2a6782cd
Reviewed-on: https://bazel-review.googlesource.com/#/c/1470
MOS_MIGRATED_REVID=96849243
|
|
|
|
|
|
|
| |
Also made it print the output for the problem command to make debugging easier.
--
MOS_MIGRATED_REVID=96783685
|
|
|
|
|
|
|
| |
And get rid of usage of "blazerc" flags in our scripts.
--
MOS_MIGRATED_REVID=96776423
|