You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Patrick Rhomberg (JIRA)" <ji...@apache.org> on 2019/04/04 17:12:00 UTC
[jira] [Resolved] (GEODE-6323) Configuration in doFirst and doLast
blocks are not valid for task configuration.
[ https://issues.apache.org/jira/browse/GEODE-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Rhomberg resolved GEODE-6323.
-------------------------------------
Resolution: Fixed
> Configuration in doFirst and doLast blocks are not valid for task configuration.
> --------------------------------------------------------------------------------
>
> Key: GEODE-6323
> URL: https://issues.apache.org/jira/browse/GEODE-6323
> Project: Geode
> Issue Type: Bug
> Components: ci
> Reporter: Patrick Rhomberg
> Assignee: Robert Houghton
> Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> See https://guides.gradle.org/using-build-cache/#suggestions_for_authoring_your_build
> {{doFirst}} and {{doLast}} occur at execution, but the up-to-date state of the task is required at configuration-time. More importantly, these task actions are cacheable and can be returned incorrectly if the declared inputs to the task are unchanged. Notably for {{gfshDepsJar}} and {{depsJar}}, if the {{cp()}} changes, these changes will not be detected and a cached version of the manifest can be used rather than the new intended classpath.
> This is not an issue in the Concourse pipeline, since no cache exists, but it can be troublesome for a developer.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)