YAML Pipelines - Server imposed 'system-pre-steps.yml' forcing agent version restriction

Nikama Adeel 1 Reputation point
2026-11-19T16:01:57.94+00:00

##[error]No agent found in pool [pool] which satisfies the following demand: Agent.Name. All demands: Agent.Name -equals '[name]', Agent.Version -gtVersion 5.279.0

Log:

Job preparation parameters

ContinueOnError: False

TimeoutInMinutes: 60

CancelTimeoutInMinutes: 5

Expand:

MaxConcurrency: 0

########## System Pipeline Decorator(s) ##########

Begin evaluating template 'system-pre-steps.yml'

Evaluating: eq('true', variables['system.debugContext'])

Expanded: eq('true', Null)

Result: False

Evaluating: resources['repositories']['self']

Expanded: Object

Result: True

Evaluating: not(containsValue(job['steps']['*']['task']['id'], '6d15af64-176c-496d-b583-fd2ae21d4df4'))

Expanded: not(containsValue(Object, '6d15af64-176c-496d-b583-fd2ae21d4df4'))

Result: False

Finished evaluating template 'system-pre-steps.yml'


Template and static variable resolution complete. Final runtime YAML document:

steps: []

MaxConcurrency: 0

Environment type: Self-Hosted

Server type: Azure DevOps Server

Server version: Azure DevOps Server 2022.2

Agent version: 4.275.0

Operating system: SUSE Linux Enterprise Server 15 SP6

This is my entire yaml file presently:

trigger: none

jobs:

  • job: Build pool: name: [pool name] demands:
    • Agent.Name -equals '[name]'
    steps:
    • checkout: none

I don't understand why system-pre-steps.yml is imposing a restriction of Agent.Version -gtVersion 5.279.0, or if it's not imposing it itself, it's being imposed from elsewhere. I have attempted to specify agent version 4.275.0 but I receive the same error as it attempts to match agent version 4.275.0 and agent version greater than 5.279.0 which is obviously impossible.

As documentation is sorely lacking, I am unsure as to how to proceed from here. I cannot simply update the agent as the Linux operating system I am attempting to host the agent on cannot support .NET 10 which is required by agent versions 5.XXX.X.

Nothing in the Microsoft documentation that I found mentions a 'system-pre-steps.yml' and I am unsure as to why it's even required. Has anybody else run into this issue? How can I bypass these restrictions?

Azure DevOps
0 comments No comments

1 answer

Sort by: Oldest
  1. AI answer

    2026-11-19T16:04:13.67+00:00

    system-pre-steps.yml evaluated to an empty steps: [], so it did not inject an executable step; the Agent.Version -gtVersion 5.279.0 demand is being generated elsewhere during server-side job preparation, and there is no documented pipeline-YAML mechanism for cancelling that generated demand.

    What the log establishes

    • The GUID [GUID] is the built-in checkout operation. Decorators evaluate tasks after keywords have been resolved to GUIDs.^1^
    • steps: [] proves only that this decorator invocation added no steps. It does not identify which server component added the version demand.
    • Azure DevOps can generate a minimum-agent demand for advanced checkout, but the documented conditions are multiple checkout steps, checkout not being first, or checking out something other than self or none. Your checkout: none does not meet those documented conditions.^2^
    • Azure DevOps Server 2022.2 normally corresponds to agent 3.238.0. Version 5.x support for Server 2020 and later depends on corresponding server updates. Therefore, a demand above 5.279.0 on Server 2022.2 is not something to resolve by blindly installing a 5.x agent.^3^

    Adding this cannot override the generated requirement:

    demands:
    - Agent.Name -equals '[name]'
    - Agent.Version -equals 4.275.0
    

    It merely requires the agent to satisfy both Agent.Version = 4.275.0 and Agent.Version > 5.279.0, which is impossible. Demands are used to select agents whose reported capabilities meet the job requirements.^4^

    Least-disruptive server-side checks

    These actions require a project-collection or Azure DevOps Server administrator.

    1. Record the exact Server 2022.2 patch level.
      • Check the installed Azure DevOps Server build/version, not only “2022.2.”
      • Compare it with the Server 2022 Update 2 release notes. Patch 12 is the latest listed servicing patch as of August 11, 2026.^5^
      • If behind, schedule the supported cumulative servicing update and rerun the minimal pipeline.
      This is a general servicing step, not a documented fix for this particular demand. Patch 3 mentions a YAML-pipeline failure, but its notes do not establish that it fixes Agent.Version -gtVersion 5.279.0.
    2. Inventory collection-installed extensions before changing anything.
      • Open the Azure DevOps Server collection gallery: http://{server}:8080/tfs/_gallery/manage
      • Identify private extensions and inspect their manifests for a contribution with:
             {
               "type": "ms.azure-pipelines.pipeline-decorator"
             }
        
      • Pipeline decorators can inject steps across all pipelines in a collection, and only private extensions can contribute decorators.^6^
    3. Only if such an extension exists, isolate it safely.
      • Prefer a non-production collection.
      • Remove or disable one candidate at a time, then rerun the minimal pipeline.
      • For Azure DevOps Server, use the extension’s … menu and select Remove.^7^
      • Restore it if the demand remains.

    This is source isolation, not an assertion that a private extension caused the demand. system-pre-steps.yml may also be an internal server-provided template.

    If 5.x is genuinely required

    Do not attempt agent 5.x on the current host unless its exact OS version supports .NET 10. Microsoft documents SLES 15.7 and 16.0 as supported for 5.x; earlier SLES versions may require migration. The 5.x runtime is self-contained, so separately installing .NET 10 does not make an unsupported OS supported.^3^

    The supported route is:

    1. Provision a .NET 10-supported OS.
    2. Confirm that the installed Azure DevOps Server servicing level supports the required agent generation.
    3. Register the replacement agent in the pool.
    4. Verify Agent pools → pool → agent → Capabilities → Agent.Version.
    5. Retire the old agent only after a test pipeline succeeds.

    Escalation

    If the demand remains on a fully serviced Server 2022.2 instance with no private pipeline decorators, open a Microsoft support case. Include:

    • Exact server build and patch level.
    • Minimal YAML.
    • Complete Job preparation parameters and final runtime YAML.
    • Agent capability export showing Agent.Version.
    • Installed-extension inventory.
    • Confirmation that checkout: none still produces Agent.Version -gtVersion 5.279.0.

    That combination demonstrates a reproducible server-generated demand inconsistent with the documented Server 2022.2 agent generation and removes the repository YAML and private decorators as likely sources.


    References

    1. Pipeline decorator expression context
    2. PipelineConstants.AdvancedCheckoutMinAgentVersion Field-Definition
    3. Agent software version 5
    4. Azure Pipelines agents
    5. Azure DevOps Server 2022 Update 2 Release Notes
    6. Author a pipeline decorator
    7. Install extensions
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.