| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
| |
Change-Id: I21c738873b2bc6b4d2e8b607e0a206589d905f86
PiperOrigin-RevId: 157271290
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 156107235
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 156102527
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 156068741
|
|
|
|
|
|
|
|
|
| |
ANDROID_SDK_API_LEVEL was previously set by a script that parsed that
platforms/ directory of the SDK. Now this functionality is handled by
android_sdk_repository which autodetects the available API levels.
Change-Id: Ifbbc5499444f465929b9d70bf488ff5ba3c4cded
PiperOrigin-RevId: 155747062
|
|
|
|
|
|
|
|
|
|
| |
Instead just mark it as a default installer when there is
no installer with a bundled JDK.
Fixes #2969
To be cherry-picked for #2692.
PiperOrigin-RevId: 155483548
|
|
|
|
|
|
| |
To be cherry-picked for #2692.
PiperOrigin-RevId: 155063394
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
that should not break CI this time...
- Make the default Bazel release artifacts include the bundled JDK.
- Create additional Bazel release artifacts without a bundled JDK.
Tested by running "bazel build //scripts/..." in a clean checkout and
one with this patch in, then diffing the entire bazel-out folder and
manually inspecting the resulting files (zips, tar.gz, deb, rpm) to make
sure that they contain the right files. Looks all good now, so let's try
again.
PiperOrigin-RevId: 154544164
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks CI because //scripts/packages/debian:bazel-bin still references //scripts/packages:bazel-real.
*** Original change description ***
Bundled JDK changes for the release process.
- Make the default Bazel release artifacts include the bundled JDK.
- Create additional Bazel release artifacts without a bundled JDK.
Change-Id: If87c986507ae8e7dbbf0e8f163dd0073a206b265
PiperOrigin-RevId: 154054435
|
|
|
|
|
|
|
|
| |
- Make the default Bazel release artifacts include the bundled JDK.
- Create additional Bazel release artifacts without a bundled JDK.
Change-Id: If87c986507ae8e7dbbf0e8f163dd0073a206b265
PiperOrigin-RevId: 153718827
|
|
|
|
| |
PiperOrigin-RevId: 151564075
|
|
|
|
|
|
|
|
| |
--
Change-Id: I044b8c244d63232ccec7bf48556248ee2dd1c43d
Reviewed-on: https://cr.bazel.build/9515
PiperOrigin-RevId: 151019006
MOS_MIGRATED_REVID=151019006
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We're using Azul Systems, Inc.'s ZuluĀ® OpenJDK build[1], as it's a good
vanilla build of OpenJDK available for our three most important
platforms:
zulu8.20.0.5-jdk8.0.121-linux_x64.tar.gz
zulu8.20.0.5-jdk8.0.121-macosx_x64.zip
zulu8.20.0.5-jdk8.0.121-win_x64.zip
You can build & run a Bazel binary with an embedded JDK by simple doing:
bazel build //src:bazel_with_jdk
bazel-bin/src/bazel_with_jdk info
The "bazel license" command prints the license of the embedded OpenJDK.
We mirror the binaries and sources of the OpenJDK used for bundling on
this website:
https://bazel-mirror.storage.googleapis.com/openjdk/index.html
RELNOTES: Bazel can now be built with a bundled version of the OpenJDK.
This makes it possible to use Bazel on systems without a JDK, or where
the installed JDK is too old.
[1] http://www.azul.com/downloads/zulu/
--
PiperOrigin-RevId: 150440467
MOS_MIGRATED_REVID=150440467
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 150194302
MOS_MIGRATED_REVID=150194302
|
|
|
|
|
|
|
|
|
|
|
| |
For test (a.k.a '[') the closing bracket has to be a separate argument.
Fix this by adding the missing space.
--
Change-Id: Ie1d64bc1fa37f85ee0c7b5520b2ba12a30c9f635
Reviewed-on: https://cr.bazel.build/9290
PiperOrigin-RevId: 149418360
MOS_MIGRATED_REVID=149418360
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Our distribution archive is supposed to contain all the original
sources, as well as derived architecture-independent files needed
for bootstrapping. So there should only be one distribution archive,
not a separate one for jdk7, especially, as the project is moving
away from java 7 soon. Change our artifact building accordingly.
Closes #2250.
--
Change-Id: If34afb544702bc309f722bdc2891b9dc60fe9899
Reviewed-on: https://cr.bazel.build/9190
PiperOrigin-RevId: 149104302
MOS_MIGRATED_REVID=149104302
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 148015085
MOS_MIGRATED_REVID=148015085
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 148010735
MOS_MIGRATED_REVID=148010735
|
|
|
|
|
|
|
|
| |
This will only affect site after adding new job calling this function on CI.
--
PiperOrigin-RevId: 147730290
MOS_MIGRATED_REVID=147730290
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 147612226
MOS_MIGRATED_REVID=147612226
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Fix CI build
*** Original change description ***
Automated [] rollback of commit 01aa7d6f177f3284b5fecc0397bf29a605b37df0.
*** Reason for rollback ***
Breaks the CI: http://ci.bazel.io/view/Bazel%20bootstrap%20and%20maintenance/job/Bazel/JAVA_VERSION=1.7,PLATFORM_NAME=linux-x86_64/1270/console
*** Original change description ***
Adds support for pushing sites that don't need build, and build benchmark site.
This should not affect CI for now.
--
PiperOrigin-RevId: 147572787
MOS_MIGRATED_REVID=147572787
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Follow-up for CI breakage.
*** Original change description ***
Fix bazel build on CI.
--
PiperOrigin-RevId: 147475894
MOS_MIGRATED_REVID=147475894
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks the CI: http://ci.bazel.io/view/Bazel%20bootstrap%20and%20maintenance/job/Bazel/JAVA_VERSION=1.7,PLATFORM_NAME=linux-x86_64/1270/console
*** Original change description ***
Adds support for pushing sites that don't need build, and build benchmark site.
This should not affect CI for now.
--
PiperOrigin-RevId: 147474775
MOS_MIGRATED_REVID=147474775
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 147470288
MOS_MIGRATED_REVID=147470288
|
|
|
|
|
|
|
|
| |
This should not affect CI for now.
--
PiperOrigin-RevId: 147346229
MOS_MIGRATED_REVID=147346229
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As more package options are added, it's confusing that the
debian package is generated in scripts/package/BUILD, but
scripts/package/debian/ contains the related files (and isn't
itself a Bazel package). This change makes the file locations
more predictable, and also makes it easier to see what
is happening in scripts/packages.
--
Change-Id: Id8c445fc164a1a4aa09c52559a5143578cfdea88
Reviewed-on: https://cr.bazel.build/8510
PiperOrigin-RevId: 146003934
MOS_MIGRATED_REVID=146003934
|
|
|
|
|
|
|
|
|
|
|
|
| |
The targets //site:jekyll-tree and //scripts/packages currently fail
due to the python rules. They will be reenabled, once those are fixed
in a released version.
--
Change-Id: I54a8bcad87b153e2eb4e86f8e4d76d1d92f00bf9
Reviewed-on: https://cr.bazel.build/8397
PiperOrigin-RevId: 145066780
MOS_MIGRATED_REVID=145066780
|
|
|
|
|
|
|
|
| |
--
Change-Id: Ia527ef1616546044e61a103749ff22191b24cb11
Reviewed-on: https://cr.bazel.build/8394
PiperOrigin-RevId: 144963679
MOS_MIGRATED_REVID=144963679
|
|
|
|
|
|
|
|
|
|
| |
...as they will also be run on platforms with different paths.
--
Change-Id: Iaa14e35c4cec3ed927a18b580d4207b0244a6620
Reviewed-on: https://cr.bazel.build/8392
PiperOrigin-RevId: 144960305
MOS_MIGRATED_REVID=144960305
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Those field are not added to the dsc file and reprepro has started
failing. Reproducing the whole set-up is almost impossible so I
am sending this and will trigger a test release.
Also use release label instead of release name so we get the rc
number (for some reason this was not included in previous release).
Fixes #2256.
To be cherry-picked for #2246
--
Change-Id: Ia0b879a24f1288cbbbb843013d41725fb1ddb569
Reviewed-on: https://cr.bazel.build/8032
PiperOrigin-RevId: 142537787
MOS_MIGRATED_REVID=142537787
|
|
|
|
|
|
|
|
|
|
| |
To be cherry-picked for #2246.
--
Change-Id: I50bbd7dc00e4305f36d9a2a3a8841d6d9bcd2bd7
Reviewed-on: https://cr.bazel.build/8034
PiperOrigin-RevId: 142524920
MOS_MIGRATED_REVID=142524920
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now the release branch does not contains the release commit anymore.
Instead, we regenerate the full release notes each time we have to
(release candidate creation and final release).
Two side effects:
- The date is now showing the date of the operation and no longer
the date of the release candidate (so release will be correctly dated)
- The release notes show the release candidate number :)
Tested: bazel test //scripts/release/... + build README.md
--
Change-Id: Ia249bbdc0d6ed240bd969f24aa013f709f9a0a74
Reviewed-on: https://cr.bazel.build/7338
PiperOrigin-RevId: 140841432
MOS_MIGRATED_REVID=140841432
|
|
|
|
|
|
|
|
|
|
|
|
| |
While we do need changes for certain test to refer to a local
copy of android SDKs, we do not want those changes in the
environment where we build the release artefacts (in particular
the distribution artefact).
--
Change-Id: I471a8c23efea389f52cd7b07b8511f69d16b8d3d
Reviewed-on: https://cr.bazel.build/7592
MOS_MIGRATED_REVID=140831994
|
|
|
|
|
|
|
|
|
| |
commit f17fb3a816851b9f3a954c881e3fbc35bed5d6a6 added the `-m` in the wrong location,
causing the gsutil command to fail, e.g.
http://ci.bazel.io/view/Bazel%20bootstrap%20and%20maintenance/job/Bazel-Release/87/console
--
MOS_MIGRATED_REVID=140589924
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Run the command with the `-m` option so gsutil
will copy files in parallel.
Suggested by gsutil itself
http://ci.bazel.io/view/Bazel%20bootstrap%20and%20maintenance/job/Bazel-Release/83/console
(look for "NOTE: You are performing a sequence of
gsutil operations")
--
MOS_MIGRATED_REVID=140119304
|
|
|
|
|
|
|
| |
--
Change-Id: I4d4b7d84b105061d1555da7f7144f310dde38cc8
Reviewed-on: https://cr.bazel.build/7512
MOS_MIGRATED_REVID=140025107
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=139573133
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=139572117
|
|
|
|
|
|
|
| |
On Windows, passing a shell script to this command will lead to a crash.
--
MOS_MIGRATED_REVID=139570957
|
|
|
|
|
|
|
| |
fixed https://github.com/bazelbuild/bazel/issues/2102
--
MOS_MIGRATED_REVID=139562049
|
|
|
|
|
|
|
|
|
|
|
| |
...as compile.sh from a plain checkout won't work in the future (an unpacked
distribution archive would be necessary, but using the bootstrap bazel is
easier for CI).
--
Change-Id: I186a9422bb1a092ced7396f396a8a158aa67e0f4
Reviewed-on: https://bazel-review.googlesource.com/#/c/7352
MOS_MIGRATED_REVID=139458547
|
|
|
|
|
|
|
| |
Fixed https://github.com/bazelbuild/bazel/issues/1611
--
MOS_MIGRATED_REVID=139190088
|
|
|
|
|
|
|
|
|
|
|
| |
...since we only build it on this architecture. And as it
is an architecture-independent artifact anyway, it is enough
to build it once.
--
Change-Id: I31a108154d20a190260ca5842947b6319d434735
Reviewed-on: https://bazel-review.googlesource.com/#/c/7333
MOS_MIGRATED_REVID=138859209
|
|
|
|
|
|
|
| |
--
Change-Id: I09053cbd476e5f8bb5bdb9f272ad414d165f6d9f
Reviewed-on: https://bazel-review.googlesource.com/#/c/7131
MOS_MIGRATED_REVID=138855685
|
|
|
|
|
|
|
|
|
| |
Those set-up have been moved to the Jenkins job or simply removed.
--
Change-Id: Ib687ad4ab682d81f94ea2eadacf3d145c9fcfe14
Reviewed-on: https://bazel-review.googlesource.com/7332
MOS_MIGRATED_REVID=138789683
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With the implementation of the distribution-artifact design,
calling ./compile.sh on a git checkout won't work any more
unless you already have the correct version of the protoc
installed. To prepare for that, and to also keep the maintenance
burden for the ci slaves low, we build bazel on the ci machines
with the latest release of bazel as bootstrap bazel.
--
Change-Id: I18953489cc7282586d6d0a3911ec94e11215a540
Reviewed-on: https://bazel-review.googlesource.com/#/c/6771
MOS_MIGRATED_REVID=138761693
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138389908
|
|
|
|
|
|
|
|
|
|
| |
...as quite some users are more used to downloading keys
from key servers.
--
Change-Id: I6bb60a618d50c7c70561eb5851932153c470e3d2
Reviewed-on: https://bazel-review.googlesource.com/#/c/6934
MOS_MIGRATED_REVID=137526194
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137503749
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137500893
|