Conversation
|
I think also removing the attribute would do the same thing. This is more explicit tho |
|
Monitoring.Sdk is still getting published. I might be because of |
|
Will this cause failures in the post-publishing steps of the build since we're still trying to deploy everything from here? |
|
I don't think we will. Dotnet.Status.Web doesn't use those packages, and none of the other projects here are used for deployments. To be safe, I can disable the rollouts for all internal tools in this PR too, we planned on doing that anyway |
| displayName: Notify deployment start | ||
| pool: server | ||
| steps: | ||
| - task: InvokeRESTAPI@1 |
There was a problem hiding this comment.
I'm not sure if this is OK to remove, since it might be used for Maestro deployments too?
There was a problem hiding this comment.
I think this was at least necessary for RolloutScorer. Let me know if ProdCon isn't planning to use results from RolloutScorer anymore for Arcade Services and I'll make sure it gets removed from RolloutScorer.
riarenas
left a comment
riarenas
left a comment
There was a problem hiding this comment.
Looks reasonable to me!
3 participants
issue: #2296
Validation PR run: https://dev.azure.com/dnceng/internal/_build/results?buildId=2186664&view=results