You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#7371 added support to finalize the value of Property typed input and output properties of a task when the task starts execution. We should also finalize the value of input and output properties with other types, such as FileCollection, FileTree, DomainObjectCollection and so on.
This fix should only apply to properties without setter methods. Feel free to raise another issue for these properties, though, which we can implement as another increment.
Expected Behavior
No changes to an input or output property of a task are observable once the task has started execution.
This has a number of immediate benefits:
Expensive values are calculated once and then the value reused for task input fingerprinting, snapshotting and by the task action.
The same value is used for each of these things, plus by any tasks that use the task outputs.
This also unblocks potential future performance improvements such as parallel file/directory fingerprinting and isolated task action execution.
Current Behavior
The value of some task input and output properties can be changed during task execution.
The text was updated successfully, but these errors were encountered:
adammurdoch
changed the title
Finalize the value of more task input and output properties when the task starts execution
Finalize the value of more types of task input and output properties when the task starts execution
Oct 18, 2018
This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution.
This issue has been automatically closed due to inactivity. If you can reproduce this on a recent version of Gradle or if you have a good use case for this feature, please feel free to reopen the issue with steps to reproduce, a quick explanation of your use case or a high-quality pull request.
#7371 added support to finalize the value of
Property
typed input and output properties of a task when the task starts execution. We should also finalize the value of input and output properties with other types, such asFileCollection
,FileTree
,DomainObjectCollection
and so on.This fix should only apply to properties without setter methods. Feel free to raise another issue for these properties, though, which we can implement as another increment.
Expected Behavior
No changes to an input or output property of a task are observable once the task has started execution.
This has a number of immediate benefits:
This also unblocks potential future performance improvements such as parallel file/directory fingerprinting and isolated task action execution.
Current Behavior
The value of some task input and output properties can be changed during task execution.
The text was updated successfully, but these errors were encountered: