kennknowles opened a new issue, #18849: URL: https://github.com/apache/beam/issues/18849
See discussion on [dev](https://lists.apache.org/thread.html/c59289787c665c7732df4095bda0877637eee59e3add4d26a11f6b7f@%3Cdev.beam.apache.org%3E). With the new Gradle build, we are now able to build incrementally, but are not yet taking advantage of it on Jenkins. This would give us the benefit of much faster pre-commits for files that aren't changed. For example, A change in the Python which doesn't touch any Java would not need to re-run Java pre-commits. By default, Gradle uses a build cache local to the workspace, and in Jenkins the workspace gets nuked on each build. There is a [Jenkins Job Cacher Plugin](https://wiki.jenkins.io/display/JENKINS/Job+Cacher+Plugin) which solves this exact plugin and integrates with Gradle's build cache support. I believe all we need to do is enable and configure this plugin to realize the benefits of incremental builds. To enable the plugin, we likely need to reach out the Apache INFRA team. Imported from Jira [BEAM-4400](https://issues.apache.org/jira/browse/BEAM-4400). Original Jira may contain additional context. Reported by: swegner. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
