Skip to content

Remove some Travis-CI references #9919

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
TravisEz13 merged 4 commits into from
Jun 20, 2019
Merged

Remove some Travis-CI references #9919

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
7f5a220
Erase Travis CI from existance
RDIL Jun 17, 2019
edabd00
Update TestRoadmap.md
RDIL Jun 17, 2019
1179688
add back
RDIL Jun 17, 2019
d1c8b64
Update docs/testing-guidelines/TestRoadmap.md
RDIL Jun 17, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 1 addition & 4 deletions docs/testing-guidelines/TestRoadmap.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand All @@ -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
Expand Down
4 changes: 2 additions & 2 deletions tools/installpsh-osx.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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
Expand Down