Skip to content

[release/10.0] Use WIF-based Entra auth for OneLocBuild ceapex feed access#17084

Open
missymessa wants to merge 2 commits into
release/10.0from
onelocbuild-wif-migration-10.0
Open

[release/10.0] Use WIF-based Entra auth for OneLocBuild ceapex feed access#17084
missymessa wants to merge 2 commits into
release/10.0from
onelocbuild-wif-migration-10.0

Use WIF-based Entra auth for OneLocBuild ceapex feed access

0357d55
Select commit
Loading
Failed to load commit list.
Azure Pipelines / arcade-pr succeeded Jul 8, 2026 in 1h 24m 31s

Build #20260708.11 had test failures

Details

Tests

  • Failed: 36 (0.39%)
  • Passed: 8,678 (94.92%)
  • Other: 428 (4.68%)
  • Total: 9,142

Annotations

Check failure on line 1 in HelixReporterTests.failure1

See this annotation in the file changed.

@azure-pipelines azure-pipelines / arcade-pr

HelixReporterTests.failure1

Intentional Failure
Raw output
            This failure is expected and is not the reason why your PR failed. This test is always failing in order to test failure reporting infrastructure. If your PR is blocked there must be another test or build error that is blocking your PR.
         

Check failure on line 1 in HelixReporterTests.failure2

See this annotation in the file changed.

@azure-pipelines azure-pipelines / arcade-pr

HelixReporterTests.failure2

Intentional Failure
Raw output
            This failure is expected and is not the reason why your PR failed. This test is always failing in order to test failure reporting infrastructure. If your PR is blocked there must be another test or build error that is blocking your PR.
         

Check failure on line 1 in tests.UnitTest2.ExpectedFailureTheoryTest

See this annotation in the file changed.

@azure-pipelines azure-pipelines / arcade-pr

tests.UnitTest2.ExpectedFailureTheoryTest

Test failed

Check failure on line 1 in HelixReporter.TRXTests.HelixReporter.TRXTests.Fail1

See this annotation in the file changed.

@azure-pipelines azure-pipelines / arcade-pr

HelixReporter.TRXTests.HelixReporter.TRXTests.Fail1

                        This failure is expected and is not the reason why your PR failed. This test is always failing in order to test failure reporting infrastructure. If your PR is blocked there must be another test or build error that is blocking your PR.
                    
Raw output
   at tests.UnitTest1.TestMethod1() in UnitTest1.cs:line 13