Updated: Azure DevOps Server 2022.1 RTW now available

Gloridel Morales

12/5 Update: There is a known issue where the Agent version does not update after upgrading to Azure DevOps Server 2022.1 and using Update Agent in Agent Pool configuration. We are currently working on a patch to resolve this issue and will share updates in the Developer Community as we make progress. In the meantime, you can find a workaround for this issue in this Developer Community ticket.

Today, we released Azure DevOps Server 2022.1 RTW. This is our final release of Azure DevOps Server 2022.1. You can directly install Azure DevOps Server 2022 Update 1 or upgrade from any version of Azure DevOps or TFS, including Team Foundation Server 2015 and newer. You can find the full details in our release notes.

Here are some key links:

We’d love for you to install this release and provide any feedback at Developer Community.

15 comments

Comments are closed. Login to edit/delete your existing comments

  • Jonathan Gillette 0

    Updated our test TFS server to 2022.1 and it looks like it’s trying to update the agent to 3.225.2 (which on github says is a pre-release?), but fails. This could be something with our environment, but just seeing if anyone else has seen this as well.

    [2023-11-30 18:44:27Z INFO Agent] Refresh message received, kick-off selfupdate background process.
    [2023-11-30 18:44:27Z INFO SelfUpdater] Version ‘3.225.2’ of ‘agent’ package available in server.
    [2023-11-30 18:44:27Z INFO SelfUpdater] Current running agent version is 3.225.0
    [2023-11-30 18:44:27Z INFO SelfUpdater] An update is available.
    [2023-11-30 18:44:27Z INFO Terminal] WRITE LINE: Agent update in progress, do not shutdown agent.
    [2023-11-30 18:44:27Z INFO Terminal] WRITE LINE: Downloading 3.225.2 agent
    [2023-11-30 18:44:27Z INFO HostContext] Well known directory ‘Bin’: ‘C:\agents\A1\bin’
    [2023-11-30 18:44:27Z INFO HostContext] Well known directory ‘Root’: ‘C:\agents\A1’
    [2023-11-30 18:44:27Z INFO HostContext] Well known directory ‘Work’: ‘C:\agents\A1_work’
    [2023-11-30 18:44:27Z INFO SelfUpdater] Attempt 1: save latest agent into C:\agents\A1_work_update\agent1.zip.
    [2023-11-30 18:44:27Z INFO SelfUpdater] Download agent: begin download
    [2023-11-30 18:44:35Z INFO SelfUpdater] Download agent: finished download
    [2023-11-30 18:44:35Z WARN SelfUpdater] Unable to perform the necessary checksum validation since the target package hash is missed
    [2023-11-30 18:44:35Z INFO SelfUpdater] Attempt 2: save latest agent into C:\agents\A1_work_update\agent1.zip.
    [2023-11-30 18:44:35Z INFO SelfUpdater] Download agent: begin download
    [2023-11-30 18:44:43Z INFO SelfUpdater] Download agent: finished download
    [2023-11-30 18:44:43Z WARN SelfUpdater] Unable to perform the necessary checksum validation since the target package hash is missed
    [2023-11-30 18:44:43Z INFO SelfUpdater] Attempt 3: save latest agent into C:\agents\A1_work_update\agent1.zip.
    [2023-11-30 18:44:43Z INFO SelfUpdater] Download agent: begin download
    [2023-11-30 18:44:49Z INFO SelfUpdater] Download agent: finished download
    [2023-11-30 18:44:49Z WARN SelfUpdater] Unable to perform the necessary checksum validation since the target package hash is missed
    [2023-11-30 18:44:49Z INFO Agent] Ignore agent update exception. System.Threading.Tasks.TaskCanceledException: Agent package checksum validation failed.
    There are possible reasons why this happened:
    1) The agent package was compromised.
    2) The agent package was not fully downloaded or was corrupted during the download process.
    You can skip checksum validation for the agent package by setting the environment variable DISABLE_HASH_VALIDATION=true
    at Microsoft.VisualStudio.Services.Agent.Listener.SelfUpdater.DownloadLatestAgent(CancellationToken token) in D:\a\1\s\src\Agent.Listener\SelfUpdater.cs:line 375
    at Microsoft.VisualStudio.Services.Agent.Listener.SelfUpdater.SelfUpdate(AgentRefreshMessage updateMessage, IJobDispatcher jobDispatcher, Boolean restartInteractiveAgent, CancellationToken token) in D:\a\1\s\src\Agent.Listener\SelfUpdater.cs:line 82
    at Microsoft.VisualStudio.Services.Agent.Listener.Agent.RunAsync(AgentSettings settings, Boolean runOnce) in D:\a\1\s\src\Agent.Listener\Agent.cs:line 379
    [2023-11-30 18:44:49Z INFO Agent] Auto update task finished at backend, there is no available agent update needs to apply, continue message queue looping.

    • Merlyn OppenheimMicrosoft employee 0

      Hi Jonathan, thank you for the report. 3.225.2 is indeed the correct version for 2022.1 (we’ll update the tag). The error message indicates that “hashValue” is missing from the API response (https://[your server]/_apis/distributedtask/packages/agent?platform=win-x64). That shouldn’t be happening; we’re taking a look on our end to see how that could occur.

  • constantin munteanu 0

    was Maven 3.9.x compatibility issue fixed into 2021.1 RTW version?

    • Gloridel MoralesMicrosoft employee 0

      Hi Constantin, this was not resolved with the final release of Azure DevOps Server 2022.1. As a workaround, you can continue using Maven 3.9.x with the property –

      Dmaven.resolver.transport=wagon

      . This change forces Maven to use Wagon Resolver Transport. Check out the documentation here for more details.

  • Kohl, Franz 1

    I’ve updated our test Azure DevOps Server from 2022.0.1 + Patch 5 to 2022.1 – and found an option missing in the “Publish build artifacts” task, which is significant to some of our developers.

    On 2022.0.1 + Patch 5, in the “Publish build artifacts” task in the “Advanced” section, you can still find the option “File copy options” with the corresponding input field (plus the new checkmark option “Tar the artifact before uploading”).

    On 2022.1 (after the upgrade from 2022.0.1 + Patch 5), the option “File copy options” with the corresponding input field is completely missing! Only the new option “Tar the artifact before uploading” is available in the “Advanced” section.

    Both tasks have an identical Task version in the UI (1.*; no other available) and in the log (1.200.0).

    This is a showstopper for our upgrade plans, unfortunately. I’d appreciate it if you could commit this bug and provide a timeline for a fix/patch.

    TIA, Franz

    • Gloridel MoralesMicrosoft employee 1

      Hi Franz, we thank you for reporting this. We opened a bug to investigate and address this issue.

      • Kohl, Franz 0

        Hi Gloridel,

        Based on Merlyn’s suggestion (see below), I just filed a problem report for this.

        Please ensure that the bug you’ve already opened gets connected to the problem report to prevent duplicate efforts and communication.

        Thanks,
        Franz

    • Merlyn OppenheimMicrosoft employee 1

      Thank you for your report! We appreciate your feedback and want to resolve this issue as soon as possible. To help us do that, we need some more information from you. Please open a ticket on Developer Community here: https://developercommunity.visualstudio.com/AzureDevOpsServerTFS.
      Make sure to use “Report a Problem” and provide a clear title and description of the issue. You can also use the ticket to track the progress of the resolution. Once you have opened the ticket, please post the link to it here and we will follow up with you. We hope to hear from you soon!

  • Dave Klostermann 0

    Is there a workaround to be able to continue using older version of the agent on this ADO Server version? We have some software limitations that require us to be on Ubuntu 18/20 and use Agent 2.217.x. When we test the upgrade on our test instance, the upgrade works, but then we get errors in the pipeline saying that Agent version 3.22.2 is required.

    If that is a new requirement, we are stuck on the ADO Server 2022 version and can no longer upgrade.

    • Michael Hauer 0

      Just out of curiosity: why is v3.x agent a problem for you? v3 is compatible with Ubuntu 18.x and 20.x.

Feedback usabilla icon