Wednesday, September 30, 2020

Prioritizing Waiting Jobs in Azure Pipelines

While we are working with Azure DevOps pipelines for build and deployment purpose, we use several private and hosted agents. However, sometimes there are more CI and PR builds in the queues due to limited number of parallel job availability. While we do daily tasks, there can be situations where we need to release a bug fix quickly but pipelines have long queues. At that type of situation, team has to wait prior until all the builds on the queue get completed. This blog explains the feature available in Azure DevOps as a solution to this issue.

Go to the build logs of the build pipeline which need to be started next. In the logs you would be able to see the position of the current  build . As the following image the selected build is 4 th in the queue. We can click on the "Run next" to queue this build next as priority.

Thursday, September 17, 2020

Fix "unknown error: cannot find Chrome binary" Failure in UI Test Execution Using Test Clients in Azure DevOps Pipelines.

 This blog explains one of the issues faced by Test Automation team when executing the UI test scripts using Chrome web driver. Lets have a look at, what is the process Test Automation team followed and the issue encountered. Importantly let's see how it can be resolved. 

In the UI test scripts developed with Spec flow, Selenium and C#, the purpose is to run automated UI test using a CD pipeline. Team has setup a Azure DevOps agent to run in interactive mode and installed the chrome web browser in the agent VM. Once, pipelines are  executing the UI test automation using the test agent it has reported the following error.


System.AggregateException : One or more errors occurred. (unknown error: cannot find Chrome binary) (unknown error: cannot find Chrome binary)

---- OpenQA.Selenium.WebDriverException : unknown error: cannot find Chrome binary

---- OpenQA.Selenium.WebDriverException : unknown error: cannot find Chrome binary