jtstorck opened a new pull request #3644: NIFI-5505 Added Java 11 build to 
Travis CI
URL: https://github.com/apache/nifi/pull/3644
 
 
   ```
   Introduced stages to cache dependencies before build and test
   Added --fail-never to dependency cache stage to allow dependency:go-offline 
to finish and update the cache with any dependencies that were able to be 
downloaded
   Added download of AdoptOpenJDK 11.0.4 for the Java 11 build
   Removed setting environment variables to enable easier sharing of cache 
between build, region/language settings are passed in via the command line when 
invoking maven
   Formatted scripts to allow multiline commands for more readability
   Replaced "exit ${PIPESTATUS[0]}" with "test ${PIPESTATUS[0]} -eq 0" to avoid 
using "exit" in script, which prevents Travis from completing the cache upload 
after the build completes
   Install Maven 3.6.1 for the -ntp (no-transfer-progress) feature
   Only runs dependency cache stages if the .m2 repository does not exist
   Updated all build stages to exclude non-api nar and assembly modules to 
decrease build time
   ```
   ----
   To verify this PR, Travis should have a completed build, with two stages 
executed to download and cache dependencies for openjdk8 and non-explicit-jdk 
Cache stages, and four stages for the various locale and JDK version builds.
   
   Please be aware that the four stages which build and test the code exclude 
assembly and -nar modules to decrease build time, so that all stages can finish 
in less than 50 minutes.
   
   ----
   Thank you for submitting a contribution to Apache NiFi.
   
   Please provide a short description of the PR here:
   
   #### Description of PR
   
   _Added Java 11 build to Travis CI._
   
   In order to streamline the review of the contribution we ask you
   to ensure the following steps have been taken:
   
   ### For all changes:
   - [x] Is there a JIRA ticket associated with this PR? Is it referenced 
        in the commit message?
   
   - [x] Does your PR title start with **NIFI-XXXX** where XXXX is the JIRA 
number you are trying to resolve? Pay particular attention to the hyphen "-" 
character.
   
   - [x] Has your PR been rebased against the latest commit within the target 
branch (typically `master`)?
   
   - [x] Is your initial contribution a single, squashed commit? _Additional 
commits in response to PR reviewer feedback should be made on this branch and 
pushed to allow change tracking. Do not `squash` or use `--force` when pushing 
to allow for clean monitoring of changes._
   
   ### For code changes:
   - [x] Have you ensured that the full suite of tests is executed via `mvn 
-Pcontrib-check clean install` at the root `nifi` folder?
   - [n/a] Have you written or updated unit tests to verify your changes?
   - [n/a] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
   - [n/a] If applicable, have you updated the `LICENSE` file, including the 
main `LICENSE` file under `nifi-assembly`?
   - [n/a] If applicable, have you updated the `NOTICE` file, including the 
main `NOTICE` file found under `nifi-assembly`?
   - [n/a] If adding new Properties, have you added `.displayName` in addition 
to .name (programmatic access) for each of the new properties?
   
   ### For documentation related changes:
   - [n/a] Have you ensured that format looks appropriate for the output in 
which it is rendered?
   
   ### Note:
   Please ensure that once the PR is submitted, you check travis-ci for build 
issues and submit an update to your PR as soon as possible.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to