[GitHub] [flink] 1u0 opened a new pull request #9065: [FLINK-13102][travis] Optimize some travis stages by skipping mvn verify if possible

[GitBox <gi...@apache.org>]

1u0 opened a new pull request #9065: [FLINK-13102][travis] Optimize some travis stages by skipping mvn verify if possible
URL: https://github.com/apache/flink/pull/9065
 
 
   ## What is the purpose of the change
   
   This PR minimizes total Travis CI time for pull request triggered builds by skipping `mvn verify` steps for non `python` and `misc` jobs in Travis `test` stage.
   
   ## Brief change log
   
     - added script to build `mvn` dependencies tree and list all changed files in a PR build run. This happens at the very first `compile` stage;
     - added script to detect if `mvn verify` can be skipped for given list of maven modules and list of changed files.
   
   ## Verifying this change
   
   This change can be verified as follows:
   
     - run different PRs (build in Travis CI) with this changes included and manually verifying that build is correct and some tests are not run because changes in a PR are not affecting them.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (yes / **no**)
     - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (yes / **no**)
     - The serializers: (yes / **no** / don't know)
     - The runtime per-record code paths (performance sensitive): (yes / **no** / don't know)
     - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / **no** / don't know)
     - The S3 file system connector: (yes / **no** / don't know)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (yes / **no**)
     - If yes, how is the feature documented? (**not applicable** / docs / JavaDocs / not documented)
   

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services