Official Stryker CI tool installer tasks

Most CI’s available have some form of tool installer plug-in support. Since we have tool installation support that is independent of project package references we could support such build tasks to install stryker in the CI pipeline. This would mean that stryker can be run on projects that might not necessarily have a dependency on stryker. This would also increase the visibility of stryker. All the build task would have to do is dotnet tool install StrykerMutator.DotNetCoreCli --tool-path <build agent workdir tool path> --version <version chosen to install in build>

It is important that --tool-path is used and not -g as we absolutely do not want a global install on a build agent.

For vsts see: https://github.com/Microsoft/vsts-task-tool-lib https://github.com/Microsoft/vsts-task-tool-lib/blob/master/docs/overview.md https://github.com/Microsoft/vsts-task-tool-lib/blob/master/sample.ts

Any other platforms are welcome as well I’m sure. If for example anyone is interested in creating a jenkins tool installer plugin I will be able to give some guidance.

[ptoonen]

Starting work on this.

[rouke-broersma]

Stryker has been refactored to a dotnet core tool. A task specifically for installing stryker in the build is not neccesary at this time. I would expect most users will migrate to local tools as well starting with dotnet core 3.0 and we will start suggesting the local tool as the recommended way of installing stryker.