This message was deleted.

The name you give there is only for storing the hash under a name and when reporting it somewhere like in

-i

output. You cannot reference the output under that name, at least not as far as I know. But luckily as the file is your only output of the task, just use the task itself as input for the next task.

Thank you for the help! I'll be sure next time to post in the community-support channel. I also could not seem to find a way to reference the output of a task in another task using the name. I read under the Runtime API section in the docs

In fact, the runtime API has almost feature parity with the annotations. All it lacks is an equivalent for @Nested.

, so I figured that there was a way to do this and have been searching for a long time. In my case I am only outputting a single file so I'll just do your recommendation, thanks again!

You can delare some local variable that is a

RegularFileProperty

that you then register as output and also give the other task as input. So there are ways, but most often it is much cleaner and nicer to just create a new class. Besides that I'm not sure whether the local variable way would then add implicit task dependencies properly.