We have gotten a lot of feedback on this change and after internal deliberation, we are now rolling back this change ASAP.
Final Update as of 5/19/22 @ 10:08 AM PST:
-
We have now fully rolled back the change that caused the issue. You should no longer experiencing this issue. * We will go back to the drawing board to re-work this fix. Our goal is to provide a high bar of security without breaking our customers.
-
We will also do a postmortem on this change to gain a better understanding of what went wrong. Our goal is to understand what we missed so we avoid rolling out this kind of breaking changes in the future.
Again, I am deeply sorry for the inconvenience and disruption this has caused. We remain deeply committed to making sure our customers have a first-class experience using Azure DevOps. Cheers!
- Benibo Ajumogobia, Azure DevOps Security PM
Hello, I am getting the same error on my classic build pipelines (You can’t set the following variables) and there is no option in the classic build Variable UI to mark them as “settable at queue time”. Did the bad change get rolled out again?
Ms Morales:
I currently have the 10/6/2020, Azure DevOps Server 2020 RTW installed. ADS admin console shows 18.170.30525.1.
The release notes for the May 17, 2022, Azure DevOps Server 2020.1.2 says that I can “upgrade from Azure DevOps Server 2020”
Can I upgrade directly from the 10/6/2020 Azure DevOps Server 2020 RTW to ADS 2020.1.2, or do I first need to install the 3 patches for ADS 2020? (Dec 8, 2020 ADS 2020 Patch 1; Jan 12, 2021 ADS 2020 Patch 2, and Feb 9, 2021 ADS 2020 Patch 3)
Is the Azure DevOps Server On-Premises 2020.1.2 impacted by this issue and do we need to wait for a patch for this issue to be fixed?
How do we know the roll back is done?
We have a lot of PRs waiting for the build to pass successfully
The roll back is complete.