Improve Travis CI build Performance #1307
Conversation
|
Is this the problem you described building with java 8? However, improving performance is good. |
The CI test takes the Gradle build as default, where I have defined a minimum test coverage of 0.84 (which will be reported with Java 11). For any reason, with Java 8 we achieve only 0.834. Solution is to a) increase the Test Coverage (which I have done in the pending PR) and also b) to define the minimum coverage based on Java 8 (which I have done in the pending PR). |
|
gradle can also be cached |
Provided by @YunLemon via PR JSQLParser#1307
|
Thank you so much, I have incorporated your suggestions into PR #1329 -- but attributed all credits to you. |
* Implement caching of the Gradle and Maven files Provided by @YunLemon via PR #1307 * Fix CREATE TABLE AS SELECT ... UNION SELECT ... Provided by @fanchuo via PR #1309 * Fix #1316 Add more specific tests verifying the nature of the UpdateSets Allow "SELECT *" (without FROM) to parse, its a valid SELECT statement * Add the enhancements since Release 4.1 * Adjust the Coverage * Improve Test Coverage * Revert the Special Oracle Tests (accidentally set to FAILURE) Co-authored-by: Tobias <t.warneke@gmx.net>
|
@YunLemon: Your change has been merged into MASTER via PR #1329. Thank you again for the improvement. |
Caching Dependencies and Directories Travis CI can cache content that does not often change, to speed up the build process.
=====================
If there are any inappropriate modifications in this PR, please give me a reply and I will change them.