Win7/PowerShell7
1
0
Fork 0
Code Issues Pull Requests Projects Releases 1 Wiki Activity

Remove all reference to AppVeyor and Travis CI from docs (#8376)

Browse Source
This commit is contained in:
Aditya Patwardhan 2018-12-03 10:14:11 -08:00 committed by Travis Plunk
parent a11810bf33
commit a62eb62701
7 changed files with 15 additions and 27 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -152,9 +152,9 @@ If you have any problems building, please consult the developer [FAQ][].
### Build status of nightly builds
| AppVeyor (Windows) | Azure CI (Linux) | Azure CI (macOS) | Code Coverage Status | Code Factor Status |
| Azure CI (Windows) | Azure CI (Linux) | Azure CI (macOS) | Code Coverage Status | Code Factor Status |
|:-----------------------------------------|:-----------------------------------------------|:-----------------------------------------------|:-------------------------|:-------------------------|
| [![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] |
| [![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] |
[bd-linux]: https://github.com/PowerShell/PowerShell/tree/master/docs/building/linux.md
[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][].
[az-spell-image]: https://powershell.visualstudio.com/PowerShell/_apis/build/status/PowerShell-CI-spelling?branchName=master
[az-spell-site]: https://powershell.visualstudio.com/PowerShell/_build?definitionId=22
[tv-image]: https://travis-ci.org/PowerShell/PowerShell.svg?branch=master
[windows-nightly-site]: https://powershell.visualstudio.com/PowerShell/_build/latest?definitionId=32
[linux-nightly-site]: https://powershell.visualstudio.com/PowerShell/_build?definitionId=23
[macos-nightly-site]: https://powershell.visualstudio.com/PowerShell/_build?definitionId=24
[av-image]: https://ci.appveyor.com/api/projects/status/nsng9iobwa895f98/branch/master?svg=true
[av-site]: https://ci.appveyor.com/project/PowerShell/powershell
[windows-nightly-image]: https://powershell.visualstudio.com/PowerShell/_apis/build/status/PowerShell-CI-Windows-daily
[linux-nightly-image]: https://powershell.visualstudio.com/PowerShell/_apis/build/status/PowerShell-CI-linux-daily?branchName=master
[macOS-nightly-image]: https://powershell.visualstudio.com/PowerShell/_apis/build/status/PowerShell-CI-macos-daily?branchName=master
[av-nightly-image]: https://ci.appveyor.com/api/projects/status/46yd4jogtm2jodcq?svg=true

BIN
docs/testing-guidelines/Images/AppVeyor-Badge-Green.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 2.3 KiB

BIN
docs/testing-guidelines/Images/AzDevOps-Success.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 2.5 KiB

BIN
docs/testing-guidelines/Images/Travis-CI-Badge-Green.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 9.5 KiB

4
docs/testing-guidelines/WritingPesterTests.md
View File

@ -100,7 +100,7 @@ The `It` block is intended to be used inside of a `Describe` or `Context` block
### Admin privileges in tests
Tests that require admin privileges **on Windows** must be additionally marked with `RequireAdminOnWindows` Pester tag.
In the AppVeyor CI, we run two different passes:
In the Azure DevOps Windows CI, we run two different passes:
- The pass with exclusion of tests with `RequireAdminOnWindows` tag
- The pass where we run only `RequireAdminOnWindows` tests
@ -324,7 +324,7 @@ They cause problems for two reasons:
* They are different on different platforms (`\r\n` on Windows and `\n` on Unix).
* Even on the same system, they depends on the way how the repo was cloned.
Particularly, in the default AppVeyor CI Windows image, you will get `\n` line ends in all your files.
Particularly, in the default Azure DevOps CI Windows image, you will get `\n` line ends in all your files.
That causes problems, because at runtime `Get-MultiLineString` would likely produce `\r\n` line ends on windows.
Some workaround could be added, but they are sub-optimal and make reading test code harder.

24
docs/testing-guidelines/testing-guidelines.md
View File

@ -13,35 +13,21 @@ When adding new tests, place them in the directories as [outlined below](#test-l
## CI System
We use [AppVeyor](http://www.appveyor.com/) as a continuous integration (CI) system for Windows
and [Travis CI](http://www.travis-ci.com) for non-Windows platforms.
We use [Azure DevOps](https://azure.microsoft.com/en-us/solutions/devops) as a continuous integration (CI) system for Windows
and non-Windows platforms.
### AppVeyor
In the `README.md` at the top of the repo, you can see AppVeyor badge.
In the `README.md` at the top of the repository, you can see Azure CI badge.
It indicates the last build status of `master` branch.
Hopefully, it's green:
![AppVeyor-Badge-Green.png](Images/AppVeyor-Badge-Green.png)
This badge is **clickable**; you can open corresponding build page with logs, artifacts, and tests results.
From there you can easily navigate to the build history.
### Travis CI
Travis CI works similarly to AppVeyor.
For Travis CI there will be multiple badges.
The badges indicate the last build status of `master` branch for different platforms.
Hopefully, it's green:
![Travis-CI-Badge-Green.png](Images/Travis-CI-Badge-Green.png)
![AzDevOps-Success.png](Images/AzDevOps-Success.png)
This badge is **clickable**; you can open corresponding build page with logs, artifacts, and tests results.
From there you can easily navigate to the build history.
### Getting CI Results
CI System builds (AppVeyor and Travis CI) and runs tests on every pull request and provides quick feedback about it.
CI System builds and runs tests on every pull request and provides quick feedback about it.
![AppVeyor-Github](Images/AppVeyor-Github.png)

8
test/tools/CodeCoverageAutomation/README.md
View File

@ -6,13 +6,13 @@ The script is self contained and can be executed on any Windows system which sup
## Execution
The virtual machine hosting the script has a scheduled task to start the tests at 5 am PDT.
The virtual machine hosting the script has a scheduled task to start the tests at 5 am PDT.
The script follows the steps below:
1. Download the code coverage binaries package from AppVeyor nightly builds artifacts (CodeCoverage.zip).
2. Download the OpenCover powershell module from AppVeyor nightly builds artifacts. (OpenCover.zip)
3. Download the tests from AppVeyor nightly builds artifacts (tests.zip)
1. Download the code coverage binaries package from Azure DevOps Windows nightly builds artifacts (CodeCoverage.zip).
2. Download the OpenCover powershell module from Azure DevOps Windows nightly builds artifacts. (OpenCover.zip)
3. Download the tests from Azure DevOps Windows nightly builds artifacts (tests.zip)
4. Download Coveralls.net from 'https://github.com/csMACnz/coveralls.net/releases/download/0.7.0/coveralls.net.0.7.0.nupkg'
5. Invoke 'Install-OpenCover' to install OpenCover toolset.
6. Invoke 'Invoke-OpenCover' to execute tests.