From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

Inputs can be marked as @Internal to avoid being part of cache key.

That's true but can't that only be done at the definition of the task, i.e by the google proto plugin. Or is there a way for me to configure an existing task?

which property appears to be problematic?  See many properties on GenerateProtoTask (assuming that’s the one), some of which are @Internal relating to executables.

For example, the code to find protoc is:
``` String protocPath = computeExecutablePath(protocLocator.get())
    List&lt;String&gt; baseCmd = [ protocPath ]
    baseCmd.addAll(dirs)```
…based off of protocLocator:
```  @Internal("Input captured by getExecutables()")
  abstract Property&lt;ExecutableLocator&gt; getProtocLocator()```

In the latest version it is the 'alternativePaths' property. For me it picks up a windows exe which has some hash, while on CI it picks up a linux exe which has a different hash.

And yep, that's the correct task

hmm.  all those appear to be `@Internal`.  There is `getSnapshotArtifacts` that uses the alternate paths, however, perhaps that is the problem.  Not aware of a way to override those annotations outside the task.

Oh! Sorry, I see. I was referring to the latest released version. Indeed in master they seem to have 'fixed' it. So it sounds like I just need to wait for a release

aha and they even have a commit which is detailing exactly my case. <https://github.com/google/protobuf-gradle-plugin/commit/8df229f8dc8e4521882fbf69806ab91ba4d51d5e>

Thanks again! Hopefully it's not too long for a release this will be very valuable for me.

As a work-around as far as I remember, you would make a subclass of that task, there override the property in question and give it the annotation you want it to have.

<@U0383QKNG3C> just worked on this! Please push Google to make a release if you have any channels available with them.