These are chat archives for bluefin-octopusdeploy/chrome-extension

29th
Jun 2016
David Roberts
@davidroberts63
Jun 29 2016 05:14
AppVeyor + SauceLabs + Azure VM . Browser testing is in flight. Now to scale it up a bit.
AppVeyor: https://ci.appveyor.com/project/BluefinOctopusDeploy/chrome-extension/build/1.0.21
SauceLabs:
Matt Richardson
@matt-richardson
Jun 29 2016 05:52
Nice. How were you thinking of handling multiple versions of OD?
David Roberts
@davidroberts63
Jun 29 2016 12:28
Multiple VMs and power shell kicking off separate browser test processes for each VM. I'm definitely open to ideas. I've also thought about making multiple builds in AppVeyor. But the free option only allows for one build at a time.
Matt Richardson
@matt-richardson
Jun 29 2016 12:37
When I get a chance, I'm gonna finish off the docker stuff, so then it'll be possible to run multiple OD instances at the same time. Still got a fair chunk of work to go on that though.
that might be a useful approach for this.
the azure cli is available for Linux so it might be possible to use the build matrix feature of travis to handle the different versions
It'll be nice to tie the appveyor build into the PR checks on GitHub.
David Roberts
@davidroberts63
Jun 29 2016 12:56
Hadn't thought about the build matrix I'll look at that.
Yes I'd like to get this hooked into the PR process too.
Matt Richardson
@matt-richardson
Jun 29 2016 14:50
I wonder if it'd be a good idea to have a single check per OD (major) version to make it obvious which version failed...
But that might mean an overhead on managing that for every OD release.
David Roberts
@davidroberts63
Jun 29 2016 16:08
Yeah, that's an idea to consider. Because that's what we really want to know, which OD version is causing a problem. We will have to dig into it either way. At the moment I'm only testing 3.3.17. I haven't automated the VM creation because it increases the build job time significantly.