| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
Since we no longer release the Bazel version without an embedded JDK.
RELNOTES: None
PiperOrigin-RevId: 205356986
|
|
|
|
|
|
| |
Closes #5100.
PiperOrigin-RevId: 195078092
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 194084231
|
|
|
|
|
|
| |
https://github.com/spomorski/bazel/edit/patch-1/site/docs/install-ubuntu.md?pr=/bazelbuild/bazel/pull/5024
PiperOrigin-RevId: 193379306
|
|
|
|
|
|
|
|
| |
Updating macOS install instructions together with David.
Closes #5025.
PiperOrigin-RevId: 193374002
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 178406494
|
|
|
|
|
|
|
| |
will change often)
RELNOTES: Replace version numbers for Bazel installers with "<version>" (because this will change often)
PiperOrigin-RevId: 173566716
|
|
|
|
| |
PiperOrigin-RevId: 170057335
|
|
|
|
|
|
|
|
| |
I assume apt-get upgrade does _not_ upgrade the shell-script install, especially if you used `--user` but also in general.
Closes #3596.
PiperOrigin-RevId: 166823519
|
|
|
|
|
| |
RELNOTES: Python is now required to build bazel.
PiperOrigin-RevId: 165694080
|
|
|
|
|
|
|
|
|
| |
Update the documentation to instruct explicitly installing JDK 8.
Fixes #3147
Change-Id: If92ff93b095bead043c9b069e000b7afbc0abca0
PiperOrigin-RevId: 161387193
|
|
|
|
|
|
|
| |
Also, the JDK7 version actually did not work in 0.5.1.
RELNOTES: None
PiperOrigin-RevId: 160645551
|
|
|
|
|
|
|
|
|
| |
Also remove warning about macOS bug in 0.5.0 and instructions about JDK7
Fixes https://github.com/bazelbuild/bazel/issues/3222
RELNOTES: None
PiperOrigin-RevId: 159569520
|
|
The new docs/ directory in the bazel source tree will only contain the Bazel
docs site, which is hosted at docs.bazel.build. This change deletes the
marketing site and blog, which have been migrated to the bazel-website and
bazel-blog GitHub repositories respectively.
This change also updates the serve-docs.sh and ci/build.sh under scripts/ in
preparation for publishing the docs site.
Note that to help make reviews more manageable, this change is limited to
moving files to their new locations. Here are the follow-up changes:
* Update all links in docs to remove versions/master in paths and to add
correct bazel.build subdomain when linking to pages on the marketing site
or the blog.
* Set up versioned directories on GCS bucket and add tooling for versioning
docs
This change is also coordinated with
https://bazel-review.googlesource.com/c/11568/ to have the PublishSite job
publish to docs.bazel.build rather than www.bazel.build.
Issue #2397
RELNOTES: None
PiperOrigin-RevId: 157612651
|