azure devops server
5 TopicsOn Premise DevOps 2022 CI/CD pipeline to Host Application on IIS
Hi All, We have deployed DevOps 2022 server on our On-Premise server which we upgraded from TFS 2018. I would like to know the steps about Build and Release pipeline which can auto deploy application on my IIS server. We have around 15 Projects deployed in new DevOps server and all our developers are doing source code check in and check out. Below is my setup details and development technology used in my company. 1. Active Directory Environment. (Separate AD server) 2. DevOps Server 2022 Installed on Physical Sever. ( Domain Joined) 3. Physical Test Server having IIS configured. 4. Physical SQL database server. 5. Development is on ASP .NET Core, Angular, and ASP .Net 6. Developers having Visual Studio 2019 and Visual 2012 Professional Edition. ( 15 Developers) Need your help in setting up a complete automated process. Regards Imran ShaikhSolved4.4KViews0likes4CommentsError in deleting test cases using Azure DevOps extension API
Hello DevOps Team, I have created an extension to delete the Test runs and Test cases in bulk. I'm able to delete the Test runs from separate hub page. For deleting test cases, We have created an (ms.vss-web.action) web action to query result windows on following target (ms.vss-work-web.query-result-work-item-menu). When user are deleting the test cases, its giving following error. Delete https://devops.url/azure/defaultcollection/projectid/_api/test/testcases/123456 net::Err_Failed 401 Network Exception: TF400893: unable to contact the server. Please check your network connection and try again. unhandled exception in fetch for https://devops.url/azure/defaultcollection/projectid/_api/test/testcases/123456 Extension have following scopes: [vs.test, vso.test_write] Debugging: Before deleting test case, I have also tired reading & deleting the TestRun to check, if that's is also failing. But it ran successfully. But when deleting the test case, it just fail with following above errors. I have all the associated right on the DevOps Server. Code. async function DeleteTestCasebyId(projectId:string, testCaseId:number): Promise<boolean>{ try{ const result = await getClient(TestRestClient).deteteTestCase(projectId,testCaseId); return true; }catch(e){ console.log(e); return false; } } Could please point what's the right solution for this? Regards, Ajit1.5KViews0likes0CommentsActive Directory Users Remapping in DevOps Server 2022
Hi All, We had a ransomware attack on our AD server and DevOps server. Luckily I had a backup of the DevOps server which I restored back after formating both the servers. I did not change anything after format hostname of DevOps & AD server, IP address, the domain name , created same user names in active directory, everything I have kept identical. After installation and configuring DevOps AD users are not able to log in to DevOps. It keeps asking for credentials whenever a user tries to connect. Is there any option in TFS to remap active directory users? Please let me know. There are so many project created in TFS and its impossible for us to go and add AD users again on each project. Regards Imran Shaikh359Views0likes1CommentLegacy SSRS reports after upgrading Azure DevOps Server 2020 to 2022 or 25H2
We are currently planning an upgrade from Azure DevOps Server 2020 to Azure DevOps Server 2022 or 25H2, and one of our biggest concerns is reporting. We understand that Microsoft’s recommended direction is to move to Power BI based on Analytics / OData. However, for on-prem environments with a large number of existing SSRS reports, rebuilding everything from scratch would require significant time and effort. Since Warehouse and Analysis Services are no longer available in newer versions, we would like to understand how other on-prem teams are handling legacy SSRS reporting during and after the upgrade. Have you rebuilt your reports in Power BI, moved to another reporting approach, or found a practical way to keep existing SSRS reports available during the transition? Any real-world experience, lessons learned, or recommended approaches would be greatly appreciated.28Views0likes0Comments