-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Wrong warn message: Resource file haven\'t set, can\'t find loc string for key: Not pushing metadata as no resource Ids found #13384
Comments
Seeing the same issue with the Maven@3 task. |
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... |
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 |
Oh absolutely not. Guys, do we not have any eyes on this at all? |
Can we please get this addressed? |
Hi @TravisEz13 we fixed this issue and will let you know once it will be available. |
Hi everyone, we have rolled out fix for this issue - please let us know if you have any other issues. |
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
Troubleshooting
Described at description.
The text was updated successfully, but these errors were encountered: