Skip to content

Update L0 for Container Label#5438

Merged
dassayantan24 merged 16 commits intomasterfrom
users/dassayantan/l0-for-container-label
Jan 20, 2026
Merged

Update L0 for Container Label#5438
dassayantan24 merged 16 commits intomasterfrom
users/dassayantan/l0-for-container-label

Conversation

@dassayantan24
Copy link
Copy Markdown
Contributor

@dassayantan24 dassayantan24 commented Dec 31, 2025

Context

Unit tests validating node path resolution for containerized pipeline tasks across different platforms.

Work-Item [AB#2345216] - https://dev.azure.com/mseng/AzureDevOps/_workitems/edit/2345216/


Description

The Azure Pipelines Agent provides the ability to run pipeline tasks in a container. During the initialize container step, the agent invokes a container start operation which creates a separate process in which the task executes. These tests cover the agent code that determines the correct node path based on the node path label in the Dockerfile. Three key parameters are directly involved in node-related operations: CustomNodePath (extracted from Docker label), ResultNodePath (final resolved path), and ContainerCommand (command executed in the container).


Risk Assessment (Low / Medium / High)

Low


Unit Tests Added or Updated (Yes / No)

Yes


Additional Testing Performed

List manual or automated tests performed beyond unit tests (e.g., integration, scenario, regression).
N/A


Change Behind Feature Flag (Yes / No)

No


Tech Design / Approach

  • Design has been written and reviewed. Yes
  • Any architectural decisions, trade-offs, and alternatives are captured. Yes

Documentation Changes Required (Yes/No)

ContainerOperationProvider L0 Tes.txt


Logging Added/Updated (Yes/No)

  • Appropriate log statements are added with meaningful messages.
  • Logging does not expose sensitive data.
  • Log levels are used correctly (e.g., info, warn, error).

Telemetry Added/Updated (Yes/No)

  • Custom telemetry (e.g., counters, timers, error tracking) is added as needed.
  • Events are tagged with proper metadata for filtering and analysis.
  • Telemetry is validated in staging or test environments.

Rollback Scenario and Process (Yes/No)

  • Rollback plan is documented.

Dependency Impact Assessed and Regression Tested (Yes/No)

  • All impacted internal modules, APIs, services, and third-party libraries are analyzed.
  • Results are reviewed and confirmed to not break existing functionality.

@dassayantan24
Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@dassayantan24
Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@dassayantan24
Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@dassayantan24
Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@dassayantan24
Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@dassayantan24
Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@dassayantan24
Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

Comment thread src/Test/L0/Worker/ContainerOperationProviderL0.cs
@dassayantan24
Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@dassayantan24
Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@dassayantan24
Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@dassayantan24
Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@dassayantan24
Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@dassayantan24
Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@dassayantan24 dassayantan24 marked this pull request as ready for review January 12, 2026 09:23
@dassayantan24 dassayantan24 requested review from a team as code owners January 12, 2026 09:23
@dassayantan24 dassayantan24 changed the title Update l0 for Container Label Update L0 for Container Label Jan 14, 2026
Comment thread src/Test/L0/Worker/ContainerOperationProviderEnhancedL0.cs Outdated
Comment thread src/Test/L0/Worker/ContainerOperationProviderL0.cs
@dassayantan24
Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@dassayantan24 dassayantan24 merged commit fd3f5a7 into master Jan 20, 2026
14 checks passed
@dassayantan24 dassayantan24 deleted the users/dassayantan/l0-for-container-label branch January 20, 2026 11:23
surajitshil-03 pushed a commit that referenced this pull request Feb 6, 2026
* Update l0 for Container Label

* Fix L0

* Update taskkey error

* Remove comments

* Fix#2 Linux errors

* fix macos issues

* fix#3 macos issues

* fix#4 macos tests

* Update fake mock invoker

* Add Base class

* TestFix#1 Queue error

* testFix#2 Queue error

* testfix#3 macos error

* TestFix#4 Add DockerExec mock for node version

* Add L0 tests for ContainerOperationProviderEnhanced

* Remove redundant reflection in Enhanced provider tests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants