Sign in to Azure DevOps
The https://dev.azure.com URL redirects to the landing page for the Azure DevOps product. I used to promote this as an URL to use to login to the product. Since this year the page is missing the "Already have an account? Sing in to Azure DevOps" link. As far as I can see there is no way to login to Azure DevOps trough this interface now. There is the usual "sing in" in the top right, which will redirect you to the azure portal (or at least for me it does). How are we supposed to login to Azure DevOps? Old login:The History of Microsoft Azure
Learn about the history of Microsoft Azure a leading giant in the cloud service industry which offers rich services on platform as a service (PaaS), software as a service (Saas) and infrastructure as a service (IaaS). This will take us back to the moments on how this powerful and sophisticated service began, revealing the resilience and vision of the Microsoft company as a brand, the present stages and how to partake of the cake Microsoft has provided for businesses and developers.Azure DevOps - How to modify files during a Build Pipeline execution based on PowerShell
Azure DevOps Build Pipeline can provide several option, but sometime we need to change a part of content extracted from Source code management (e.g. Git) before execute another task. In my case, this case is to comment one specific declaration (#include) placed in couple of JavaScript files. These lines are understood well by the application server using this code, but not by generic JavaScript parser used for example into SonarQube. So into the Pipeline process, it's only a PowerShell task could be used to do that like following. In Yaml mode: steps: - powershell: | Write-Host "------------------------------------------------------------" Write-Host "Get JS File content containing #include line", $(Agent.WorkFolder) Write-Host "------------------------------------------------------------" $AllJSFIleToManage = Get-ChildItem -Path $(Agent.WorkFolder)\*.js -Recurse -Force | Select-String -Pattern "#include " -AllMatches | Foreach {$_.Path} | Select-Object -Unique foreach ($MyFile in $AllJSFIleToManage) { Write-Host "JS File to change -", $MyFile (Get-Content $MyFile -Encoding UTF8) -replace '#include ', '//#include ' | Set-Content $MyFile Write-Host "JS File changed -", $MyFile Write-Host " -----------------------------------" } displayName: 'PowerShell Script remove specific #Include lines from JS files for Sonar' In Visual Editor mode: When the pipeline is running, it will get the source code from Git and change dynamically only the JS files replacing the blocks found with this "#include" by "//#include" to comment the concerned lines in JavaScript. The result of this execution in Pipeline log is like following: Into SonarQube the result is visible via the Source Code navigation option: You can adapt this code with your specific case and need, but PowerShell tasks are really powerful when you need to change something before a specific step only during the Pipeline execution. Fabrice Romelard
How do I change the date format in all areas of Azure DevOps web interface?
Hello. I'm fairly new to Azure DevOps and I've just started setting up some projects ready to migrate away from JIRA. However, something I cannot figure out is how to change the date formats in the DevOps web interface. We are in the UK and want UK format dates everywhere (dd/mm/yyyy). I have found that I can change this in my User Settings but it hasn't changed what I see in various screens. For example, dashboard widgets still show American dates. Burndown Trends still show American dates. This is really frustrating. How do I configure UK dates for all areas for all users? All of our projects will be the same, we will never ever use American dates. I've gone through project settings and organisation settings but can't find it anywhere, and Googling returned nothing useful. Thanks in advance.How to Use Azure Pipeline Task and Job Conditions
Azure Pipeline conditions allow us to define conditions under which a task or job will execute. In this blog post, I will detail a common situation in which pipeline conditions are helpful, the configuration of this condition, and will include documentation links for more information.
How to grant Service Principle access right to Azure Repos
In Azure Pipelines, we need to get source code of another organization's Azure Repos. Currently we use personal access token, but it links to a user who might leave the organization. Can we use a service principle to authenticate? How to grant the service principle access right to the other organization's Azure Repos?
Azure OpenAI GPT model to review Pull Requests for Azure DevOps
In recent months, the use of Generative Pre-trained Transformer (GPT) models for natural language processing (NLP) has gained significant traction. GPT models, which are based on the Transformer architecture, can generate text from arbitrary sources of input data and can be trained to identify errors and detect anomalies in text. As such, GPT models are increasingly being used for a variety of applications, ranging from natural language understanding to text summarization and question-answering. In the software development world, developers use pull requests to submit proposed changes to a codebase. However, reviews by other developers can sometimes take a long time and not accurate, and in some cases, these reviews can introduce new bugs and issues. In order to reduce this risk, During my research I found the integration of GPT models is possible and we can add Azure OpenAI service as pull request reviewers for Azure Pipelines service. The GPT models are trained on developer codebases and are able to detect potential coding issues such as typos, syntax errors, style inconsistencies and code smells. In addition, they can also assess code structure and suggest improvements to the overall code quality. Once the GPT models have been trained, they can be integrated into the Azure Pipelines service so that they can automatically review pull requests and provide feedback. This helps to reduce the time taken for code reviews, as well as reduce the likelihood of introducing bugs and issues.
