admin/PowerShell-PowerShell
1
0
Fork 0
mirror of https://github.com/PowerShell/PowerShell synced 2026-06-08 12:12:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

Remove some Travis-CI references (#9919)

Browse Source
This commit is contained in:
Reece Dunham
2019-06-20 11:08:32 -07:00
committed by Travis Plunk
parent 66e571b19f
commit 4223bf1f8e
2 changed files with 3 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/testing-guidelines/TestRoadmap.md
+1 -4
View File
@@ -79,7 +79,7 @@ We need to be sure that we can easily enable remoting for the non-Windows platfo
* Our current multi-machine tests do not test the connection code, they simply execute test code remotely and retrieve results and assume a good connection.
The infrastructure used for these tests is STEX which is not an open environment.
We will need to create automation to create and configure the test systems in the test matrix and then invoke tests on them.
It is not clear that our current CI systems can accommodate our needs here as neither AppVeyor or Travis can supply us with all of the OS images needed.
It is not clear that our current CI systems can accommodate our needs here as Azure DevOps can supply us with all of the OS images needed.
We may need to create our own heterogeneous environment in Azure, or look to other teams (MS Build Lab/Jenkins) for assistance.
We need to investigate whether there are solutions available, and if not, design/implement an environment to meet our needs.
@@ -88,9 +88,6 @@ We need to investigate whether there are solutions available, and if not, design
Currently, we report against the simplest of KPI:
* is the CI build error free (which is part of the PR/Merge process - and reported on our landing page)
We are also collecting data for a daily build, but not yet report on the following KPI
* is the daily build error free (we are running this on AppVeyor, we still need to do this for Travis-CI)
There are a number of KPIs which we could report on:
* Code KPIs
* What is the coverage (% blocks covered) of our `CI` tests