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

["Luke Cwik (JIRA)" <ji...@apache.org>]

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

Luke Cwik commented on BEAM-4400:
---------------------------------

How do we ensure that tasks correctly label their inputs and outputs so that the task cache correctly says that a task doesn't need to run?

> 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: Minor
>
> 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
(v7.6.3#76005)