3party/pugixml
0
0
Fork 0
mirror of https://github.com/zeux/pugixml.git synced 2024-12-27 13:33:17 +08:00
Code Issues Projects Releases Wiki Activity
pugixml/appveyor.yml

23 lines
1.4 KiB
YAML
Raw Normal View History

use 2 images to build on appveyor
2017-06-15 11:49:10 +03:00
image:
Update nuget creation to VS2019 (#291) Create visual studio projects that are vs2019 compliant. * nuget_build.ps1 : Introduce a new argument that will define how we implement the nuget build. For now we accept 201{9,7.5.3} as possible argument values. * pugixml_vs2019{,_static}.vcxproj : Add two visual studio projects that build pugi with the latest SDK and build tools * appveyor.yml - Add Visual Studio 2019 to build targets - Add Visual Studio 201{9,3,5} to build_scripts. And call nuget_build.ps1 with a new argument. - Add Visual Studio 2019 to the test_scripts.
2019-09-09 16:37:29 +02:00
- Visual Studio 2019
Add VS2017 to AppVeyor test run This requires moving the list of VS versions out of autotest-appveyor.ps1 and into appveyor.yml.
2017-06-18 21:21:58 -07:00
- Visual Studio 2017
Update nuget creation to VS2019 (#291) Create visual studio projects that are vs2019 compliant. * nuget_build.ps1 : Introduce a new argument that will define how we implement the nuget build. For now we accept 201{9,7.5.3} as possible argument values. * pugixml_vs2019{,_static}.vcxproj : Add two visual studio projects that build pugi with the latest SDK and build tools * appveyor.yml - Add Visual Studio 2019 to build targets - Add Visual Studio 201{9,3,5} to build_scripts. And call nuget_build.ps1 with a new argument. - Add Visual Studio 2019 to the test_scripts.
2019-09-09 16:37:29 +02:00
- Visual Studio 2015
Appveyor image set to VS2017
2017-06-15 11:14:28 +03:00
Add branch name to AppVeyor version
2015-04-13 20:38:52 -07:00
version: "{branch}-{build}"
Add AppVeyor build scripts
2015-04-13 20:03:49 -07:00
build_script:
Update nuget creation to VS2019 (#291) Create visual studio projects that are vs2019 compliant. * nuget_build.ps1 : Introduce a new argument that will define how we implement the nuget build. For now we accept 201{9,7.5.3} as possible argument values. * pugixml_vs2019{,_static}.vcxproj : Add two visual studio projects that build pugi with the latest SDK and build tools * appveyor.yml - Add Visual Studio 2019 to build targets - Add Visual Studio 201{9,3,5} to build_scripts. And call nuget_build.ps1 with a new argument. - Add Visual Studio 2019 to the test_scripts.
2019-09-09 16:37:29 +02:00
- ps: if ($env:APPVEYOR_BUILD_WORKER_IMAGE -eq "Visual Studio 2013") { .\scripts\nuget_build.ps1 2013}
- ps: if ($env:APPVEYOR_BUILD_WORKER_IMAGE -eq "Visual Studio 2015") { .\scripts\nuget_build.ps1 2015}
- ps: if ($env:APPVEYOR_BUILD_WORKER_IMAGE -eq "Visual Studio 2017") { .\scripts\nuget_build.ps1 2017}
- ps: if ($env:APPVEYOR_BUILD_WORKER_IMAGE -eq "Visual Studio 2019") { .\scripts\nuget_build.ps1 2019}
Build NuGet package on AppVeyor
2015-10-18 21:10:45 -07:00
test_script:
Add VS2017 to AppVeyor test run This requires moving the list of VS versions out of autotest-appveyor.ps1 and into appveyor.yml.
2017-06-18 21:21:58 -07:00
- ps: if ($env:APPVEYOR_BUILD_WORKER_IMAGE -eq "Visual Studio 2015") { .\tests\autotest-appveyor.ps1 9 10 11 12 14 }
- ps: if ($env:APPVEYOR_BUILD_WORKER_IMAGE -eq "Visual Studio 2017") { .\tests\autotest-appveyor.ps1 15 }
Update nuget creation to VS2019 (#291) Create visual studio projects that are vs2019 compliant. * nuget_build.ps1 : Introduce a new argument that will define how we implement the nuget build. For now we accept 201{9,7.5.3} as possible argument values. * pugixml_vs2019{,_static}.vcxproj : Add two visual studio projects that build pugi with the latest SDK and build tools * appveyor.yml - Add Visual Studio 2019 to build targets - Add Visual Studio 201{9,3,5} to build_scripts. And call nuget_build.ps1 with a new argument. - Add Visual Studio 2019 to the test_scripts.
2019-09-09 16:37:29 +02:00
- ps: if ($env:APPVEYOR_BUILD_WORKER_IMAGE -eq "Visual Studio 2019") { .\tests\autotest-appveyor.ps1 19 }
Fix PowerShell errors on stderr PS invocation of code coverage upload gets triggered because of stderr output from curl with progress report when uploading coverage.
2020-07-06 07:59:29 -07:00
- ps: if ($env:APPVEYOR_BUILD_WORKER_IMAGE -eq "Visual Studio 2015") { & C:\cygwin\bin\bash.exe -c "PATH=/usr/bin:/usr/local/bin:$PATH; make config=coverage test && bash <(curl -s https://codecov.io/bash) -f pugixml.cpp.gcov 2>&1" }
- ps: if ($env:APPVEYOR_BUILD_WORKER_IMAGE -eq "Visual Studio 2015") { & C:\cygwin\bin\bash.exe -c "PATH=/usr/bin:/usr/local/bin:$PATH; make config=coverage defines=PUGIXML_WCHAR_MODE test && bash <(curl -s https://codecov.io/bash) -f pugixml.cpp.gcov 2>&1" }
Build NuGet package on AppVeyor
2015-10-18 21:10:45 -07:00
artifacts:
Add VS2017 to AppVeyor test run This requires moving the list of VS versions out of autotest-appveyor.ps1 and into appveyor.yml.
2017-06-18 21:21:58 -07:00
- path: .\scripts\*.nupkg
Reference in New Issue Copy Permalink