summaryrefslogtreecommitdiffstats
path: root/ci
Commit message (Collapse)AuthorAgeFilesLines
* Remove auto-detection of Python toolchain from MODULE.bazel (#4582)v1.15.1Derek Mauro2024-07-311-1/+6
| | | | | | | | | | | since it affects downstream users The correct solution appears to be https://rules-python.readthedocs.io/en/stable/toolchains.html#library-modules-with-dev-only-python-usage This change also includes a workaround for the new mechanism creating paths that are too long for Windows to handle. Backport of 3e3b44c300b21eb996a2957782421bc0f157af18
* Update GoogleTest CI Docker image to use Clang 19, GCC 14, and CMake 3.29.3Derek Mauro2024-05-241-1/+1
| | | | | PiperOrigin-RevId: 636977286 Change-Id: Id9e09398a991c74c2137672948a1eb7dd2d96596
* Add support for Bzlmod for the next releaseDerek Mauro2024-01-253-2/+7
| | | | | | | | | | | | | | | | | | | https://bazel.build/external/overview#bzlmod Bzlmod will be the default in a future Bazel release. By default it requires projects to be registered with the Bazel Central Registry (https://registry.bazel.build/) and thus uses regular releases by default. Users that want to "live-at-head" can still do this through with overrides (https://bazel.build/external/module#overrides). This change updates GoogleTest dependencies to use released versions. CI uses Bzlmod except in the case of linux_gcc-floor, which will keep testing the old WORKSPACE-based dependency system. PiperOrigin-RevId: 601489729 Change-Id: I6be52034eba0d0e5fe12110e5e82879305cf73ff
* Update CI builds to use Bazel 7.0.0Derek Mauro2024-01-093-7/+5
| | | | | | | --features=external_include_paths has been removed from Windows builds since it appears cause build command errors currently PiperOrigin-RevId: 597020418 Change-Id: Ie37be0d05f3a154ab0d3c3f7d39b4e2c0ed650a3
* CI: Update the Linux hybrid-latest docker container used for testingDerek Mauro2023-08-211-1/+1
| | | | | | | | | | | The following are the major updates * LLVM 17 branch (https://github.com/llvm/llvm-project b744f4c99cf91155c74a3c92db6f1335232ff3d) * GCC 13.2 * CMake 3.27.1 * Bazel 6.2.1 PiperOrigin-RevId: 558818264 Change-Id: Ib08d8331e2a8b2d68a702670451beaaac5d266f4
* Remove the Win64 arch from the CMake Generator sinceDerek Mauro2023-03-281-5/+5
| | | | | | | | | | | this can't be used with MSVC 2022 We also have to use Python 3.4 since that is what the base image has, however, I will create a new image soon that has a modern version of Python. PiperOrigin-RevId: 520010732 Change-Id: Icf2420fd97d2bbc310382a17793045b6e16d62bb
* Migrate CI builds to MSVC 2022Derek Mauro2023-03-271-9/+11
| | | | | PiperOrigin-RevId: 519792199 Change-Id: Ic821b264bf1aef5e03f22fb0e288dd9d56fd536b
* Add -Wundef to the CI scripts when building with BazelTom Hughes2023-03-072-0/+4
| | | | | | | | The CMake build already adds -Wundef for gcc/clang. This change makes sure that the gcc/clang Bazel builds also compile correctly with -Wundef (#3267). PiperOrigin-RevId: 514864451 Change-Id: I7798a4a4c68d037e23625db24ee29df454367734
* Update googletest's test docker containersDino Radakovic2023-02-221-2/+2
| | | | | PiperOrigin-RevId: 511500508 Change-Id: Ib686f93d317b95ac9b9bcb0a5566500316ba1929
* Fix compiler flags in Linux presubmitTom Hughes2023-02-021-1/+1
| | | | | | | | | | CXX_FLAGS should be CXXFLAGS and the quoting was wrong. As a result, "-Werror -Wdeprecated" was not being applied. https://cmake.org/cmake/help/latest/envvar/CXXFLAGS.html PiperOrigin-RevId: 506656655 Change-Id: Ic5e861be3b9c32257eb9aabb845c931f3cba7122
* Add Windows CI scriptDino Radakovic2022-10-171-0/+56
| | | | | PiperOrigin-RevId: 481680362 Change-Id: I87b2b71427a8ad2603f5445d6ef794c3fa84746e
* Rollback 4fa8cfe3f4dee8975ee02d98633a5245ab67c6d7Derek Mauro2022-09-132-0/+2
| | | | | | | Breaks the intended C++ version on some CI builds PiperOrigin-RevId: 474022587 Change-Id: I41a58893802c90864e0f2cc3d15e6c169c59146d
* bazel: move -std=c++14 to .bazelrcrefs/pull/3984/headKeith Smiley2022-08-192-2/+0
| | | | Bazel defaults to -std=c++11 on macOS which gtest doesn't support.
* Add --features=external_include_paths to Bazel CI to ignore warningsDerek Mauro2022-08-122-0/+4
| | | | | | | from dependencies PiperOrigin-RevId: 467244441 Change-Id: Iefa65474d8c62e7c4c942957dc8e275715076e5f
* Remove the Bazel provided default cxxopt -std=c++0x and replace itDerek Mauro2022-07-011-0/+1
| | | | | | | with -std=c++14 when testing with GCC 5. PiperOrigin-RevId: 458502826 Change-Id: I83637a222b5c0a54e55d93ce7fdbc878af27b250
* Remove support for C++11Derek Mauro2022-06-302-4/+5
| | | | | | | | v1.12.x is the last branch to support C++11 Future releases will require at least C++14 PiperOrigin-RevId: 458250106 Change-Id: Ibee2248649ff3c13daaa179135887848bf730f3f
* Update GCC floor container used by CI to fix the Bazel cache errorDerek Mauro2022-06-211-1/+2
| | | | | PiperOrigin-RevId: 456323043 Change-Id: I86e3d52b72b51c2d4e96f536daa7f84a52c598f5
* Merge pull request #3797 from glandium:issue3514Copybara-Service2022-04-261-0/+3
| | | | | PiperOrigin-RevId: 444444700 Change-Id: I8ac5cc96cc6eb9d583fa7e3fb304ef3dcaa95b5b
* Update GCC/Clang Linux tests to use Bazel 5.0.0Derek Mauro2022-02-171-1/+1
| | | | | PiperOrigin-RevId: 429400664 Change-Id: I6454cf52cb2fc616a96663823de997591b63dfae
* Update test Docker image to GCC 11.2, Clang 14 (prerelease),Derek Mauro2022-01-141-1/+1
| | | | | | | CMake 3.22.1, and Bazel 4.2.2 PiperOrigin-RevId: 421814198 Change-Id: Ief4e39d7f077089f10afdc8d63cc1e51dc18e97f
* Googletest exportAbseil Team2021-10-131-2/+2
| | | | | | | | Use newer Docker images in CI The new floor image contains GCC 5.5.0, like the old one. PiperOrigin-RevId: 402402465
* Googletest exportdmauro2021-06-021-1/+3
| | | | | | | | Updates Linux docker image to use Bazel 4.1.0 and GCC 11.1 Updates Bazel dependencies Removes the last usage of the deprecated and removed Python2 PiperOrigin-RevId: 375759184
* Googletest exportAbseil Team2021-04-092-8/+12
| | | | | | Generalize root directory in CI scripts PiperOrigin-RevId: 367628939
* Googletest exportAbseil Team2021-03-092-0/+193
| | | | | | Add CI test scripts PiperOrigin-RevId: 360931988
* Googletest exportdmauro2021-02-058-330/+0
| | | | | | | Disable Travis CI. The migration to travis-ci.com is incompatible with security policy. These tests are now run on Kokoro. PiperOrigin-RevId: 355438343
* Googletest exportdmauro2021-01-142-7/+0
| | | | | | | Remove platformio tests. This currently uses gcc 4.8.2 which is no longer supported. PiperOrigin-RevId: 351667999
* Googletest exportdmauro2020-12-023-17/+6
| | | | | | Fix the TravisCI build by updating the required tools PiperOrigin-RevId: 344882646
* Googletest exportdmauro2020-05-283-4/+3
| | | | | | Update Travis CI to use Ubuntu Bionic in some cases PiperOrigin-RevId: 313639562
* Merge pull request #2797 from Jyun-Neng:masterGennadiy Rozental2020-05-011-15/+0
|\ | | | | | | PiperOrigin-RevId: 307604377
| * Remove duplicate codes existed in get-nprocessors.shrefs/pull/2797/headJi Jyun-Neng2020-04-041-15/+0
| |
* | Fix a typo in .travis.ymlrefs/pull/2772/headArthur O'Dwyer2020-03-281-5/+5
|/ | | | | | | | | | | | | | The old code was trying to pass -Wgnu-zero-variadic-macro-arguments as part of CXXFLAGS, but it forgot the quotation marks needed around whitespace. This meant that option was ignored: https://travis-ci.org/github/google/googletest/jobs/666534177#L760 Unfortunately, the codebase is not remotely clean with respect to that warning option. It fails like this: https://travis-ci.org/github/Quuxplusone/googletest/jobs/668118135 So, remove that failing configuration from the test matrix until someone has time to look at it.
* Googletest exportmisterg2019-09-291-1/+1
| | | | | | fix OSS Travis Builds -remove hardcoded updated package from brew PiperOrigin-RevId: 271863378
* Googletest exportmisterg2019-08-161-0/+1
| | | | | | Stop depending on the abseil master PiperOrigin-RevId: 263789087
* Googletest exportmisterg2019-06-181-4/+1
| | | | | | | Move Googletest OSS bazel builds to latest bazel. The latest bazel ( 0.27.0 as of now ) does not run on trusty. PiperOrigin-RevId: 253829774
* Fixing CI break by going to bazel 0.26.1refs/pull/2290/headGennadiy Civil2019-06-171-1/+4
|
* Finish removing autotoolsGennadiy Civil2019-06-131-44/+0
|
* Googletest exportmisterg2019-02-1211-0/+407
| | | | | | Internal Change PiperOrigin-RevId: 233614147
* Googletest exportAbseil Team2019-02-1211-407/+0
| | | | | | Internal change PiperOrigin-RevId: 232362580
* Test out changes with clang/OSX each PR using Travis CIrefs/pull/2100/headEnji Cooper2019-02-042-2/+9
| | | | | | | | | | | | | | | | | | | | | | | This will help ensure that test coverage isn't missed when changes that can impact OSX with clang are submitted. Although not perfect, testing changes on OSX with clang is an ok proxy [for now] for testing changes on FreeBSD with clang (testing on FreeBSD is non-trivial, as Travis CI doesn't support operating systems other than Linux and OSX). In order to support this, install the packages via homebrew using a `addons::homebrew::packages` block (similar to `addons::apt::packages` for Ubuntu), as documented in the Travis CI docs ( https://docs.travis-ci.com/user/installing-dependencies/ ). While here, try pushing apt* calls into the Travis config for Ubuntu, instead of delaying the equivalent calls in the `ci/*.sh` scripts. Keep the `ci/*.sh` scripts for ease of testing locally (and extend the OSX one to install gcc 4.9 and llvm 3.9, like the travis config does). In order to accomodate this change (and because the homebrew package for llvm@3.9 doesn't automatically add clang*-3.9 to `$PATH`), `$PATH` needs to be adjusted to find the llvm@3.9 toolchain. Signed-off-by: Enji Cooper <yaneurabeya@gmail.com>
* feat: Add initial support for PlatformIO and ArduinoChris Johnson2018-12-052-0/+7
|
* fix typoRyan Yee2018-10-111-1/+2
|
* Revert "Add clang format check to one of the builds"refs/pull/1863/headGennadiy Civil2018-09-251-33/+0
|
* typorefs/pull/1857/headGennadiy Civil2018-09-251-0/+0
|
* Add clang format check to one of the builds to provide indication that ↵Gennadiy Civil2018-09-251-0/+33
| | | | formatting is incorrect
* Changing clang tp 3.9 as 3.7 no longer works on TravisGennadiy Civil2018-08-303-3/+3
|
* Add no-exception and no-rtti to build matrixrefs/pull/1589/headScott Graham2018-05-011-0/+8
|
* Merges and also adding new bazel build moderefs/pull/1435/headGennadiy Civil2018-01-311-0/+1
|
* Build both googletest and googlemock.Carlos O'Ryan2017-12-241-2/+0
|
* Create a autotools-based build for Travis.Carlos O'Ryan2017-12-243-0/+96
| | | | When this build works, we know the autoconf support is working.
* Implement bazel-based builds in Travis.Carlos O'Ryan2017-12-097-0/+289
This refactored test build scripts to enable bazel-build scripts in Travis.
generated by cgit v0.12 at 2025-04-04 20:03:40 (GMT)