Improve error reporting when configuration cache is enabled and task references the output of an artifact transform without declaring this as an input

[adammurdoch]

The user can receive a cryptic internal exception when a task references the output of an artifact transform without declaring this as an input and the configuration cache is enabled.

This case is also broken for vintage builds, and fails in arbitrary ways based on the state of the file system, the tasks that are currently running and the transform implementation.

This is essentially a special case of the more general situation, where a task references the output of some other task or transform (or any work) without declaring that as an input.

Expected Behavior

Inform the user that this situation will not work. There are many options for implementing this, ranging from just improving the error message for this specific case (transform outputs + configuration cache) through to deprecating all cases where a task uses the output of some other task or work without declaring this as an input for both vintage and configuration cache builds.

Current Behavior

Writing to the configuration cache fails with a cryptic internal exception, when configuration cache is enabled and fails in different ways when not enabled.

[stale]

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.