[
https://issues.apache.org/jira/browse/BEAM-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16506459#comment-16506459
]
Scott Wegner commented on BEAM-4400:
------------------------------------
Bummer. Another possibility would be to setup our own build cache node without
worrying about Jenkins integration. According to the [Gradle
docs|https://docs.gradle.org/current/userguide/build_cache.html#sec:build_cache_setup_http_backend],
the have a Docker image that makes setup straight-forward. If we could host
this on GCE co-located with our Jenkins machines the network overhead shouldn't
be too expensive.
> 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)
