From 7f5a2203598de16961ddcd85e12fd0b5232c4299 Mon Sep 17 00:00:00 2001 From: Reece Dunham Date: Mon, 17 Jun 2019 15:38:38 -0700 Subject: [PATCH 1/4] Erase Travis CI from existance --- tools/installpsh-osx.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tools/installpsh-osx.sh b/tools/installpsh-osx.sh index d61be1da18b..ff199085dd7 100755 --- a/tools/installpsh-osx.sh +++ b/tools/installpsh-osx.sh @@ -103,7 +103,7 @@ if ! hash brew 2>/dev/null; then exit 3 fi -# Suppress output, it's very noisy on travis-ci +# Suppress output, it's very noisy on Azure DevOps echo "Refreshing Homebrew cache..." for count in {1..2}; do # Try the update twice if the first time fails @@ -123,7 +123,7 @@ for count in {1..2}; do sleep 5 done -# Suppress output, it's very noisy on travis-ci +# Suppress output, it's very noisy on Azure DevOps if [[ ! -d $(brew --prefix cask) ]]; then echo "Installing cask..." if ! brew tap caskroom/cask >/dev/null; then From edabd00d919ce150608edb6a9ddf96b0f0da68d4 Mon Sep 17 00:00:00 2001 From: Reece Dunham Date: Mon, 17 Jun 2019 15:44:18 -0700 Subject: [PATCH 2/4] Update TestRoadmap.md --- docs/testing-guidelines/TestRoadmap.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/docs/testing-guidelines/TestRoadmap.md b/docs/testing-guidelines/TestRoadmap.md index ad8cc160c62..b9ba3977881 100644 --- a/docs/testing-guidelines/TestRoadmap.md +++ b/docs/testing-guidelines/TestRoadmap.md @@ -79,7 +79,6 @@ 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. 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 +87,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 From 11796880e7a5b2201dfe32ba45e8c3deb735336b Mon Sep 17 00:00:00 2001 From: Reece Dunham Date: Mon, 17 Jun 2019 15:47:22 -0700 Subject: [PATCH 3/4] add back --- docs/testing-guidelines/TestRoadmap.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/testing-guidelines/TestRoadmap.md b/docs/testing-guidelines/TestRoadmap.md index b9ba3977881..7f3df3568e6 100644 --- a/docs/testing-guidelines/TestRoadmap.md +++ b/docs/testing-guidelines/TestRoadmap.md @@ -79,6 +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 Azure DevOps can't 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. From d1c8b640e2d9b4007af71040b0eb3ec482925a29 Mon Sep 17 00:00:00 2001 From: Reece Dunham Date: Mon, 17 Jun 2019 15:52:19 -0700 Subject: [PATCH 4/4] Update docs/testing-guidelines/TestRoadmap.md Co-Authored-By: Travis Plunk --- docs/testing-guidelines/TestRoadmap.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/testing-guidelines/TestRoadmap.md b/docs/testing-guidelines/TestRoadmap.md index 7f3df3568e6..aea71be5aec 100644 --- a/docs/testing-guidelines/TestRoadmap.md +++ b/docs/testing-guidelines/TestRoadmap.md @@ -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 Azure DevOps can't 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.