Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AzureResourceGroupDeployment@2 csmFile path not working if template artifact location contains space characters #11673

Closed
petegrimsdale opened this issue Oct 31, 2019 · 4 comments

Comments

@petegrimsdale
Copy link

Question, Bug, or Feature?
Type: Bug

Enter Task Name: AzureResourceGroupDeployment@2

Environment

  • Server - Azure Pipelines

    • If using Azure Pipelines, provide the account name, team project name, build definition name/build number:
      AZGlobal/Azure Global CAT Engineering/Pipelines/Releases/Benfica-Jmeter-release
  • Agent - Hosted
    - If using Hosted agent, provide agent queue name:
    Agent name: 'Azure Pipelines 2'
    Agent machine name: 'fv-az645'
    Current agent version: '2.159.2'

Issue Description

Using the AzureResourceGroupDeployment@2 task and providing the file path link to the ARM template in the classic pipeline UI the task fails with error:
Error: Could not find any file matching the template file pattern

image

The debug logs show the path to the template correctly but failing when "applying matching pattern" within findmatch code block

Task logs

tasklog_5.zip

Troubleshooting

Checkout how to troubleshoot failures and collect debug logs: https://docs.microsoft.com/en-us/vsts/build-release/actions/troubleshooting

Error logs

[Insert error from the logs here for a quick overview]

@vinodkumar3
Copy link
Contributor

vinodkumar3 commented Nov 4, 2019

For finding matching file patters AzureResourceGroupDeployment@2 task use findMatch library method.
I'm able to repro the scenario and the way to get unblocked is to avoid using brackets ('[' or ']') in folder/file name.

@vinodkumar3
Copy link
Contributor

Closing this issue in favor of main tracking issue.

@bishal-pdMSFT
Copy link
Contributor

Reactivating this issue till the time tracking issue is triaged as a bug

@jalajmsft
Copy link
Contributor

Hey @petegrimsdale The fix is rolled out and should be available in all the regions by end of this week. Closing this issue. Feel free to re-open or create a new issue for further queries.

@jalajmsft jalajmsft self-assigned this Dec 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants