aboutsummaryrefslogtreecommitdiffhomepage
path: root/site/versions
Commit message (Collapse)AuthorAge
* Polish the documentation addressing #3063Gravatar hlopko2017-05-30
| | | | | RELNOTES: None. PiperOrigin-RevId: 157401168
* Update Windows documentGravatar Yun Peng2017-05-30
| | | | | | | | | | 1. We are not high experimental any more 2. Point known issues to the right place 3. Make it clear that we also support python 3 4. MSVC is the default on Windows toolchain since 0.5.0 Change-Id: I804215b7b14263e43b30cdf76a9aaf0eb4598cee PiperOrigin-RevId: 157398506
* For version 0.5.0, update installation instructions:Gravatar Googler2017-05-29
| | | | | | | | | - Bazel with JDK 7 will not be supported past 0.5.0 - a new installer is available with embedded JDK This change should only be submitted when version 0.5.0 is released. PiperOrigin-RevId: 157396320
* Update documentation to address #3063Gravatar hlopko2017-05-29
| | | | | RELNOTES: None PiperOrigin-RevId: 157393208
* fixed broken "compile bazel from source" in "ubuntu" pageGravatar Or Shachar2017-05-26
| | | | | | Closes #3052. PiperOrigin-RevId: 157210157
* Clarify difference between sources and distribution archiveGravatar Klaus Aehlig2017-05-22
| | | | | | | | | | In the install instructions, explain that the distribution archive contains more files than a checkout of the source tree. It is a common mistake to believe that using a checkout of the source tree is equivalent to downloading a distribution archive. Change-Id: I13cc48f5efe93bd2593d7b74d1f7c6db19de74dc PiperOrigin-RevId: 156732571
* Update install-ubuntu.mdGravatar MarkusTeufelberger2017-05-19
| | | | | | | | Fixed small grammatical error (sending this doc change through GH to demonstrate how this change process looks for a completely external contributor, see also https://github.com/bazelbuild/bazel/pull/2784) Closes #2786. PiperOrigin-RevId: 156342450
* Fix Java class file name (must match class name).Gravatar Googler2017-05-19
| | | | PiperOrigin-RevId: 156315435
* Fix mandatory provider example in cookbookGravatar brandjon2017-05-11
| | | | | RELNOTES: None PiperOrigin-RevId: 155766583
* Fix some typos in best-practices doc.Gravatar janakr2017-05-10
| | | | PiperOrigin-RevId: 155521449
* docs: fix the documentation for server/ output directoryGravatar Thiago Farina2017-05-05
| | | | | | | | "server.log" is not written anymore, what goes in now is: cmdline, jvm.out and server.starttime. Change-Id: I81b8c1d2647001e2c9c2bf3f1fc304d348033ef3 PiperOrigin-RevId: 155174690
* Document our syntactic guaranteesGravatar brandjon2017-05-04
| | | | | RELNOTES: None PiperOrigin-RevId: 155113548
* Improve docs regarding the CPU core reservation feature for tests.Gravatar philwo2017-05-04
| | | | PiperOrigin-RevId: 155063811
* Document output groups.Gravatar Dmitry Lomov2017-05-04
| | | | | | | Work towards #2880. Change-Id: I7b661e368c0bd60fc6bcc10c7c1d63b82ba9702e PiperOrigin-RevId: 154957882
* Clarification on the cookbook example "cc_and_something_else_binary"Gravatar laurentlb2017-05-03
| | | | | | | | Reorder definitions, based on user feedback. Add some comments. RELNOTES: None. PiperOrigin-RevId: 154951404
* Set the local CPU reservation for tests based on their "cpu:<n>" tag.Gravatar philwo2017-05-03
| | | | | | | | | | | | | | | | | | This lets users specify that their test needs a minimum of <n> CPU cores to run and not be flaky. Example for a reservation of 4 CPUs: sh_test( name = "test", size = "large", srcs = ["test.sh"], tags = ["cpu:4"], ) This could also be used by remote execution strategies to tune their resource adjustment. RELNOTES: You can increase the CPU reservation for tests by adding a "cpu:<n>" (e.g. "cpu:4" for four cores) tag to their rule in a BUILD file. This can be used if tests would otherwise overwhelm your system if there's too much parallelism. PiperOrigin-RevId: 154856091
* Clarify the meaning of the two symbol counts that Gold outputs forGravatar Googler2017-05-03
| | | | | | --print-symbol-counts. PiperOrigin-RevId: 154843561
* Add best practices docGravatar kchodorow2017-05-02
| | | | PiperOrigin-RevId: 154734540
* Add documentation for cfg = "target".Gravatar Googler2017-04-28
| | | | PiperOrigin-RevId: 154441586
* Bazel docs: Add section about dependeing on external packages, refactor ↵Gravatar steren2017-04-28
| | | | | | | external dependencies page. RELNOTES: None PiperOrigin-RevId: 154426608
* Fix the aspects documentationGravatar vladmos2017-04-26
| | | | | | Fixes #2873 PiperOrigin-RevId: 154294358
* Update getting-started.mdGravatar michelleirvine2017-04-25
| | | | | | | | Fixed small typo (sending this doc change through GH to try this change process) Closes #2784. PiperOrigin-RevId: 154167908
* Document declared providers.Gravatar Dmitry Lomov2017-04-25
| | | | | Change-Id: Ifdc1773fb1439c16327bb84961998793a942e666 PiperOrigin-RevId: 154151084
* Make implementations method non-publicGravatar Régis Décamps2017-04-24
| | | | | | | | | | Prefix implementation methods with one underscore. Also, consistently surround attribute assignmenets by spaces `rule(x = y)` instead `rule(x=y)`. Closes #2770. PiperOrigin-RevId: 154036583
* Updated Java tutorial so it is now an introductory to Bazel.Gravatar Googler2017-04-24
| | | | | | The Java project used in the tutorial has stayed the same. PiperOrigin-RevId: 153747213
* Edit to match description of 'workspace' in the Java tutorial.Gravatar Googler2017-04-19
| | | | PiperOrigin-RevId: 153474001
* Do not add a build id to C++ binaries by default.Gravatar lberki2017-04-13
| | | | | | | Fixes #2805. RELNOTES: None. PiperOrigin-RevId: 153039178
* Docs: fix "<" and ">" in bash commandGravatar laszlocsomor2017-04-11
| | | | | | | Fixes https://github.com/bazelbuild/bazel/issues/1586 RELNOTES: none PiperOrigin-RevId: 152679734
* Fix typos in Bazel C++ tutorial documentationGravatar Googler2017-04-04
| | | | | | The tutorial discusses code for a "Hello World" program, but the test near the end is named "FactorialTest". This seems like a copy-and-paste error. PiperOrigin-RevId: 152140360
* Windows, docs: update VC++ requirementsGravatar laszlocsomor2017-04-04
| | | | | | RELNOTES: none PiperOrigin-RevId: 152137659
* Remove leading '$' from docs that are interfering with copy/pasteGravatar laszlocsomor2017-04-04
| | | | | | | | Fixes: https://github.com/bazelbuild/bazel/issues/2399 Change-Id: I21d00430cdf7ece72f532a1cb1be94e9b07a0114 PiperOrigin-RevId: 152001779
* Keep compile-from-source instructions distribution agnosticGravatar aehlig2017-03-29
| | | | | | | | | | The instructions on how to compile bazel from source are particularly useful for platforms where no ready-made binaries are provided for. As such, we should not assume a debian-package--based system. It is OK to mention what needs to be done on those systems, but only as an example after stating the goal to achive (have OpenJKD 8 installed). PiperOrigin-RevId: 151571121
* Changed "OS X" to "macOS (OS X)" to be consistent. Change was made to the ↵Gravatar Googler2017-03-29
| | | | | | | | doc, faq, and contribute topics. Did not update content which is static: blog posts, release notes, design docs. PiperOrigin-RevId: 151569872
* Updated .md header: Windows Chocolatey maintenance is now in 'contribute' ↵Gravatar Googler2017-03-29
| | | | | | section, not 'documentation' PiperOrigin-RevId: 151461423
* Some fixes for ijar tests.Gravatar kchodorow2017-03-29
| | | | PiperOrigin-RevId: 151461345
* - Clarify that we still support Ubuntu 14.04.Gravatar Googler2017-03-28
| | | | | | | | - When compiling from source, adding instructions to install OpenJDK 8 -- PiperOrigin-RevId: 151440425 MOS_MIGRATED_REVID=151440425
* Fix for broken links on bazel.build - updated the .md headers for these ↵Gravatar Googler2017-03-27
| | | | | | | | three files -- PiperOrigin-RevId: 151319959 MOS_MIGRATED_REVID=151319959
* Update to Bazel's installation instructions:Gravatar Googler2017-03-22
| | | | | | | | | | - adding doc about Ubuntu 16.04 - removing doc about Ubuntu 14.04 - individual platform instructions now chunked into separate doc topics -- PiperOrigin-RevId: 150856210 MOS_MIGRATED_REVID=150856210
* Recover a link that seems to have been lost in a doc migration.Gravatar Googler2017-03-22
| | | | | | -- PiperOrigin-RevId: 150783779 MOS_MIGRATED_REVID=150783779
* Fix link (maybe)?Gravatar Jon Brandvein2017-03-20
| | | | | | -- PiperOrigin-RevId: 150439226 MOS_MIGRATED_REVID=150439226
* Fix broken link: s/html/md/Gravatar Googler2017-03-20
| | | | | | -- PiperOrigin-RevId: 150431342 MOS_MIGRATED_REVID=150431342
* Make mobile-install wait for debuggerGravatar Googler2017-03-17
| | | | | | -- PiperOrigin-RevId: 150372383 MOS_MIGRATED_REVID=150372383
* Detail support channels Gravatar Steren Giannini2017-03-10
| | | | | | | | | | | Put forward Stack Overflow as the main place for questions. Closes #2623. -- Reviewed-on: https://github.com/bazelbuild/bazel/pull/2623 PiperOrigin-RevId: 149754442 MOS_MIGRATED_REVID=149754442
* Small fixes: title case and rendering of rule names.Gravatar Googler2017-03-09
| | | | | | -- PiperOrigin-RevId: 149536881 MOS_MIGRATED_REVID=149536881
* Typo fixGravatar Jon Brandvein2017-03-07
| | | | | | -- PiperOrigin-RevId: 149418254 MOS_MIGRATED_REVID=149418254
* Update android tutorial to clarify android sdk path options Gravatar Iain McGinniss2017-03-07
| | | | | | | | | | | The android_sdk_repository path parameter is now optional, and for most setups it is easier to omit it and rely on the `ANDROID_HOME` environment variable. Updated this part of the tutorial to clarify this. Closes #2632. -- Reviewed-on: https://github.com/bazelbuild/bazel/pull/2632 PiperOrigin-RevId: 149337570 MOS_MIGRATED_REVID=149337570
* Topic describing "what is Bazel" at a high-level, with a focus on: build ↵Gravatar Googler2017-03-06
| | | | | | | | files and their language, the dependency graph, and Bazel being fast/correct/reproducible. -- PiperOrigin-RevId: 149114565 MOS_MIGRATED_REVID=149114565
* Update instructions for building bazel from source Gravatar Klaus Aehlig2017-03-02
| | | | | | | | | | | | | As we do not recommend using versions of bazel pre 0.4.1, drop instructions on how to build those old versions. Also, emphasize that building bazel at HEAD is only assumed to work, if the latest version of bazel is used. Hopefully, this will help avoid misunderstandings as in #2608. -- Change-Id: I5192bbc7420a3611fad99b8872e0074a02060183 Reviewed-on: https://cr.bazel.build/9119 PiperOrigin-RevId: 148982493 MOS_MIGRATED_REVID=148982493
* Add Java install step for Homebrew install guide Gravatar Steren2017-02-28
| | | | | | | | | | | fix #2438 Closes #2439. -- Reviewed-on: https://github.com/bazelbuild/bazel/pull/2439 PiperOrigin-RevId: 148781010 MOS_MIGRATED_REVID=148781010
* Remove shell highlighting which isn't supported by our version of jekyll. Gravatar John Cater2017-02-27
| | | | | | | | | | Fixes #2587. -- Change-Id: Ieaedd70c6b7561be3765fe41f81e3c3f388f9cc7 Reviewed-on: https://cr.bazel.build/9090 PiperOrigin-RevId: 148466063 MOS_MIGRATED_REVID=148466063
generated by cgit v1.2.3 (git 2.39.1) at 2024-07-09 02:11:07 +0000