-
-
Notifications
You must be signed in to change notification settings - Fork 66
/
appveyor.yml
45 lines (37 loc) · 1.53 KB
/
appveyor.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
# See http://www.appveyor.com/docs/appveyor-yml for many more options
os: Visual Studio 2015
# Init variables for publishing to PowerShell Gallery or GitHub
environment:
ModuleName: $(APPVEYOR_PROJECT_NAME) # Hard code if you really need to...
GitHubRelease: $(APPVEYOR_PROJECT_NAME)-v1.1.0 # TODO: extract version from PSD1...
NugetApiKey: # Add your API key to AppVeyor, paste the encrypted bit here
secure: oqMFzG8F65K5l572V7VzlZIWU7xnSYDLtSXECJAAURrXe8M2+BAp9vHLT+1h1lR0
#Beware the infinite rebuild bug. Woke up to 84 new releases!
skip_tags: true
# Skip on updates to the readme.
# We can force this by adding [skip ci] or [ci skip] anywhere in commit message
skip_commits:
message: /updated readme.*/
# PS2 compat
install:
- cinst pester -y --version=4.10.1
# Package things up.
build_script:
- 7z a %ModuleName%.zip %ModuleName%\
# Test with native PS and PS version 2. Upload test results
test_script:
# Set up pester path for PSv2
- ps: . .\Tests\Helpers\Initialize-PesterPath.ps1
# Test in PSv2
- ps: powershell.exe -version 2.0 -executionpolicy bypass -noprofile -file .\Tests\Helpers\Invoke-PesterFromAppveyor.ps1
# Test in native PS
- ps: . .\Tests\Helpers\Invoke-PesterFromAppveyor.ps1
# Collect all test results, fail if any failures
- ps: . .\Tests\Helpers\Read-PesterOutput.ps1
# zipped package for delivery
artifacts:
- path: $(ModuleName).zip
# Duct tape, until this is implemented:
# https://github.com/appveyor/ci/issues/128
deploy_script:
- ps: . .\Tests\Helpers\Invoke-PSGalleryDeployment.ps1