Today we’re very excited to announce the first release candidate (RC1) of Azure DevOps Server 2022.1!
With this release, we’ve added many new features that you’ve been asking for. Here are a few of the highlights:
- Last Accessed column on Delivery Plans page
- Visualize all dependencies on Delivery Plans
- New PAT Scope for managing pipeline authorization and approvals and checks
- New user interface for upstream package search
- Show Parent in Query Results Widget
There are many more features with this release, and you can read all about those features in our release notes. You can download Azure DevOps Server 2022.1 RC1 today. A direct upgrade to Azure DevOps Server is supported from any version of TFS, including Team Foundation Server 2015 and newer. Let us know any feedback or questions via the Developer Community.
Hi!
I just updated our test environment with this release, and it seems that release pipelines are completely broken. They don’t even start (the status remains “Not deployed”).
Is this a known issue ?
Hi Thomas, do you still have issues with the release pipelines? Are you getting any error messages?
Yesterday we released Azure DevOps Server 2022.1 RC2.
I wanted to download the RC1 but on the download page https://learn.microsoft.com/en-us/azure/devops/server/download/azuredevopsserver either downloads (exe / iso) lead to RC2 files.
It really seems to be RC2 build on 09/27/2023.
Hi Michael, the download page is now linked to RC1 downloads. We will be releasing RC2 mid-October.
Will it be safe to upgrade my schroedinger-RC2 test environment to the real RC2?
Could you please tell us what sprint Update 1 will be set on?
You will be able to install Azure DevOps Server 2022.1 RC2 and/or the final release of Azure DevOps Server 2022.1 on your test environmet running Azure DevOps Server 2022.0.1.
Azure DevOps Server 2022.1 will include features from sprints 206 – 225. Not sure I understand your question about upgrading with the real RC2. Can you elaborate?
I installed the setup provided by yesterdays link (19.225.34127.2) on a test system running at 2022.0.1patch3.
Will I be able to update this test system on the upcoming RC2 release?
Would someone be so kind to reveal what version of the pipeline agent is bundled with this release?
I am specifically interested in knowing if we are getting version v2.220.0 or newer, which should be using a (substantial) never version of git-lfs.
We updated to the latest 2022.0.1 patch 3 and it included 3.225, so you don’t even need to wait for 2022.1!
That seems like quite the jump as we are on 2022.0.1 Patch 1. I would recon that version 3.x of the pipeline agent was optional at least in the beginning as it might break functionality in existing Build Tools.
The jump from 2.x to 3.x was because of the upgrade from .net 3.1 to 6, its functionality didn’t change, but which OS it can run on did
https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/v3-agent?view=azure-devops
yep, know that.
But I would expect the update to 3.x to not happen automatically similar to what was done on Azure DevOps services:
https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/v3-agent?view=azure-devops#what-will-happen-when-a-task-requires-an-agent-to-be-updated-to-agent-version-3
at least of for one release…
I’ve been trying to do an unattended setup that includes Search configuration, but the documentation at https://learn.microsoft.com/en-us/azure/devops/server/install/unattended doesn’t give a comprehensive overview of parameters or inputs available.
How do I find out what inputs I can use that isn’t part of the ini-files created using tfsconfig /create ?
Hi Dennis, we are reviewing the documentation and will update with parameters.
this comment has been deleted.
Do not sync tags when fetching a Git repository
Looked through a couple of the builds and I do not see this option available in the screen, it shows the same options as 2022.0.1 does.
Hi
I expect that you have to set this through yaml and not the UI.
From the release notes:
https://learn.microsoft.com/en-us/azure/devops/server/release-notes/azuredevops2022u1?view=azure-devops&tabs=yaml#do-not-sync-tags-when-fetching-a-git-repository
The release notes have a “classic” tab that shows it in their example
You are absolutely right! Sorry, I didn’t see the mention of classic.
I had patched our test ADO box with 2022.0.1 Patch 3 previously, and just finished the 2022.1 update, this warning appeared when it completed. I’m guessing you’ll update this task by the time the non-RC version is out.
[2023-09-22 12:13:36Z][Warning] Updating an existing task Azure file copy (eb72cb01-a7e5-427b-a8a1-1b31ccac8a43) with an older version 2.226.2. The service already had version 2.227.3. This means the task author must bump their version number.
Hi Jonathan, we are currently investigating this. We will get back to you once we have details about what is causing this warning.
Looks like it was most of the tasks updated in the latest patch, when looking through the install logs
[Warning@08:22:21.821] [2023-09-22 12:13:45Z][Warning] Updating an existing task Azure file copy (eb72cb01-a7e5-427b-a8a1-1b31ccac8a43) with an older version 3.226.2. The service already had version 3.227.3. This means the task author must bump their version number.
[Warning@08:22:21.821] [2023-09-22 12:13:55Z][Warning] Updating an existing task Azure file copy (eb72cb01-a7e5-427b-a8a1-1b31ccac8a43) with an older version 4.226.2. The service already had version 4.227.0. This means the task author must bump their version number.
[Warning@08:22:21.821] [2023-09-22 12:14:08Z][Warning] Updating an existing task Azure file copy (eb72cb01-a7e5-427b-a8a1-1b31ccac8a43) with an older version 5.226.2. The service already had version 5.227.0. This means the task author must bump their version number.
[Warning@08:22:21.821] [2023-09-22 12:16:53Z][Warning] Updating an existing task PowerShell (e213ff0f-5d5c-4791-802d-52ea3e7be1f1) with an older version 2.226.1. The service already had version 2.226.2. This means the task author must bump their version number.
[Warning@08:22:21.822] [2023-09-22 12:18:26Z][Warning] Updating an existing task SSH (91443475-df55-4874-944b-39253b558790) with an older version 0.226.1. The service already had version 0.226.2. This means the task author must bump their version number.
[Warning@08:22:21.822] [2023-09-22 12:19:17Z][Warning] Updating an existing task Windows machine file copy (731004d4-1d66-4f70-8c05-638018b22210) with an older version 1.226.2. The service already had version 1.227.0. This means the task author must bump their version number.
[Warning@08:22:21.822] [2023-09-22 12:19:17Z][Warning] Updating an existing task Windows machine file copy (731004d4-1d66-4f70-8c05-638018b22210) with an older version 2.226.2. The service already had version 2.227.0. This means the task author must bump their version number.
[Info @08:22:22.100] Node returned: Warning
[Warning@08:22:22.100] [2023-09-22 12:13:36Z][Warning] Updating an existing task Azure file copy (eb72cb01-a7e5-427b-a8a1-1b31ccac8a43) with an older version 2.226.2. The service already had version 2.227.3. This means the task author must bump their version number.
Hi Jonathan, we’ve implemented a fix and will release it with Azure DevOps Server 2022.1 RC2. Thank you for installing RC1 and reporting this issue.
Looks like 2022.1 RC1 suffers the same issue as 2022.0.1 where you cannot install and configure it on Windows Server Core (2019 or 2022).
On Server 2022 Core the installer fails to start with:
Class not registered
On Server 2019 Core the server configuration wizard fails with:
Unable to find an entry point named
‘NetFreeAadJoinInformation’ in DLL ‘netapi32.dll’
More detail can be found here:
https://developercommunity.visualstudio.com/t/Configuration-wizard-fails-after-upgrade/10385103
Hi Adrian, thank you for installing RC1 and sharing your feedback. This issue will be addressed in the Azure DevOps Server 2022.1 RC2 release.
Thanks Gloridel
Some minor feedback
Disappointed to not see the Boards experience refresh but still a decent set of updated. Thanks again.
Hi Mike, thank you for sharing your feedback. We have updated the release notes to address the items that you pointed out.