Publish task PublishArtifactsInManifest failing in AspLabs pipeline
See original GitHub issue- This issue is blocking
- This issue is causing unreasonable pain
I see that the publishing step of the AspLabs hasn’t passed in a long time: https://dnceng.visualstudio.com/internal/_build?definitionId=249&_a=summary and the error suggests something is wrong in the task PublishArtifactsInManifest
in arcade. It looks like my attempt didn’t fix it so I’m hoping someone can help from Arcade can help us.
This is currently blocking publishing packages from this repo and we are trying to push out some new bits for customers to try so there is some urgency.
Investigation wise, I think this is related to the work in https://github.com/dotnet/arcade/pull/7317. This repo uses publishingInfraVersion=2. Given that most repos are using version 3 already and that this is a low traffic repo, I can see how we didn’t notice the problem. Is there an issue with publishing infra version 2 that needs to be fixed? Or do we need to do work to move to version 3 like the rest of the repos?
Issue Analytics
- State:
- Created 2 years ago
- Comments:14 (10 by maintainers)
Top GitHub Comments
Oh, duh… oops.
I think I see the problem, and it’s silly.
https://github.com/aspnet/AspLabs/blob/main/eng/Publish.props needs to be renamed to Publishing.props so that the Arcade SDK will try to read from it.