[jira] [Commented] (BEAM-4400) Integrate Jenkins Job Cacher Plugin for improved build caching

["Kenneth Knowles (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BEAM-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17156881#comment-17156881 ] 

Kenneth Knowles commented on BEAM-4400:
---------------------------------------

From the tutorials {{clean}} is not expected to affect the build cache.

We should view tasks with bad inputs/outputs as bugs. If the cache serves a result based on inputs, the cache is working correctly.

> Integrate Jenkins Job Cacher Plugin for improved build caching
> --------------------------------------------------------------
>
>                 Key: BEAM-4400
>                 URL: https://issues.apache.org/jira/browse/BEAM-4400
>             Project: Beam
>          Issue Type: Improvement
>          Components: build-system
>            Reporter: Scott Wegner
>            Priority: P3
>
> 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.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)