cheng/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
8f9e679393
wxWidgets/appveyor.yml

109 lines
2.9 KiB
YAML
Raw Normal View History

Quick fix to version string in AppVeyor config.
2015-11-04 09:33:43 -05:00
version: '{build}'
Added initial AppVeyor config.
2015-11-04 09:30:27 -05:00
branches:
only:
- master
- WX_3_0_BRANCH
Skip AppVeyor CI builds on documentation-only changes There is no need to rebuild everything if only the documentation files have changed. Unfortunately there doesn't seem to be any way to do the same thing for Travis CI yet, see https://github.com/travis-ci/travis-ci/issues/6301
2017-11-25 04:46:39 -05:00
skip_commits:
files:
Add more ignored paths for AppVeyor CI AppVeyor CI builds for Microsoft Windows only. Therefore, do not start builds for changes made only in dfb, gtk, gtk1, motif, unix, and x11 folders. Additionally, do not start the builds when only an *.md file in the root folder changes. Lastly, ignore all changes in the demos folder: Demos are not built by AppVeyor at all.
2021-03-02 14:21:21 -05:00
- demos/
Skip AppVeyor CI builds on documentation-only changes There is no need to rebuild everything if only the documentation files have changed. Unfortunately there doesn't seem to be any way to do the same thing for Travis CI yet, see https://github.com/travis-ci/travis-ci/issues/6301
2017-11-25 04:46:39 -05:00
- docs/
- interface/
Don't start CI builds for the changes to message catalogs only We currently don't use these files in the existing builds. It might be a good idea to add another GitHub Action workflow checking the message catalogs compilation that would be executed _only_ for the changes to them, but this can/will be done later.
2021-03-07 17:48:25 -05:00
- locale/
Skip AppVeyor CI builds on documentation-only changes There is no need to rebuild everything if only the documentation files have changed. Unfortunately there doesn't seem to be any way to do the same thing for Travis CI yet, see https://github.com/travis-ci/travis-ci/issues/6301
2017-11-25 04:46:39 -05:00
- misc/
Add more ignored paths for AppVeyor CI AppVeyor CI builds for Microsoft Windows only. Therefore, do not start builds for changes made only in dfb, gtk, gtk1, motif, unix, and x11 folders. Additionally, do not start the builds when only an *.md file in the root folder changes. Lastly, ignore all changes in the demos folder: Demos are not built by AppVeyor at all.
2021-03-02 14:21:21 -05:00
- include/wx/dfb/
- src/dfb/
- include/wx/gtk/
- src/gtk/
- include/wx/gtk1/
- src/gtk1/
- include/wx/motif/
- src/motif/
Disable AppVeyor rebuilds on Mac files changes too As long as we don't test under AppVeyor, there is no need to do anything there when only Mac-specific files are changed.
2020-04-22 11:18:11 -04:00
- include/wx/osx/
- src/osx/
Add more ignored paths for AppVeyor CI AppVeyor CI builds for Microsoft Windows only. Therefore, do not start builds for changes made only in dfb, gtk, gtk1, motif, unix, and x11 folders. Additionally, do not start the builds when only an *.md file in the root folder changes. Lastly, ignore all changes in the demos folder: Demos are not built by AppVeyor at all.
2021-03-02 14:21:21 -05:00
- include/wx/unix/
- src/unix/
- include/wx/x11/
- src/x11/
Do not trigger build by change in any MD file Co-authored-by: VZ <vz-github@zeitlins.org>
2021-03-05 13:41:05 -05:00
- '**/*.md'
Skip AppVeyor builds when GitHub workflows are modified Don't waste AppVeyor CI resources unnecessarily.
2020-09-27 20:56:19 -04:00
- .github/workflows/
Ignore more Travis CI files on AppVeyor Avoid unnecessary AppVeyor rebuilds when Travis build files are changed.
2020-04-22 09:25:31 -04:00
- build/tools/before_install.sh
Ignore changes to a script not used under AppVeyor This file is only used by GitHub and Travis CI, so don't rebuild AppVeyor needlessly.
2021-04-05 09:41:04 -04:00
- build/tools/httpbin.sh
Skip AppVeyor CI builds on documentation-only changes There is no need to rebuild everything if only the documentation files have changed. Unfortunately there doesn't seem to be any way to do the same thing for Travis CI yet, see https://github.com/travis-ci/travis-ci/issues/6301
2017-11-25 04:46:39 -05:00
Added initial AppVeyor config.
2015-11-04 09:30:27 -05:00
environment:
matrix:
- TOOLSET: msbuild
CONFIGURATION: DLL Release
ARCH: x64
wxUSE_STL: 1
- TOOLSET: nmake
VS: '9.0'
BUILD: release
ARCH: x86
- TOOLSET: nmake
VS: '14.0'
BUILD: debug
ARCH: amd64
wxUSE_STL: 1
Enable wxUSE_WEBVIEW_EDGE in an AppVeyor test
2021-01-18 19:20:02 -05:00
wxUSE_WEBVIEW_EDGE: 1
Added initial AppVeyor config.
2015-11-04 09:30:27 -05:00
- TOOLSET: mingw
- TOOLSET: msys2
MSYSTEM: MINGW32
Add CMake to Appveyor Build with “Visual Studio 12 (2013)” 32-bit Release DLLs Other configurations can later be added in the appveyor.yml
2016-10-05 04:16:30 -04:00
- TOOLSET: cmake
GENERATOR: 'Visual Studio 12'
SHARED: ON
CONFIGURATION: Release
Build WXQT toolkit with AppVeyor
2018-09-25 13:46:21 -04:00
- TOOLSET: cmake_qt
GENERATOR: 'Visual Studio 14 2015 Win64'
SHARED: ON
CONFIGURATION: Release
Added initial AppVeyor config.
2015-11-04 09:30:27 -05:00
clone_depth: 50
Checkout submodules in Appveyor builds Unlike Travis CI, Appveyor doesn't do this automatically, but we will need them soon (the currently existing Catch submodule is not used by Appveyor builds but, arguably, should be too).
2017-11-10 09:23:20 -05:00
install: git submodule update --init
Check if AppVeyor should abort before cloning the repo
2018-09-25 13:57:40 -04:00
init:
- ps: |
if ($env:APPVEYOR_PULL_REQUEST_NUMBER -and $env:APPVEYOR_BUILD_NUMBER -ne ((Invoke-RestMethod `
https://ci.appveyor.com/api/projects/$env:APPVEYOR_ACCOUNT_NAME/$env:APPVEYOR_PROJECT_SLUG/history?recordsNumber=50).builds | `
Where-Object pullRequestId -eq $env:APPVEYOR_PULL_REQUEST_NUMBER)[0].buildNumber) { `
throw "There are newer queued builds for this pull request, failing early." }
Added initial AppVeyor config.
2015-11-04 09:30:27 -05:00
before_build:
- ps: |
Remove the correct directory from PATH for MinGW AppVeyor builds We need to remove the directory containing sh.exe from the PATH as otherwise mingw32-make seems to use it and not cmd.exe for executing the commands in the makefile, but the wrong directory was being removed in appveyor.yml, having no effect. Fix this and undo 5f2ccde269278860d7afbe1ca101a1b69370fbfb which compensated for it by (almost) clearing the PATH entirely which, in turn, broke one of our unit tests (and could break other things in the future, as having an empty PATH is rather unexpected). Also use the full path for head program now that its directory is not in the PATH any more. Alternative could be to use PowerShell, but while powershell -Command "'gcc','mingw32-make','ar'|%%{ iex \"$_ --version\"|select -first 1 }" does work, it looks really ugly, so avoid it for now. See https://github.com/wxWidgets/wxWidgets/pull/142 See #17274.
2017-11-25 09:59:16 -05:00
$env:PATH = $env:PATH -replace "C:\\Program Files\\Git\\usr\\bin",""
Enable wxUSE_WEBVIEW_EDGE in an AppVeyor test
2021-01-18 19:20:02 -05:00
if (-not (Test-Path env:wxUSE_STL)) { $env:wxUSE_STL = '0' }
if (-not (Test-Path env:wxUSE_WEBVIEW_EDGE)) { $env:wxUSE_WEBVIEW_EDGE = '0' }
Correct test for MSYS2/Cygwin in AppVeyor script There is no "compiler" environment variable, use TOOLSET instead.
2021-01-31 18:51:28 -05:00
if (($env:TOOLSET -ne "msys2") -and ($env:TOOLSET -ne "cygwin")) {
Fix replacement in setup.h done in AppVeyor builds We can't write to the file we're reading from, so use a temporary variable.
2021-01-31 17:12:08 -05:00
$txt = gc include\wx\msw\setup.h
Write-Output $txt |
Added initial AppVeyor config.
2015-11-04 09:30:27 -05:00
%{$_ -replace "define wxUSE_STL 0", "define wxUSE_STL $env:wxUSE_STL"} |
Enable wxUSE_WEBVIEW_EDGE in an AppVeyor test
2021-01-18 19:20:02 -05:00
%{$_ -replace "define wxUSE_WEBVIEW_EDGE 0", "define wxUSE_WEBVIEW_EDGE $env:wxUSE_WEBVIEW_EDGE"} |
Added initial AppVeyor config.
2015-11-04 09:30:27 -05:00
sc include\wx\msw\setup.h
}
Run unit tests on AppVeyor too Launch the tests after building them.
2017-11-22 09:37:34 -05:00
build_script: c:\projects\wxwidgets\build\tools\appveyor.bat
Added initial AppVeyor config.
2015-11-04 09:30:27 -05:00
Run httpbin in appveyor.yml to be able to stop it later There is no way to stop a background task simply and safely with cmd.exe, but in appveyor.yml we can use PowerShell, so use its job support to do it instead. This is important because AppVeyor waits until all jobs launched by the script terminate, so without stopping the background job all builds waited for an hour before timing out.
2021-01-26 16:50:43 -05:00
before_test:
- ps: |
Write-Output "Getting and launching httpbin."
Add Python scripts directory to PATH to avoid pip warnings They're really too annoying.
2021-01-27 05:11:20 -05:00
$env:PATH = "C:\Python35;C:\Python35\Scripts;" + $env:PATH
pip.exe --disable-pip-version-check install httpbin
Start-Job -Name wx_httpbin { python.exe -m httpbin.core 2>&1 > c:\projects\wxwidgets\httpbin.log }
Disable the tests if launching httpbin failed for some reason This is not ideal, but will have to do for now.
2021-01-27 04:04:31 -05:00
Start-Sleep -Seconds 5
Fix testing for curl success in PowerShell Of course doing the natural thing doesn't work in PowerShell.
2021-01-27 05:30:18 -05:00
curl.exe -s http://127.0.0.1:5000/ip > $null
if ($lastExitCode -eq "0") {
Disable the tests if launching httpbin failed for some reason This is not ideal, but will have to do for now.
2021-01-27 04:04:31 -05:00
$env:WX_TEST_WEBREQUEST_URL="http://127.0.0.1:5000"
}
else {
Write-Error "Disabling wxWebRequest tests as launching httpbin failed."
$env:WX_TEST_WEBREQUEST_URL="0"
}
Run httpbin in appveyor.yml to be able to stop it later There is no way to stop a background task simply and safely with cmd.exe, but in appveyor.yml we can use PowerShell, so use its job support to do it instead. This is important because AppVeyor waits until all jobs launched by the script terminate, so without stopping the background job all builds waited for an hour before timing out.
2021-01-26 16:50:43 -05:00
Run unit tests on AppVeyor too Launch the tests after building them.
2017-11-22 09:37:34 -05:00
test_script: c:\projects\wxwidgets\build\tools\appveyor-test.bat
Run httpbin in appveyor.yml to be able to stop it later There is no way to stop a background task simply and safely with cmd.exe, but in appveyor.yml we can use PowerShell, so use its job support to do it instead. This is important because AppVeyor waits until all jobs launched by the script terminate, so without stopping the background job all builds waited for an hour before timing out.
2021-01-26 16:50:43 -05:00
after_test:
- ps: |
Stop-Job -Name wx_httpbin
Reference in New Issue Copy Permalink