Skip to content

Commit a62eb62

Browse files
adityapatwardhanTravisEz13
adityapatwardhan
authored and
TravisEz13
committed
Remove all reference to AppVeyor and Travis CI from docs (PowerShell#8376)
1 parent a11810b commit a62eb62

7 files changed

Lines changed: 15 additions & 27 deletions

File tree

‎README.md‎

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -152,9 +152,9 @@ If you have any problems building, please consult the developer [FAQ][].
152152

153153
### Build status of nightly builds
154154

155-
| AppVeyor (Windows) | Azure CI (Linux) | Azure CI (macOS) | Code Coverage Status | Code Factor Status |
155+
| Azure CI (Windows) | Azure CI (Linux) | Azure CI (macOS) | Code Coverage Status | Code Factor Status |
156156
|:-----------------------------------------|:-----------------------------------------------|:-----------------------------------------------|:-------------------------|:-------------------------|
157-
| [![av-nightly-image][]][av-nightly-site] | [![linux-nightly-image][]][linux-nightly-site] | [![macOS-nightly-image][]][macos-nightly-site] | [![cc-image][]][cc-site] | [![cf-image][]][cf-site] |
157+
| [![windows-nightly-image][]][windows-nightly-site] | [![linux-nightly-image][]][linux-nightly-site] | [![macOS-nightly-image][]][macos-nightly-site] | [![cc-image][]][cc-site] | [![cf-image][]][cf-site] |
158158

159159
[bd-linux]: https://github.com/PowerShell/PowerShell/tree/master/docs/building/linux.md
160160
[bd-windows]: https://github.com/PowerShell/PowerShell/tree/master/docs/building/windows-core.md
@@ -171,10 +171,12 @@ If you have any problems building, please consult the developer [FAQ][].
171171
[az-spell-image]: https://powershell.visualstudio.com/PowerShell/_apis/build/status/PowerShell-CI-spelling?branchName=master
172172
[az-spell-site]: https://powershell.visualstudio.com/PowerShell/_build?definitionId=22
173173
[tv-image]: https://travis-ci.org/PowerShell/PowerShell.svg?branch=master
174+
[windows-nightly-site]: https://powershell.visualstudio.com/PowerShell/_build/latest?definitionId=32
174175
[linux-nightly-site]: https://powershell.visualstudio.com/PowerShell/_build?definitionId=23
175176
[macos-nightly-site]: https://powershell.visualstudio.com/PowerShell/_build?definitionId=24
176177
[av-image]: https://ci.appveyor.com/api/projects/status/nsng9iobwa895f98/branch/master?svg=true
177178
[av-site]: https://ci.appveyor.com/project/PowerShell/powershell
179+
[windows-nightly-image]: https://powershell.visualstudio.com/PowerShell/_apis/build/status/PowerShell-CI-Windows-daily
178180
[linux-nightly-image]: https://powershell.visualstudio.com/PowerShell/_apis/build/status/PowerShell-CI-linux-daily?branchName=master
179181
[macOS-nightly-image]: https://powershell.visualstudio.com/PowerShell/_apis/build/status/PowerShell-CI-macos-daily?branchName=master
180182
[av-nightly-image]: https://ci.appveyor.com/api/projects/status/46yd4jogtm2jodcq?svg=true

‎docs/testing-guidelines/Images/AppVeyor-Badge-Green.png‎

-2.28 KB
Binary file not shown.

‎docs/testing-guidelines/Images/AzDevOps-Success.png‎

2.54 KB
Loading

‎docs/testing-guidelines/Images/Travis-CI-Badge-Green.png‎

-9.47 KB
Binary file not shown.

‎docs/testing-guidelines/WritingPesterTests.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -100,7 +100,7 @@ The `It` block is intended to be used inside of a `Describe` or `Context` block
100100
### Admin privileges in tests
101101

102102
Tests that require admin privileges **on Windows** must be additionally marked with `RequireAdminOnWindows` Pester tag.
103-
In the AppVeyor CI, we run two different passes:
103+
In the Azure DevOps Windows CI, we run two different passes:
104104

105105
- The pass with exclusion of tests with `RequireAdminOnWindows` tag
106106
- The pass where we run only `RequireAdminOnWindows` tests
@@ -324,7 +324,7 @@ They cause problems for two reasons:
324324
* They are different on different platforms (`\r\n` on Windows and `\n` on Unix).
325325
* Even on the same system, they depends on the way how the repo was cloned.
326326

327-
Particularly, in the default AppVeyor CI Windows image, you will get `\n` line ends in all your files.
327+
Particularly, in the default Azure DevOps CI Windows image, you will get `\n` line ends in all your files.
328328
That causes problems, because at runtime `Get-MultiLineString` would likely produce `\r\n` line ends on windows.
329329

330330
Some workaround could be added, but they are sub-optimal and make reading test code harder.

‎docs/testing-guidelines/testing-guidelines.md‎

Lines changed: 5 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -13,35 +13,21 @@ When adding new tests, place them in the directories as [outlined below](#test-l
1313

1414
## CI System
1515

16-
We use [AppVeyor](http://www.appveyor.com/) as a continuous integration (CI) system for Windows
17-
and [Travis CI](http://www.travis-ci.com) for non-Windows platforms.
16+
We use [Azure DevOps](https://azure.microsoft.com/en-us/solutions/devops) as a continuous integration (CI) system for Windows
17+
and non-Windows platforms.
1818

19-
### AppVeyor
20-
21-
In the `README.md` at the top of the repo, you can see AppVeyor badge.
19+
In the `README.md` at the top of the repository, you can see Azure CI badge.
2220
It indicates the last build status of `master` branch.
2321
Hopefully, it's green:
2422

25-
![AppVeyor-Badge-Green.png](Images/AppVeyor-Badge-Green.png)
26-
27-
This badge is **clickable**; you can open corresponding build page with logs, artifacts, and tests results.
28-
From there you can easily navigate to the build history.
29-
30-
### Travis CI
31-
32-
Travis CI works similarly to AppVeyor.
33-
For Travis CI there will be multiple badges.
34-
The badges indicate the last build status of `master` branch for different platforms.
35-
Hopefully, it's green:
36-
37-
![Travis-CI-Badge-Green.png](Images/Travis-CI-Badge-Green.png)
23+
![AzDevOps-Success.png](Images/AzDevOps-Success.png)
3824

3925
This badge is **clickable**; you can open corresponding build page with logs, artifacts, and tests results.
4026
From there you can easily navigate to the build history.
4127

4228
### Getting CI Results
4329

44-
CI System builds (AppVeyor and Travis CI) and runs tests on every pull request and provides quick feedback about it.
30+
CI System builds and runs tests on every pull request and provides quick feedback about it.
4531

4632
![AppVeyor-Github](Images/AppVeyor-Github.png)
4733

‎test/tools/CodeCoverageAutomation/README.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,13 +6,13 @@ The script is self contained and can be executed on any Windows system which sup
66

77
## Execution
88

9-
The virtual machine hosting the script has a scheduled task to start the tests at 5 am PDT.
9+
The virtual machine hosting the script has a scheduled task to start the tests at 5 am PDT.
1010

1111
The script follows the steps below:
1212

13-
1. Download the code coverage binaries package from AppVeyor nightly builds artifacts (CodeCoverage.zip).
14-
2. Download the OpenCover powershell module from AppVeyor nightly builds artifacts. (OpenCover.zip)
15-
3. Download the tests from AppVeyor nightly builds artifacts (tests.zip)
13+
1. Download the code coverage binaries package from Azure DevOps Windows nightly builds artifacts (CodeCoverage.zip).
14+
2. Download the OpenCover powershell module from Azure DevOps Windows nightly builds artifacts. (OpenCover.zip)
15+
3. Download the tests from Azure DevOps Windows nightly builds artifacts (tests.zip)
1616
4. Download Coveralls.net from 'https://github.com/csMACnz/coveralls.net/releases/download/0.7.0/coveralls.net.0.7.0.nupkg'
1717
5. Invoke 'Install-OpenCover' to install OpenCover toolset.
1818
6. Invoke 'Invoke-OpenCover' to execute tests.

0 commit comments

Comments
 (0)