aboutsummaryrefslogtreecommitdiffhomepage
path: root/scripts
Commit message (Collapse)AuthorAge
...
* Windows,bootstrapping: fix build_windows_jni.shGravatar Laszlo Csomor2017-10-06
| | | | | | | | | | | | | | Also: - check as the first thing in compile.sh that we can locate the GNU coreutils, and remove the duplicate check for the same thing on Windows - check early in compile.sh that we can access python.exe Fixes https://github.com/bazelbuild/bazel/issues/3863 Change-Id: Ib48b405cf93eafd48e21b280bcbab4d45117c1d9 PiperOrigin-RevId: 171291435
* Use releases.bazel.build instead of googleapis.comGravatar Damien Martin-Guillerez2017-10-06
| | | | | | | | This URL works everywhere in the world and is easier to remember. It also allow us to change the backend transparently. Change-Id: I25ed753e5a4c27f26a8a1a86266cc06a3cf22744 PiperOrigin-RevId: 170789151
* CI,windows: create test_suites for Windows testsGravatar L?szl? Csomor2017-09-19
| | | | | | | | | | | | | | | Add recursive test_suite rules for all tests that ci.bazel.io runs for Windows, and set the top-level test_suite as the CI test target. Doing so shortens the command line and works around https://github.com/bazelbuild/bazel/issues/3742 I verified that the old set of tests are the same as the new set. Change-Id: Id8d5da3f0c03c9b8969a9f8e1e9a3096888365aa PiperOrigin-RevId: 169242858
* Add files that were droped by our export processGravatar dmarting2017-09-19
| | | | | | | | | Those files are not linked anywhere and where removed by the export process either by accident or for better support from IntelliJ. According to ij.bazel.build a non linked target will not be analyzed so it should be safe. PiperOrigin-RevId: 169229654
* bazel_bootstrap_distfile_test: add loggingGravatar laszlocsomor2017-09-13
| | | | | | | | | | | | Add logging to bazel_bootstrap_distfile_test.sh and to buildenv.sh in hopes of catching this bug: https://github.com/bazelbuild/bazel/issues/3618 For justification, see: https://github.com/bazelbuild/bazel/issues/3618#issuecomment-328857891 RELNOTES: none PiperOrigin-RevId: 168508723
* CI slow-tests: fix parameters for non dockerGravatar dmarting2017-09-08
| | | | | | | | | We were having 2 level of parameters, so we had a unused parameters called "parameters". Fixes #3704. PiperOrigin-RevId: 167982900
* CI slow-tests: Add '+' to enforce the tag presenceGravatar dmarting2017-09-08
| | | | | | | | So we do not execute more tests that needed. Issue #3704. PiperOrigin-RevId: 167976313
* CI: Add missing comma to the docker-slow-test configGravatar dmarting2017-09-08
| | | | | | Fixes #3703. PiperOrigin-RevId: 167973195
* Have intellij ignore docker tests.Gravatar John Cater2017-09-08
| | | | | Change-Id: Iabc89286a10dd4d3314f3480f87ac74b34aee969 PiperOrigin-RevId: 167855167
* Move bazel_determinism_test to bazel-slow-test jobGravatar Damien Martin-Guillerez2017-09-08
| | | | | | | | | Now every test labelled slow will be moved to that job. Issue bazelbuild/continuous-integration#98. Change-Id: I37baa0f4233201557493a8fac643e571026fcd93 PiperOrigin-RevId: 167854935
* Update gRPC dependency to 1.6.1Gravatar buchgr2017-09-08
| | | | | | https://github.com/bazelbuild/bazel/commit/8c8633610a948846244494e2e3dad91eb0536a58 PiperOrigin-RevId: 167853283
* Shard further docker-tests and use tags for shardingGravatar Damien Martin-Guillerez2017-09-07
| | | | | | | | | | | | | | To select which test to run on bazel-docker-tests, use the docker and shard- tag intead of hard to read queries and shard based on the compilation mode. Also copy the file to bazel-slow-tests in prevision from renaming the job on CI. Issue bazelbuild/continuous-integration#98. Change-Id: Ie8e9a21c5a1ce93c9ecaa74cbb2734c150c7f592 PiperOrigin-RevId: 167752261
* Simplify bazel-{,docker-}tests.jsonGravatar Damien Martin-Guillerez2017-09-07
| | | | | | | Remove optional variation and simplify node specifications. Change-Id: Ie0a137768312152d9c036a94e5214b419b3c12ce PiperOrigin-RevId: 167717139
* bootstrap.json: removed obsoleted TODOGravatar Damien Martin-Guillerez2017-09-07
| | | | | Change-Id: If2bf41a96cde21bb97017d4fa35f8f61111635a1 PiperOrigin-RevId: 167714075
* Remove some left over bits of Java 7 supportGravatar Liam Miller-Cushon2017-09-04
| | | | | Change-Id: I3fce66ec2e63d152aafc0cf9ea067d6dbf1245f7 PiperOrigin-RevId: 167484075
* Compile Bazel with -c opt when bootstrappingGravatar Damien Martin-Guillerez2017-09-01
| | | | | | | | | So release are build with -c opt Fixes #3340. Change-Id: I455b5c2a53be5fb8fb39e247a849058f19d1d884 PiperOrigin-RevId: 167266776
* CI: Add def parser test into Windows testsGravatar pcloudy2017-08-31
| | | | | RELNOTES: None PiperOrigin-RevId: 167132537
* Clean up NO_MSVC_WRAPPER flagGravatar Yun Peng2017-08-28
| | | | | | | This flag no longer exists after MSVC-less CROSSTOOL became default. Change-Id: I015c3c03c72d15c0efe00f48e923a2d54876b1b2 PiperOrigin-RevId: 166680678
* Increase size of //src/test/shell/integration:java_integration_testGravatar Klaus Aehlig2017-08-25
| | | | | | | | | | | ...and re-enable of FreeBSD. It turns out that the timeout-flakyness was just because the CI machines weren't fast enough. Running the test 150 times showed no further timeout. Fixes #3614. Change-Id: Icdf2f91b1fe91e22117c3cf6d3fda9409d473198 PiperOrigin-RevId: 166470850
* Shard docker-testsGravatar dmarting2017-08-25
| | | | | | | | This divide the docker tests in 2 parts (with the current build file it is 6 per jobs) and each configuration can now be run on different worker. Issue bazelbuild/continuous-integration#98 PiperOrigin-RevId: 166469254
* Support BUILD.bazel in the autocomplete scriptGravatar Ian Cottrell2017-08-24
| | | | | | | | This adds support for BUILD.bazel in the bash auto completion script. Closes #3604. PiperOrigin-RevId: 166317130
* Add a Bazel test testing determinism of `bazel build //src:bazel`Gravatar Damien Martin-Guillerez2017-08-23
| | | | | | | | | - Test if hash(bazel1) == hash(bazel2) This ensure that the build of bazel is a fixed point. Change-Id: I422dfc7ec5b95aa054a2677e59427cbd8cd4ef01 PiperOrigin-RevId: 166180529
* Deactivate //src/test/shell/integration:java_integration_test on FreeBSDGravatar dmarting2017-08-23
| | | | | | This test is timeout flaky, deactivating. PiperOrigin-RevId: 166180421
* Update javac version to 9-dev-r4023-3Gravatar Liam Miller-Cushon2017-08-22
| | | | | Change-Id: If9373f81193050009432759da6299f1382e587ec PiperOrigin-RevId: 165994437
* Fix osx_cc_wrapper.sh for multiple rpathsGravatar Marcel Hlopko2017-08-18
| | | | | | | | | | | | | | osx_cc_wrapper.sh was not working correctly in cases when multiple rpaths were specified on linking command line. This cl modifies the wrapper to record all rpaths, and use the rpath that corresponds to a particular library when updating libraries install name. Fixes #3450 RELNOTES: None. Change-Id: I614694a792b6724a1db9814ee25af1802560c463 PiperOrigin-RevId: 165618946
* Update files attribute on pkg_tar.Gravatar John Cater2017-08-10
| | | | | Change-Id: I37bb40cae9d8a6ca99460df83b33541972926766 PiperOrigin-RevId: 164726294
* Remove non-existent target from IntelliJ config.Gravatar John Cater2017-08-10
| | | | | Change-Id: Id31ff0fcf72388fe1e5697b57e67385c6c27824b PiperOrigin-RevId: 164720069
* Fix typo in the chocolatey generation scriptGravatar hlopko2017-08-09
| | | | | | | | It's releases.bazel.build where we share the release candidates, not release.bazel.build. RELNOTES: None. PiperOrigin-RevId: 164694701
* Make tests more portableGravatar Klaus Aehlig2017-08-04
| | | | | | | | | By replacing uses of /bin/bash by /bin/sh, a tool which is more reliably at this location. Then, enable most of the bazel tests for FreeBSD as well. Change-Id: Ic56a1705858f1ed67d1e96e2937e9389dd1d0e36 PiperOrigin-RevId: 164241635
* Don't run bazel_windows_example_test with MSYS toolchain anymore.Gravatar pcloudy2017-07-31
| | | | | | | Instead just using a //examples/cpp:hello-world to make sure the MSYS toolchain doesn't regress. RELNOTES: None PiperOrigin-RevId: 163676783
* Adjust chocolatey package for new artifact namesGravatar Peter Mounce2017-07-31
| | | | | | Closes #3466. PiperOrigin-RevId: 163459450
* Release script: remove non-needed `xargs echo`Gravatar dmarting2017-07-28
| | | | | | They are the root cause of #3459. PiperOrigin-RevId: 163392890
* Replace create_embedded_tools.sh with a faster Python version.Gravatar Philipp Wollermann2017-07-28
| | | | | | | | | This is functionally equivalent, but ~30x faster on Windows, ~2x faster on macOS and ~1.5x faster on Linux. RELNOTES: None. Change-Id: Ib4a7e10400a3955e47772425acfce2d9530de462 PiperOrigin-RevId: 163346634
* bazel-tests.json: remove trailing commaGravatar Klaus Aehlig2017-07-27
| | | | | | | Trailing commas are not part of the JSON specification. Change-Id: Icbfc072b448e422a3cdb7fd827fbfb392611d344 PiperOrigin-RevId: 163331760
* Use the .bazel.build URL instead of the googleapis.com oneGravatar dmarting2017-07-27
| | | | PiperOrigin-RevId: 163326705
* CI build.sh: delete unused codeGravatar Damien Martin-Guillerez2017-07-27
| | | | | | | This code was replaced by code on the CI side where it belongs. Change-Id: I67741f27aee5f133fe29f8e1d57b843d96f3f9ea PiperOrigin-RevId: 163320045
* Move the configuration file for Bazel jobs to our own repositoryGravatar Damien Martin-Guillerez2017-07-27
| | | | | | | | | | This will allow to update the file that explains how to build and test Bazel at the same time that Bazel evolves. Fixes bazelbuild/continuous-integration#99 Change-Id: I2ab8641a6eb5d8cf7ea95667bd6b3af42be5a420 PiperOrigin-RevId: 163320005
* Force fetch when fetching remote release notesGravatar dmarting2017-07-26
| | | | | | | | If the release note locally are totally different, they will failed to fetch and we want to consider the remote as the source of truth rather than the local. Fixes #3447. PiperOrigin-RevId: 163202815
* Use the correct function to generate the release notesGravatar Damien Martin-Guillerez2017-07-26
| | | | | | | To be cherry-picked for #3375 Change-Id: I81e3660d1e01935101a19d75e1a696296df1941d PiperOrigin-RevId: 163202698
* Create Windows ZIP release artifact using BazelGravatar Damien Martin-Guillerez2017-07-25
| | | | | | | | | | | | 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
* Automated rollback of commit 820a46af10808396873c36d0f331e533118cf0c6.Gravatar dmarting2017-07-24
| | | | | | | | | | | | | | | | | | | | | | | | | | *** Reason for rollback *** Now the new jenkins pipeline has been rolled forward we actually needs that change To cherry-pick for #3375 *** Original change description *** Automated rollback of commit 6d6e87297fe8818e4c374fdfabfbcf538bca898a. *** Reason for rollback *** Does not work so well, see https://storage.googleapis.com/bazel/0.5.3/rc1/index.html *** Original change description *** Release script: generate the index.html from the commit message Do not rely on the README.md anymore, because it relies on log still existing forever on Jenkins. Incoming change will just provides the log as a file that will be archived on GCS. PiperOrigin-RevId: 162950464
* Don't build MSYS Bazel anymoreGravatar pcloudy2017-07-24
| | | | | | | This is the first CL to remove MSYS Bazel. RELNOTES: PiperOrigin-RevId: 162731750
* Add more of our common targets to the IJWB project file.Gravatar Philipp Wollermann2017-07-19
| | | | | | | | | | | | This will make it easier to work on Bazel's core tools like buildjar, singlejar and the JUnit test runner. Also correctly mark their tests as test code in the project. RELNOTES: None. Change-Id: Id79810b4c78b73d92b9c01b1d33f77b7504eab3d PiperOrigin-RevId: 162472964
* generate_bash_completion.sh: add explict end-of-options for exprGravatar aehlig2017-07-19
| | | | | | | | | Some implementations of expr(1) get confused if the first argument is not an option argument but starts with a minus sign. To make this script more portable, add an explict '--' argument, signaling "end of options", which seems to be understood by most implementations. PiperOrigin-RevId: 162349479
* Automated rollback of commit 6d6e87297fe8818e4c374fdfabfbcf538bca898a.Gravatar dmarting2017-07-18
| | | | | | | | | | | | | | | | | *** Reason for rollback *** Does not work so well, see https://storage.googleapis.com/bazel/0.5.3/rc1/index.html *** Original change description *** Release script: generate the index.html from the commit message Do not rely on the README.md anymore, because it relies on log still existing forever on Jenkins. Incoming change will just provides the log as a file that will be archived on GCS. Change-Id: Ib962c249145d222bf9909070698c5d419b34db4c PiperOrigin-RevId: 162321172
* Release script: generate the index.html from the commit messageGravatar Damien Martin-Guillerez2017-07-14
| | | | | | | | | Do not rely on the README.md anymore, because it relies on log still existing forever on Jenkins. Incoming change will just provides the log as a file that will be archived on GCS. Change-Id: Ib962c249145d222bf9909070698c5d419b34db4c PiperOrigin-RevId: 161804017
* Allow Debian package to be installed alongside JDK 9Gravatar Thomas Broyer2017-07-10
| | | | | | | | | Update the documentation to instruct explicitly installing JDK 8. Fixes #3147 Change-Id: If92ff93b095bead043c9b069e000b7afbc0abca0 PiperOrigin-RevId: 161387193
* build_windows_jni.sh: move file to subdirectoryGravatar Laszlo Csomor2017-07-05
| | | | | | | | | | | | | The script more logically belongs in src/main/native/windows than in src/main/native. Also move the //src/main/native:windows_jni rule into //src/main/native/windows:windows_jni, so the logic of building the JNI library is fully contained in that package. Change-Id: I96e19003932cc0ddc5af3471b0b31a1aec09b8fa PiperOrigin-RevId: 160876594
* Bazel, bootstrap: fix JNI build errorsGravatar Laszlo Csomor2017-06-29
| | | | | | | Fixes https://github.com/bazelbuild/bazel/issues/3292 Change-Id: I67db893c36067b950303d2b131b925dce974d7d1 PiperOrigin-RevId: 160529960
* zsh completion: discard progress from internal bazel invocationsGravatar Klaus Aehlig2017-06-29
| | | | | | | | | When computing completion options, bazel has to be called. For those calls, discard the progress output (on stderr) to avoid them messing up the terminial. Fixes #2279. Change-Id: Ic1536058a44dac687ad59042ec56af50a4125f3b PiperOrigin-RevId: 160525601