aboutsummaryrefslogtreecommitdiffhomepage
path: root/scripts
Commit message (Collapse)AuthorAge
...
* Shell code cleanupGravatar Androbin2017-12-14
| | | | | | | | | | | | - Argument mixes string and array. Use * or separate argument. - Quote the grep pattern so the shell won't interpret it. - Use "${var:?}" to ensure this never expands to /* . - > is for string comparisons. Use -gt instead. - Quote the parameter to -name so the shell won't interpret it. Closes #4163. PiperOrigin-RevId: 179042046
* Fix broken target in Intellij project definition.Gravatar buchgr2017-12-13
| | | | | RELNOTES: None. PiperOrigin-RevId: 178892596
* Add a toolchains= dependency to a few genrules so that the Bazel test suite ↵Gravatar lberki2017-12-11
| | | | | | | | | passes. Fixes #4268 . RELNOTES: None. PiperOrigin-RevId: 178604877
* Moving the RemoteWorker into tools/remote directory.Gravatar olaola2017-12-05
| | | | | | | | This is because I want to add another remote execution related tool, the remote_client, which will use the Remote Execution API to fetch blobs from a remote cache. I will use this tool as part of end-to-end tests for remote execution. TESTED=remote integration tests, presubmit RELNOTES: None PiperOrigin-RevId: 177995895
* scripts/serve-docs.sh: allow overriding PORT/HOSTGravatar Klaus Aehlig2017-12-05
| | | | | | | | | ...through the corresponding environment variables. In this way, more than one documentation version can be served, e.g., to simplify comparing. Change-Id: I4ae069a4a48f12e9bd48210ee3bd22299149f59d PiperOrigin-RevId: 177959891
* Move bazel conditions into src/conditions.Gravatar tomlu2017-11-30
| | | | | | | This will enable an easier transition from checked-in BUILD files to ones generated by copybara. RELNOTES: None PiperOrigin-RevId: 177514519
* Add . to the bootstrap protoc include pathsGravatar Olivier Chafik2017-11-29
| | | | | | | | | | | | | | | | | | | This fixes the following error I got when building from scratch on Raspbian: ``` src/main/protobuf/invocation_policy.proto: File not found. src/main/protobuf/command_line.proto: File not found. ``` Note: ``` protoc --version libprotoc 3.0.0 ``` Closes #4187. PiperOrigin-RevId: 177306773
* Enable auto-completion for the "ibazel" commandGravatar Martin Probst2017-11-29
| | | | | | | | | | ibazel implements a the same command line interface as bazel, so we can just use the same completion function. See https://github.com/bazelbuild/bazel-watcher. Closes #4091. PiperOrigin-RevId: 177282217
* Various Shell Script Fixes and Improvements - Part OneGravatar Androbin2017-11-29
| | | | | | | | see #4023 Closes #4051. PiperOrigin-RevId: 177279457
* macOS compatibility in build.ps1.Gravatar Peter Mounce2017-11-28
| | | | | | | | | | | | Apparently powershell on macOS is a thing now... However, chocolatey does not yet seem to be... cc @dslomov Closes #4026. PiperOrigin-RevId: 177172660
* Fix //src/test/shell/integration:progress_reporting_testGravatar Klaus Aehlig2017-11-21
| | | | | | | | | | | | | | | | The test case test_failed_actions_with_keep_going was never correct and only worked by accident: it relied on bazel starting at least two actions, if for there are at least two where all the dependencies are already met; however bazel is clever and analyzes the resources of the system it is running in, and if they are small will only run one genrule at a time. Fix this by telling it to run 2 actions and lying about the available resources of the local system. Also increase the test size and reenable the test for remote execution. Fixes #3995. Change-Id: Ic84de17a98a2e74c24901d4efb38d7631de4690a PiperOrigin-RevId: 176511026
* SOURCE_DATE_EPOCH environment variable override the timestampGravatar Damien Martin-Guillerez2017-11-21
| | | | | | | | | | | | | | | | | | | | This is applying the version 1.1 of the specification (https://reproducible-builds.org/specs/source-date-epoch/) where the only timestamp that Bazel puts in the final targets is overridden by the value of SOURCE_DATE_EPOCH. This change also remove the legacy SOURCE_DATE_EPOCH handling which wasn't really following the spec. Note that Bazel itself tries hard to remove all timestamps from intermediary binaries and overridde SOURCE_DATE_EPOCH in most action, which is a not according to the version 1.0 of the spec but according to the expected change for version 1.1. RELNOTES: SOURCE_DATE_EPOCH (https://reproducible-builds.org/specs/source-date-epoch/) can be used to override the timestamp used for stamped target (when using --stamp). Fixes #2240. Change-Id: I074e7905fa6745cc706f7391340aeae9188909ca PiperOrigin-RevId: 176489717
* Allow Bazel's Debian package to install with headless JDK.Gravatar John Millikin2017-11-20
| | | | | | | | Fixes https://github.com/bazelbuild/bazel/issues/3761 Closes #4015. PiperOrigin-RevId: 176340908
* third_party/grpc: Update to version 1.7.0Gravatar Jakob Buchgraber2017-11-17
| | | | | Change-Id: I9ae0c56844db45e28eb5a08e8180514aa2729fdf PiperOrigin-RevId: 176114077
* Remove target from BUILD file that was prematurely added in ↵Gravatar dannark2017-11-17
| | | | | | | https://github.com/bazelbuild/bazel/commit/75d8fe1d347b45f4dd808a76c3a73b24f9728284. RELNOTES: None PiperOrigin-RevId: 176107565
* third_party/grpc: Update to version 1.7.0Gravatar Jakob Buchgraber2017-11-17
| | | | Change-Id: I9ae0c56844db45e28eb5a08e8180514aa2729fdf
* Deactivate //src/test/shell/integration:progress_reporting_test on remote testsGravatar dmarting2017-11-12
| | | | | | This test is hitting time out on remote execution. Until the workers are fixed, deactivate it. PiperOrigin-RevId: 175478669
* Deactivate FreeBSD-12 testsGravatar dmarting2017-11-12
| | | | | | Issue bazelbuild/continuous-integration#149: FreeBSD 12 slaves cannot copy the Bazel binary keeping permission correctly. PiperOrigin-RevId: 175474382
* Make bazel work with java9Gravatar Bernhard M. Wiedemann2017-11-09
| | | | | | | | | unlike earlier versions, openjdk9 returns "javac 9" when asked for its version Closes #4004. PiperOrigin-RevId: 175029317
* Remove no longer used site publisherGravatar Damien Martin-Guillerez2017-11-08
| | | | | | | This is now done by a Google Cloud Container Builder job. Change-Id: I33a9543f9b5bdb083171482e9eaebdb43e77181b PiperOrigin-RevId: 174905217
* Fix Bazel nightlies: do not build webappGravatar dmarting2017-11-07
| | | | | | This target was removed. PiperOrigin-RevId: 174870373
* Fix the docker path for Bazel docs publisher and set timeoutGravatar dmarting2017-11-07
| | | | PiperOrigin-RevId: 174867981
* Add files to build site directly on Google Cloud Container BuilderGravatar Damien Martin-Guillerez2017-11-06
| | | | | | | | | | | | | | | Using `bazel build //site` will now build the site (needs the proper version of Jekyll in the path :/), `bazel run //site` will serve it using Jekyll. This change also contains the yaml file to build and deploy the site on Google Cloud Container Builder. This will allow to remove that special hook from our CI. Note: this is copied from https://github.com/bazelbuild/bazel-blog Change-Id: I6bb04fea0fa80623bd5d25a5f191ae49e8074e92 PiperOrigin-RevId: 174459256
* Delete benchmark code.Gravatar tomlu2017-11-06
| | | | | | This is no longer maintained and the CI is turned down. PiperOrigin-RevId: 174456265
* Migrate bazel-tests-remote.json and update configsGravatar Xin Gao2017-11-03
| | | | | | | | | | | - Migrate bazel-tests-remote.json file from bazelbuild/continuous-integration repo to bazelbuild/bazel repo. - Update toolchain and configs to use container v0.2.0 and new configs (v0.7.0 for c++, v0.6.0 for java). Change-Id: Ib376f662c6c6cec617d82133254f9a12ef67e748 PiperOrigin-RevId: 174329569
* Do not output Bazel leaves to logs.Gravatar Dmitry Lomov2017-10-24
| | | | | | | Unicode characters are trouble we do not want. Change-Id: I5f5239baab60a875a697f2ee3104225e19c0ce1d PiperOrigin-RevId: 173245285
* bazelrc: remove experimental_ui optionsGravatar Klaus Aehlig2017-10-20
| | | | | | | | | | 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
* Fix compile.sh to not hardcode the guava version.Gravatar John Cater2017-10-20
| | | | | Change-Id: I5e946c093499dffd0a34253a5f8e47c49c6a12ec PiperOrigin-RevId: 172686697
* Release notes: correctly strip out none, n/a, noGravatar Damien Martin-Guillerez2017-10-18
| | | | | | | | | | | | | | The previous regex was only matching lines and was not even correctly doing so. We no match everything that is starting with none, n/a or no as a sentence or as a full line. We also match empty string and '.' as a full line. RELNOTES: . RELNOTES: None. RELNOTES: No. Change-Id: I6e85627170ce35e652c90a37e735b7db93c88b4e PiperOrigin-RevId: 172452278
* Ensure that the release notes are not empty if there is no rollbackGravatar Damien Martin-Guillerez2017-10-16
| | | | | | | | | | Because the empty list was returned for the list of hashes to ignore, we matching all the lines in the following grep. By adding a dummy hashes, it ensure that list is never empty and we thus never give a match all pattern. Change-Id: Ic5446c16b56633805e61b24ad71b67029a7b01e3 PiperOrigin-RevId: 172321625
* Release notes test small fixesGravatar Damien Martin-Guillerez2017-10-16
| | | | | | | | - Avoid trap being called when grep is not matching (|| true) - Ensure we always start in master branch Change-Id: I7a71abbdfae7dc2b9680e769ed0322a6a12221dc PiperOrigin-RevId: 172316454
* Remove support for --javabase=<absolute path>.Gravatar lberki2017-10-11
| | | | | | | | | | | | | | | | | | | | | | If an absolute javabase is desired, the following set of rules can be used: java_runtime_suite(name="suite", default=":runtime") java_runtime(name="runtime", java_home=<path to the JDK>) Then --javabase can be pointed to the java_runtime_suite() rule. Alternatively, the java_runtime rule can reference a Make variable: java_runtime(name="runtime", java_home="$(ABSOLUTE_JAVABASE)") Then the Javabase can be specified on the command line like this: --javabase=<your package>:suite --define=ABSOLUTE_JAVABASE=<path to the JDK> RELNOTES[INC]: --javabase=<absolute path> and --host_javabase=<absolute path> are not supported anymore. If you need this functionality java_runtime_suite(name="suite", default=":runtime") java_runtime(name="runtime", java_home=<path to the JDK>) is an alternative. PiperOrigin-RevId: 171798416
* Release notes: exclude no.Gravatar dmarting2017-10-11
| | | | | RELNOTES: No. (test) PiperOrigin-RevId: 171673073
* Clean up TODOs.Gravatar László Csomor2017-10-09
| | | | | | | | | | | | | | | | | | | In this commit: * buildenv.sh: restore its state to that as of commit 511c35b46cead500d4e76706e0a709e50995ceba * CommonCommandOptions.java: remove a deprecated no-op flag * WindowsPathFragment.java: implement an ASCII-only isLetter function, use that instead of Character.isLetter, because the latter returns true for some Unicode characters too * bazel_bootstrap_distfile_test: remove logging that we no longer need, since the bugfix for issue #3618 will be pushed to GitHub later today Change-Id: Ibda70219e974f0c47bc82addc647d8951f4bd701 PiperOrigin-RevId: 171498977
* 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
generated by cgit v1.2.3 (git 2.39.1) at 2024-05-15 18:36:58 +0000