Need Wild cards support in Report Files Path

[rp557rajendra]

I have various reports with logical grouping under $(Build.SourcesDirectory) as below. I have tried various match pattern options on Report Files Path to do deployment but in vain.

Reports source folder path $(Build.SourcesDirectory)*grp1*\bin\release\1.rdl $(Build.SourcesDirectory)*grp1*\bin\release\2.rdl $(Build.SourcesDirectory)*grp2*\bin\release\3.rdl $(Build.SourcesDirectory)*grp3*\bin\release\4.rdl

Few of Match Patterns I have tried *\bin* *\bin\release* $(Build.SourcesDirectory)*\bin*

However, I have found a workaround for this. Usage of the VSTS COPY FILES task with FLATTEN FOLDERS option can resolve it. Would be great, if you can fix this issue in your DEPLOY SSRS task with the match patterns?

[rp557rajendra]

Any update on this?

[mmajcica]

Hi, it was not in my plans to implement such a feature. You are always welcome to submit a PR.

[steveosacky]

This feature is not working as it is described in the extension. Wildcards can be used. For example, **/*.rdl for RDL files present in all sub folders. I have used $(System.DefaultWorkingDirectory)/$(Build.DefinitionName)/Reports Folder/**/*.rdl AND $(System.DefaultWorkingDirectory)/$(Build.DefinitionName)/Reports Folder/*.rdl These both return an invalid path error.

[rp557rajendra]

I have found a workaround for this. Usage of the VSTS COPY FILES task with FLATTEN FOLDERS option can resolve it.That did trick for me.

[mwhisler]

Wildcard support doesn't work for me either. Feels like something got missed here. I'm going to have to use other file copy tasks in the pipeline to arrange the RDL files in a single directory before calling the SSRS deploy.