-
Notifications
You must be signed in to change notification settings - Fork 1
/
appveyor.yml
77 lines (64 loc) · 3.22 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
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
# See http://www.appveyor.com/docs/appveyor-yml for many more options
# Notes:
# - Minimal appveyor.yml file is an empty file. All sections are optional (perhaps not 'build'. set it
# to 'off' as I have below if not needed).
# - Indent each level of configuration with 2 spaces. Do not use tabs!
# - All section names are case-sensitive.
# - Section names should be unique on each level.
# - appveyor.yml and UI coexistence:
# It's worth noticing that both appveyor.yml and UI configuration are mutually exclusive.
# It's always either YAML or UI - the settings from each are not merged. If you have appveyor.yml
# in your repo it will override all settings made on the UI unless explicitly disabled by Ignore
# appveyor.yml. There are few exceptions, which are:
# 1. Environment variables. Variables defined on UI are getting merged with those ones defined
# in appveyor.yml. Variable values with the same names are getting overridden with values from UI.
# 2. Notification settings defined on UI are getting merged with those ones defined in appveyor.yml.
# 3. Build version format is taken from UI if it is not set in appveyor.yml.
#
#---------------------------------#
# sequential steps #
#---------------------------------#
# scripts that are called at very beginning, before repo cloning
init:
- git config --global core.autocrlf input
cache:
- C:\Program Files\WindowsPowerShell\Modules\Pester
- C:\ProgramData\chocolatey
# scripts that run after cloning repository
install:
- ps: Write-Host "install"
- choco install Pester --version=3.4.6
- refreshenv
- ps: Write-Host $ENV:APPVEYOR_BUILD_FOLDER
- ps: New-Item "$ENV:APPVEYOR_BUILD_FOLDER\out-$($ENV:APPVEYOR_BUILD_VERSION)" -ItemType Directory
environment:
Out_Build: $(APPVEYOR_BUILD_FOLDER)\out-$(APPVEYOR_BUILD_VERSION)\outbuild
Out_Test: $(APPVEYOR_BUILD_FOLDER)\out-$(APPVEYOR_BUILD_VERSION)\outtest
My_NuGet_Api_Key:
secure: cO4umBABvn/thfk7Gd0/fcq8+h2Hfx1hFdGAkZn2zZhum1FSsQYBpd1neziRYUud
build_script:
- ps: Write-Host ("test_script - "+$ENV:OUT_BUILD)
- ps: powershell.exe -version 5.0 -executionpolicy bypass -noprofile -file .\build\appveyor.build.ps1 -Version 5
test_script:
- ps: Write-Host ("test_script - "+$ENV:OUT_TEST)
- ps: powershell.exe -version 5.0 -executionpolicy bypass -noprofile -file .\test\appveyor.pester.ps1 -Version 5
- ps: powershell.exe -version 5.0 -executionpolicy bypass -noprofile -file .\test\appveyor.pester.ps1 -Version 5 -Finalize
# Automatically register private account and/or project AppVeyor NuGet feeds.
#nuget:
# account_feed: true
# project_feed: true
artifacts:
- path: out-$(APPVEYOR_BUILD_VERSION)
name: PSTrueCrypt-$(APPVEYOR_BUILD_VERSION)
# deploys to: https://www.powershellgallery.com/packages/PSTrueCrypt
deploy_script:
- ps: Write-Host "deploy_script"
- ps: Publish-Module -Name $ENV:OUT_BUILD\PSTrueCrypt.psd1 -NuGetApiKey $ENV:MY_NUGET_API_KEY
#---------------------------------#
# variables #
#---------------------------------#
version: '{branch}.{build}'
# 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.*/