microsoft-authentication-library-for-dotnet
microsoft-authentication-library-for-dotnet copied to clipboard
[Engineering Task] Verify that our OneBranch pipelines are sufficient to be the primary release pipelines
Type of task?
Builds
Description
Per guidance release pipelines should use OneBranch and the non-OneBranch ones will need to be disabled in the future.. We need to make sure that our production OneBranch pipelines are sufficient - run all the tasks, tests, etc. (compare with non-OneBranch equivalent).
Solution
No response
They can't, there are tests that are disabled on OneBranch related to public client. Not expecting to fix them. What other steps are you thinking of?
They can't, there are tests that are disabled on OneBranch related to public client. Not expecting to fix them. What other steps are you thinking of?
@bgavrilMS we can ensure that we use an image that at least has the same components as the agents on the non onebranch build. Today we are a couple of versions behind due to a bug in OneBranch related to android.
I rephrased the title. Yes, I meant that that OneBranch should be sufficient and be our primary pipelines. If there are blockers, we should create support tickets with them, sooner rather than later.