flasn4nt
/
grpc-java
mirror of https://github.com/grpc/grpc-java.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
grpc-java/.travis.yml

61 lines
2.0 KiB
YAML
Raw Normal View History

Revert "Draft of Android specific Channe builder" This reverts commit d6dc790f05c90ffba2c7a4356121ae4d586e467e.
2015-09-05 04:26:24 +08:00
language: java
Basic travis configuration
2015-03-19 07:31:38 +08:00
env:
global:
Limit memory during build When running :grcp-interop-testing:test, Travis has been hanging on OS X or flaking on Linux with: > Process 'Gradle Test Executor 4' finished with non-zero exit value 137 Exit code 137 indicates SIGKILL (128 + 9) and is most likely caused by the JVM being killed by the kernel's OOM killer. The limit in .travis.yml is 2x what was necessary to do a parallel build. The main test memory limit in build.gradle is well above 16m which is necessary for the tests. Interop-testing is well above 64m which is necessary for interop-testing, but we use 1.5g to help prevent timeouts on Travis. Protobuf and protobuf-nano each have one tests that decodes a proto >64M in size, which prevents them from running with less than 512m and 768m, respectively.
2016-02-13 00:48:41 +08:00
- GRADLE_OPTS=-Xmx512m
Allow cache to be shared between Linux and OS X It doesn't appear that OS X is saving its cache yet, so this may not be needed in the future, but for now we need OS X to avoid attempting to use the Linux binaries.
2016-04-28 06:23:35 +08:00
- LDFLAGS=-L/tmp/protobuf/lib
- CXXFLAGS=-I/tmp/protobuf/include
- LD_LIBRARY_PATH=/tmp/protobuf/lib
Basic travis configuration
2015-03-19 07:31:38 +08:00
Working Travis build, with caching of deps
2015-03-21 01:26:00 +08:00
before_install:
travis: Use default Maven settings Throw away Travis-CI's custom Maven settings, because they are causing massive CI failures when Maven slows to a crawl/hangs because of failures contaicting repository.apache.org. Travis-CI's settings includes repo.maven.apache.org, oss.sonatype (releases and snapshots), and repository.apache.org (releases and snapshots). Now we will just be using Maven's default, which may just be repo.maven.apache.org.
2018-08-18 08:03:50 +08:00
- rm ~/.m2/settings.xml || true # Avoid repository.apache.org, which has QPS limits and is useless
travis: Avoid $HOME in cache, since it varies $HOME can be different between different platforms/configurations, so using /tmp means the path is consistent and be shared in the caches.
2016-04-30 06:07:22 +08:00
- mkdir -p $HOME/.gradle/caches &&
ln -s /tmp/gradle-caches-modules-2 $HOME/.gradle/caches/modules-2
- mkdir -p $HOME/.gradle &&
ln -s /tmp/gradle-wrapper $HOME/.gradle/wrapper
buildscripts: make unix.sh and make_dependencies.sh arch aware (#4384) ARCH can be '32' or '64'. If it is not set then default to '64'. make_dependencies.sh should do the symlinking
2018-04-28 06:59:16 +08:00
- buildscripts/make_dependencies.sh # build protoc into /tmp/protobuf
Allow checkstyle failures fatal, and fix last issues Failing disabled by default, but setting checkstyle.ignoreFailures=false in ~/.gradle/gradle.properties enables failing. Travis will always run with such failing enabled.
2015-03-22 01:59:17 +08:00
- mkdir -p $HOME/.gradle
- echo "checkstyle.ignoreFailures=false" >> $HOME/.gradle/gradle.properties
travis,jenkins: Fail build if javac emits warnings
2016-07-11 02:40:12 +08:00
- echo "failOnWarnings=true" >> $HOME/.gradle/gradle.properties
all: Enable ErrorProne during compilation ErrorProne provides static analysis for common issues, including misused variables GuardedBy locks. This increases build time by 60% for parallel builds and 30% for non-parallel, so I've provided a way to disable the check. It is on by default though and will be run in our CI environments.
2017-02-25 06:53:23 +08:00
- echo "errorProne=true" >> $HOME/.gradle/gradle.properties
Basic travis configuration
2015-03-19 07:31:38 +08:00
Add tests for nano proto Since some of the tests would need only minor modification to work for normal proto, normal proto got a few more tests as well.
2015-10-28 10:53:18 +08:00
install:
all: Stop committing generated protobuf messages This commit swaps to using a Sync task to place generated code in the src/generated folder instead of the gradle-protobuf-plugin's generatedFilesBaseDir. This provides much nicer results on failed builds, and you will no longer see all the generated files deleted. But at the same time the Sync task makes it easy to only copy the grpc-generated code. This was not previously done because we were lazy and using generatedFilesBaseDir, which made it difficult to treat the services differently from the messages.
2018-10-25 05:25:22 +08:00
- ./gradlew assemble syncGeneratedSources publishToMavenLocal
examples: Provide Maven and Gradle build files The examples are no longer part of the normal build, although they are built with Travis. The examples now include their own copy of the gradle wrapper to ease usage from IDEs which can now properly detect the correct version of gradle to use. The build files were generated using "gradle init" and "mvn archetype:generate" and then modified following our README. Fixes #1414
2016-06-25 09:18:06 +08:00
- pushd examples && ./gradlew build && popd
- pushd examples && mvn verify && popd
all: remove copies of gradle wrapper
2018-12-12 08:23:28 +08:00
- pushd examples/example-alts && ../gradlew build && popd
examples: move TLS example to a separate project
2018-12-07 04:03:25 +08:00
- pushd examples/example-tls && ../gradlew clean build && popd
all: remove copies of gradle wrapper
2018-12-12 08:23:28 +08:00
- pushd examples/example-kotlin && ../gradlew build && popd
Add tests for nano proto Since some of the tests would need only minor modification to work for normal proto, normal proto got a few more tests as well.
2015-10-28 10:53:18 +08:00
Fail travis build if codegen isn't committed This doesn't catch 100% of such problems, as it runs before tests have been run. However, almost all of our protos are used in 'main' so this limitation shouldn't be a big deal. If it does become a problem, we change it from 'before_script' to 'script', but then we'll also need to include gradle build instructions.
2015-05-08 08:00:44 +08:00
before_script:
- test -z "$(git status --porcelain)" || (git status && echo Error Working directory is not clean. Forget to commit generated files? && false)
Add support for codecov.io Codecov.io provides patch-based code coverage, so you can easily know how many of the added lines are covered. It also has a more useful UI. Unfortunately, the percentage it reports does not include partially- covered lines--those with uncovered conditions. Thus the reported percentage is about 6% lower than the coverage we've been looking at previously. Because of this alone, I don't expect to remove coveralls support soon. Use the bash script instead of python module since pip isn't available by default on Travis OS X. jacocoTestReport uses mustRunAfter (contrary to the docs; see https://issues.gradle.org/browse/GRADLE-2960) to make sure it runs after all tests, only if testing is taking place. We would like :grpc-all:jacocoTestReport to behave the same way. Without it, we would need two separate invocations of gradle (adding ~1m to Travis run) in order to prevent getting random results depending on what tests just so happened to have been run.
2016-02-14 06:43:38 +08:00
script:
- ./gradlew check :grpc-all:jacocoTestReport
Add coveralls support
2015-08-08 09:02:31 +08:00
after_success:
Fix compilation in Java 9
2018-03-29 08:13:39 +08:00
# Upload to coveralls once, instead of for each job in the matrix
travis.yml: Actually trigger coveralls Previously it was just erroring: [[: command not found This has been broken since #3638
2018-07-31 03:44:35 +08:00
- if [[ "$TRAVIS_JOB_NUMBER" == *.1 ]]; then ./gradlew :grpc-all:coveralls; fi
Add support for codecov.io Codecov.io provides patch-based code coverage, so you can easily know how many of the added lines are covered. It also has a more useful UI. Unfortunately, the percentage it reports does not include partially- covered lines--those with uncovered conditions. Thus the reported percentage is about 6% lower than the coverage we've been looking at previously. Because of this alone, I don't expect to remove coveralls support soon. Use the bash script instead of python module since pip isn't available by default on Travis OS X. jacocoTestReport uses mustRunAfter (contrary to the docs; see https://issues.gradle.org/browse/GRADLE-2960) to make sure it runs after all tests, only if testing is taking place. We would like :grpc-all:jacocoTestReport to behave the same way. Without it, we would need two separate invocations of gradle (adding ~1m to Travis run) in order to prevent getting random results depending on what tests just so happened to have been run.
2016-02-14 06:43:38 +08:00
- bash <(curl -s https://codecov.io/bash)
Basic travis configuration
2015-03-19 07:31:38 +08:00
os:
- linux
Support OS X on Travis
2015-10-16 05:52:24 +08:00
Fix compilation in Java 9
2018-03-29 08:13:39 +08:00
jdk:
Update net.ltgt.errorprone to 0.6 and enable Error Prone on JDK 10+
2018-12-14 02:17:06 +08:00
- oraclejdk8
Add build support for Java 11 It appears everything was already working on Java 11, except build-specific and testing issues. Updating to Netty 4.1.30 (#4940) probably fixed the last true Java 11 incompatibility. Fixes #4933
2018-10-18 02:49:30 +08:00
- openjdk11
Fix compilation in Java 9
2018-03-29 08:13:39 +08:00
Basic travis configuration
2015-03-19 07:31:38 +08:00
notifications:
Working Travis build, with caching of deps
2015-03-21 01:26:00 +08:00
email: false
cache:
directories:
travis.yml: Fix protobuf compilation caching Wildcard apparently doesn't work... silently. Move versions into their own directory so we can use a hard-coded string in the travis configuration.
2018-07-31 07:31:12 +08:00
- /tmp/protobuf-cache
travis: Avoid $HOME in cache, since it varies $HOME can be different between different platforms/configurations, so using /tmp means the path is consistent and be shared in the caches.
2016-04-30 06:07:22 +08:00
- /tmp/gradle-caches-modules-2
- /tmp/gradle-wrapper
Cache Gradle and not really Maven Artifacts that Gradle caches from Maven Central go in ~/.gradle/caches/modules-2, not ~/.m2. We only need .m2 for the locally-installed Netty.
2015-03-21 03:03:48 +08:00
before_cache:
travis: Avoid $HOME in cache, since it varies $HOME can be different between different platforms/configurations, so using /tmp means the path is consistent and be shared in the caches.
2016-04-30 06:07:22 +08:00
# The lock changes based on folder name; normally $HOME/.gradle/caches/modules-2/modules-2.lock
- rm /tmp/gradle-caches-modules-2/gradle-caches-modules-2.lock
Remove stray character that hinded Travis cache
2015-04-29 22:56:04 +08:00
- find $HOME/.gradle/wrapper -not -name "*-all.zip" -and -not -name "*-bin.zip" -delete