Hi @chris.boley!
I just started testing out the task as well and had the same issue.
It appears that the extension has some interesting logic within it… While I didn’t look at it’s source, I did some investigation and based on the verbose output, I believe the extension is
- Scanning the entire
{Build.SourcesDirectory}directory - Looking for your file w/in that list (instead of simply looking for that path blindly)
In my case, I put my build artifacts into the {Build.ArtifactStagingDirectory} directory, and had to change things in my pipeline to keep the build artifact w/in the {Build.SourcesDirectory} and then reference that path before it would pickup my package…
We should submit a bug for this as it’s very limiting and presumptuous that we can only point to files w/in the sources directory of the pipeline. Hopefully that work around will work for you in the meantime.