Wrong warn message: Resource file haven\'t set, can\'t find loc string for key: Not pushing metadata as no resource Ids found

[gabrielclima]

Required Information

Recently, we received build warns with ##[warning]Resource file haven\'t set, can\'t find loc string for key: Not pushing metadata as no resource Ids found. We didn't changed anything in our build config and I don't if we made a miss config or anything to fix this warn. I already checked the task documentation and both version task code (PublishPipelineMetadataV0 and PublishPipelineMetadataV1)

Our task config:

Question, Bug, or Feature?
Type: Bug

Enter Task Name: PublishBuildArtifacts@1

Environment

Azure Pipelines: stonepagamentos | finprods-Credit | CreditApi-CI | 1.2.2008.0306
Agent: Ubuntu16

Issue Description

Warn screenshot:

Task logs

2020-08-03T19:09:51.2043227Z ##[section]Starting: Publish Pipeline Metadata
2020-08-03T19:09:51.2048748Z ==============================================================================
2020-08-03T19:09:51.2049295Z Task         : Publish Pipeline Metadata
2020-08-03T19:09:51.2049669Z Description  : Publish Pipeline Metadata to Evidence store
2020-08-03T19:09:51.2050055Z Version      : 0.170.0
2020-08-03T19:09:51.2050392Z Author       : Microsoft Corporation
2020-08-03T19:09:51.2050772Z Help         : ms-resource:loc.helpMarkDown
2020-08-03T19:09:51.2051252Z ==============================================================================
2020-08-03T19:09:51.3691632Z ##[warning]Resource file haven\'t set, can\'t find loc string for key: Not pushing metadata as no resource Ids found
2020-08-03T19:09:51.4298673Z ##[section]Finishing: Publish Pipeline Metadata

Troubleshooting

Described at description.

[asostechnix]

Seeing the same issue with the Maven@3 task.

[lindhe]

It's a shame that there's no way to pin patch version numbers of the tasks, so one could roll back to avoid this...

[github-actions]

This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days

[lindhe]

Oh absolutely not. Guys, do we not have any eyes on this at all?

[TravisEz13]

Can we please get this addressed?
https://dev.azure.com/powershell/PowerShell/_build/results?buildId=73459&view=logs&j=bc13c707-2b09-5831-a107-b42ace4fe40a&t=a88287c2-32fb-5af0-89ea-5d5b1a3cc8cf
I'm using the ##vso commands and it seems to be triggering this.

[anatolybolshakov]

Hi @TravisEz13 we fixed this issue and will let you know once it will be available.

[anatolybolshakov]

Hi everyone, we have rolled out fix for this issue - please let us know if you have any other issues.