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.
After installing Azure DevOps Server 2022.1 Plans feature not working at all
https://developercommunity.visualstudio.com/t/After-installing-Azure-DevOps-Server-202/10576764
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...
Just out of curiosity: why is v3.x agent a problem for you? v3 is compatible with Ubuntu 18.x and 20.x.
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...
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...
Hi Merlyn,
I just filed this as a problem, as you suggested.
Here is the link to the report:
https://developercommunity.visualstudio.com/t/ADS-20221-RTW:-%E2%80%9CPublish-build-artifacts/10543525
HTH,
Franz
Hi Franz, we thank you for reporting this. We opened a bug to investigate and address this issue.
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
It would be sweet if the Feature Timeline could also be updated to indicate the features that are part of 2022.1:
https://learn.microsoft.com/en-us/azure/devops/release-notes/features-timeline-released
Now we are on the subject, then I think that there are still changes marked with "Future" that is already in the product.
E.g. the following from April 2018:
https://learn.microsoft.com/en-us/azure/devops/release-notes/2018/apr-16-vsts#trigger-ci-builds-from-yaml
Or this one from from September 2018
https://learn.microsoft.com/en-us/azure/devops/release-notes/2018/sep-10-azure-devops-launch#configure-builds-using-yaml
Or this one from October 2018
https://learn.microsoft.com/en-us/azure/devops/release-notes/2018/sprint-142-update#use-yaml-template-expressions-inline
I could go on - this is just the three oldest that I figure is already there.
Hi Tore, features for 2022.1 are now identified in the Released Feature table. We will look into reviewing this next year and mark with the corresponding release for any features that we have missed.
was Maven 3.9.x compatibility issue fixed into 2021.1 RTW version?
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 –
. This change forces Maven to use Wagon Resolver Transport. Check out the documentation here for more details.
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...
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.