When using Azure DevOps build (in my case on a public agent), it seems to be a bit dubious to fill my filelist.txt with a fixed path (D:\a\1\a\.exe) on each line, while that path is not quaranteed.
Is there a way to use -ifl parameter with AzureDevOps, i.e. using a base-path as parameter or a pipelinevariable $(build.artifactstagingdirectory)? For now I've added all files as individual parameters. This works, but isn't as maintainable as we would like.
In sourcecode I found that wildcards are supported, but passing with wildcard () like `$(build.artifactstagingdirectory)\folder\prefix..exeis not accepted (output:File 'D:\a\1\a\folder\prefix.*.exe' does not exist.`)
When checking sourcecode, I found the SignCommand.AllFiles-property, with does a Matcher.Execute on Directory '.'. So there seems to be no way to specify a root-directory, and using wildcards results in results.HasMatches to be false.
When using Azure DevOps build (in my case on a public agent), it seems to be a bit dubious to fill my filelist.txt with a fixed path (D:\a\1\a\.exe) on each line, while that path is not quaranteed.
Is there a way to use -ifl parameter with AzureDevOps, i.e. using a base-path as parameter or a pipelinevariable
$(build.artifactstagingdirectory)? For now I've added all files as individual parameters. This works, but isn't as maintainable as we would like.In sourcecode I found that wildcards are supported, but passing with wildcard () like `$(build.artifactstagingdirectory)\folder\prefix..exe
is not accepted (output:File 'D:\a\1\a\folder\prefix.*.exe' does not exist.`)When checking sourcecode, I found the
SignCommand.AllFiles-property, with does a Matcher.Execute on Directory '.'. So there seems to be no way to specify a root-directory, and using wildcards results inresults.HasMatchesto befalse.Any ideas on this topic?