This post was most recently updated on December 6th, 2019.2 min read.
Uh, okay, well. So this is where you should just RTFM (that’s along the lines of “check the documentation” for those uninitiated in the world of unnecessary abbreviations). But as we’ve found out before, Microsoft’s documentation on the agent’s installed software isn’t always up-to-date. That’s why I added this simple snippet on my pipeline to figure out which version of the browser AND the webdriver are installed on the machine.
The snippets below can be combined with logic to install different versions of Chrome and the WebDriver, if need be. And of course, while I’m using Chrome, you could use Firefox and the GeckoWebDriver instead – it’s just a matter of changing the respective apps in the snippets!
Well, this turned out to be fairly simple. For our convenience, let’s echo both the VersionInfo of the browser executable and the version output of the WebDriver!
The following YAML will output the Chrome and Chrome WebDriver versions nicely in your build log.
- powershell: | (Get-Item "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe").VersionInfo displayName: 'We want to know the Chrome version installed on this darned machine' - pwsh: | chromeDriver -v displayName: Echo Chrome WebDriver version
If you get an error, something like below:
chromeDriver : The term 'chromeDriver' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
Then see this post on how to configure your pipeline to use the WebDriver that’s installed on the build agent already:
And that’s about it. If you run into any issues, let me know in the comments section below!
- How to fix a Logic App deployment that failed with error “ApiNotFound”? - April 22, 2021
- Experiment: DateTime formats - April 21, 2021
- How to fix “LinkedAuthorizationFailed” when deploying an Azure Logic App? - April 15, 2021