| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The file is left as an empty file, so make upgrades easier. Site administrators can add their own content as needed, still.
Fixes #4850.
Closes #4857.
TESTED: Created a Debian VM and tested installing the new version as an upgrade and as the first Bazel, observed that the global bazelrc had the expected content.
RELNOTES: Remove the default content of the global bazelrc.
Change-Id: I5f285f0c59d18179005ffe5bfc35931299635bbb
PiperOrigin-RevId: 190060838
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes #4810, invalidates #4782, and extends #4747.
Change-Id: I19426bb30a151358875e9bae0e0c1d92b3818432
Closes #4816.
Change-Id: I5d92cec994103e2136c5ed279780f321a42d1bdd
PiperOrigin-RevId: 188722982
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Commit c8be465869fbcfaa00b75d241c67279324976e0b added the headless JDK
to `debian/control`, but this isn't propagating to published packages
because those use the deps list in `debian/BUILD`.
This commit adds the headless JDK to `debian/BUILD`, with comments so
future changes won't hit the same problem.
Closes #4686.
PiperOrigin-RevId: 187461399
|
|
|
|
| |
PiperOrigin-RevId: 183840991
|
|
|
|
|
| |
Change-Id: I33717f6a68035bfd5f8406685f935253e1d24325
PiperOrigin-RevId: 183815476
|
|
|
|
|
|
|
|
|
|
|
| |
The debian package changlog file doesn't have to contain the real CHANGELOG.md.
Parsing change log is error-prone and caused our release job to fail everytime,
so here we simplified the script for generating changelog.
Fix https://github.com/bazelbuild/bazel/issues/4530
Change-Id: I8adc5a98def5709ea57f9edbed9f0cf772a48d76
PiperOrigin-RevId: 183651058
|
|
|
|
|
| |
Change-Id: Ie6070b01e7d004589064edc1f182baa6b6fac8b4
PiperOrigin-RevId: 182940613
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1.Deleted config_setting for --cpu=x64_windows_msys, because we don't build
Bazel with MSYS gcc anymore.
2.Deleted config_setting for --cpu=x64_windows_msvc, because it uses exactly
the same toolchain as --cpu=x64_windows, it'll be removed in the future.
This change reduces the complexity of our BUILD files and make them less
confusing.
Change-Id: I939831a6861413b0f745fb1be98aacd4fb780e0a
PiperOrigin-RevId: 181751853
|
|
|
|
|
|
|
| |
This will enable an easier transition from checked-in BUILD files to ones generated by copybara.
RELNOTES: None
PiperOrigin-RevId: 177514519
|
|
|
|
|
|
|
|
|
|
|
|
| |
Apparently powershell on macOS is a thing now...
However, chocolatey does not yet seem to be...
cc @dslomov
Closes #4026.
PiperOrigin-RevId: 177172660
|
|
|
|
|
|
|
|
| |
Fixes https://github.com/bazelbuild/bazel/issues/3761
Closes #4015.
PiperOrigin-RevId: 176340908
|
|
|
|
|
|
|
|
|
|
| |
Now that the experimental_ui is enabled by default in commit
784bb52613feb484221c3aa6756de, we do not need to enable it in the
(recommended) bazelrc file anymore. While there, also move the default
number of actions shown in the experimental_ui to the flag default.
Change-Id: I74673a0d677b6d832c9fb5e2983f97c0dcbc44e4
PiperOrigin-RevId: 172736977
|
|
|
|
|
| |
Change-Id: I3fce66ec2e63d152aafc0cf9ea067d6dbf1245f7
PiperOrigin-RevId: 167484075
|
|
|
|
|
| |
Change-Id: I37bb40cae9d8a6ca99460df83b33541972926766
PiperOrigin-RevId: 164726294
|
|
|
|
|
|
|
|
| |
It's releases.bazel.build where we share the release candidates, not
release.bazel.build.
RELNOTES: None.
PiperOrigin-RevId: 164694701
|
|
|
|
|
|
| |
Closes #3466.
PiperOrigin-RevId: 163459450
|
|
|
|
| |
PiperOrigin-RevId: 163326705
|
|
|
|
|
|
|
|
|
|
|
|
| |
The new pipeline does not support ziping artifact which was
a custom hack for Windows, relies on Bazel to generate those
zip instead.
Step forward fixing bazelbuild/continuous-integration#101
To cherry-pick for #3375.
Change-Id: Id566d66bb179096d60c5b535f245d64cea28c5b8
PiperOrigin-RevId: 163054883
|
|
|
|
|
|
|
|
|
| |
Update the documentation to instruct explicitly installing JDK 8.
Fixes #3147
Change-Id: If92ff93b095bead043c9b069e000b7afbc0abca0
PiperOrigin-RevId: 161387193
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the bazelrc we ship with our packages and recommend other
package maintainers to use, enable the experimental_skyframe_target_evaluator
and experimental_ui by default. Also set show_progress_rate_limit
to a value that fits with the experimental UI.
We plan to switch to those values as default (Issue #3187), and by
setting apropriate defaults in the rc-file, we encourage users to
test those settings while giving the possibility to easily roll back,
should any problems arise.
Change-Id: I456a5a34158541151a0bff61f3039b3d7e2d61b0
PiperOrigin-RevId: 158970147
|
|
|
|
|
|
|
|
| |
reading.
Closes #2794.
PiperOrigin-RevId: 158117701
|
|
|
|
|
|
|
|
|
|
|
|
| |
This attempts to fix #3006.
This change will presumably have to be reversed once msysless binary name changes to become the default.
It would be simpler to name the default binary for being default, to avoid special casing (see https://github.com/bazelbuild/bazel/issues/3006#issuecomment-301440068).
Closes #3066.
PiperOrigin-RevId: 157390473
|
|
|
|
|
|
| |
bundled JDK.
PiperOrigin-RevId: 156092071
|
|
|
|
|
|
|
| |
Closes #2959.
Ping #2692 for cherry-picking into Bazel 0.5.0.
PiperOrigin-RevId: 155357560
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
Bazel binary installer contains empty files because of the line that wasn't removed while packaging bazel_tools inside bazel.
Fixes: https://github.com/bazelbuild/bazel/issues/2662
Change-Id: I53a1f74566c48c3458ced2d46362873a68b6bf49
PiperOrigin-RevId: 153048191
|
|
|
|
|
|
| |
Closes #2764.
PiperOrigin-RevId: 152907840
|
|
|
|
|
|
|
|
|
|
| |
This causes a hard-fail. I'm attempting to publish a fixed package now, but chocolatey.org is failing with a `502 Bad Gateway`. I'm talking to the chocolatey team in their gitter now.
I'll update here once I've been able to push.
Closes #2758.
PiperOrigin-RevId: 151693032
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
@laszlocsomor - This addresses https://github.com/bazelbuild/bazel/issues/2449#issuecomment-278059161.
Note - this is _not_ in the 0.4.5 package, since I was waiting for that release to go out prior to this.
Closes #2690.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/2690
PiperOrigin-RevId: 150745085
MOS_MIGRATED_REVID=150745085
|
|
|
|
|
|
|
|
|
| |
Closes #2678.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/2678
PiperOrigin-RevId: 150167309
MOS_MIGRATED_REVID=150167309
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Powershell v2 (win7 vintage) doesn't have json cmdlets.
Got a report via chocolatey.org message that this doesn't work on win7. Cried. Replaced with simpler text file based approach for separating data from code.
Also fix package version fix notation bit of the automation to produce version numbers valid with chocolatey/nuspec.
I've already published a fixed 0.4.5-rc2 and 0.4.4 with this
* https://chocolatey.org/packages/bazel/0.4.4.20170306
* https://chocolatey.org/packages/bazel/0.4.5-rc2-20170306-124051
Closes #2633.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/2633
PiperOrigin-RevId: 149314972
MOS_MIGRATED_REVID=149314972
|
|
|
|
|
|
|
|
|
|
|
|
| |
To be cherry-picked for #2472.
Fixes #2605.
--
Change-Id: Idfd1bf264ceb696ca766268c8a16891476ee33b1
Reviewed-on: https://cr.bazel.build/9111
PiperOrigin-RevId: 148749784
MOS_MIGRATED_REVID=148749784
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 147825291
MOS_MIGRATED_REVID=147825291
|
|
|
|
|
|
|
|
|
|
| |
RELNOTES: Adds pkg_rpm rule for generating RPM packages.
--
Change-Id: I2e83161e29218700bbe7e62186b0b1667e555a7c
Reviewed-on: https://cr.bazel.build/8590
PiperOrigin-RevId: 146477490
MOS_MIGRATED_REVID=146477490
|
|
|
|
|
|
|
|
| |
--
Change-Id: I8c6d5cdbe9e2fc19ca6a626bea26944efa36e4db
Reviewed-on: https://cr.bazel.build/8550
PiperOrigin-RevId: 146120078
MOS_MIGRATED_REVID=146120078
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
--
Change-Id: Ief0dd31d7b514caaf5ea0108b7c497d42e86da70
Reviewed-on: https://cr.bazel.build/8395
PiperOrigin-RevId: 144966247
MOS_MIGRATED_REVID=144966247
|
|
|
|
|
|
|
|
|
|
|
|
| |
This only builds a development package, further work (and probably a full pkg_rpm rule) will be needed to make a releasable RPM.
Closes #2276.
--
Change-Id: If307c6143334957a127c7c2fe897009a08e88d5c
Reviewed-on: https://github.com/bazelbuild/bazel/pull/2276
PiperOrigin-RevId: 143450212
MOS_MIGRATED_REVID=143450212
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
correctly""
Roll-forward with fix: the original change did not produced any changelog if
this was not a release branch, use a default, empty one in that case. The
debian version number will then be LAST_VERSION~HEAD
This reverts commit e4cf9aa8b63173326cfe72ba76be4303bc038def.
--
Change-Id: I9e19b1132570ea20d90053734418f2703b1a641e
Reviewed-on: https://cr.bazel.build/7976
PiperOrigin-RevId: 142525180
MOS_MIGRATED_REVID=142525180
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 9012bf1676bd6426229625e2567bfa399f89dabe.
Fixes #2260.
--
Change-Id: Ia08dd65d55274acdd15993cfde4eab225fb01df0
Reviewed-on: https://cr.bazel.build/8012
PiperOrigin-RevId: 142294105
MOS_MIGRATED_REVID=142294105
|
|
|
|
|
|
|
|
|
|
|
| |
Partial fix of #2256
To cherry-pick for #2246
--
Change-Id: Ib25cc1dd85fd4af59b36eb2ac215ebd31d4d9eaa
Reviewed-on: https://cr.bazel.build/7975
PiperOrigin-RevId: 142262764
MOS_MIGRATED_REVID=142262764
|
|
|
|
|
|
|
|
|
| |
Closes #2152.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/2152
PiperOrigin-RevId: 141046624
MOS_MIGRATED_REVID=141046624
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The launcher script uses "exec -a" to launch the wrapper, but if
the wrapper script is itself a Bash script, Bash will set "$0" to be
the path to the wrapper script, not the path to the launcher script.
To work around this, we've been having our wrapper script search the
user's PATH environment variable for bazel-real, but that doesn't
work well with the IntelliJ plugin for Bazel, which may not use the
expected PATH environment.
--
Change-Id: I402ad29d5b809be8e687e217e19c03e7ac3eb972
Reviewed-on: https://cr.bazel.build/7550
PiperOrigin-RevId: 140851992
MOS_MIGRATED_REVID=140851992
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With this change, `oracle-java7-installer` and `oracle-java8-installer` become
alternatives to satisfy the JDK dependency and thus can be implicitly installed
when someone just asks to install Bazel by itself.
Resolves issue #1821.
Closes #2137.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/2137
MOS_MIGRATED_REVID=140200795
|
|
|
|
|
|
|
|
| |
Closes #2095.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/2095
MOS_MIGRATED_REVID=140134289
|
|
|
|
|
|
|
|
|
|
|
|
| |
I've used this to create https://chocolatey.org/packages/bazel/0.4.1-rc2-20161124-122858 which is in the queue for automated validation.
That package is built with #2134.
Closes #2135.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/2135
MOS_MIGRATED_REVID=140131036
|
|
|
|
|
|
|
|
|
|
| |
See gitter chat around https://gitter.im/chocolatey/choco?at=58361d42b07a1fd34833fe36. The rc failed automatic validation because of it, we think.
Closes #2134.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/2134
MOS_MIGRATED_REVID=140114046
|