[CI] Adding MSVC build to CI check with Appveyor

NicolasDorier commented at 12:48 pm on March 6, 2018: contributor

Credit to @sipsorcery for his hard work on making bitcoin compile in Visual Studio.

On top of this, he managed to integrate Visual Studio to integration server AppVeyor. (Travis does not support Windows for now as far as I know)

You can see it in action here: https://ci.appveyor.com/project/sipsorcery/bitcoin this is done on top of this PR.

He shared the following config file for the CI:

 0version: 1.0.{build}
 1branches:
 2  only:
 3  - master
 4skip_tags: true
 5image: Visual Studio 2017
 6configuration: Release
 7platform: x64
 8environment:
 9  EMAIL: aaron@sipsorcery.com
10  APPVEYOR_SAVE_CACHE_ON_ERROR: true
11  DUMMY1: dummy
12cache: C:\Tools\vcpkg\installed
13before_build:
14- ps: >-
15    dir c:\tools\vcpkg
16
17    dir c:\tools\vcpkg\installed
18
19
20    vcpkg install boost:x64-windows-static
21
22    vcpkg install libevent:x64-windows-static
23
24    vcpkg install openssl:x64-windows-static
25
26    vcpkg install zeromq:x64-windows-static
27
28    vcpkg install berkeleydb:x64-windows-static
29
30    vcpkg install secp256k1:x64-windows-static
31
32    vcpkg install leveldb:x64-windows-static
33
34
35    git pull origin pull/11526/head
36     Invoke-WebRequest -Uri https://gist.githubusercontent.com/sipsorcery/0ce4b529ebd3bda784ad71c5702cae88/raw/6732cef26554fd016a154ed852f5dbac8fbf4199/bitcoin-config.h -OutFile src\config\bitcoin-config.h
37build:
38  project: build_msvc\bitcoin.sln
39  parallel: true
40  verbosity: minimal
41artifacts:
42- path: build_msvc\x64\Release\*.exe
43  name: Executables

Note that the download of bitcoin-config.h will likely go away and be part of the build.

fanquake added the label Windows on Mar 6, 2018

MarcoFalke added the label Tests on Mar 6, 2018

sipsorcery commented at 3:53 am on March 7, 2018: member

Now slightly simplified with @NicolasDorier changes to VS project files.

 0version: 1.0.{build}
 1branches:
 2  only:
 3  - master
 4skip_tags: true
 5image: Visual Studio 2017
 6configuration: Release
 7platform: x64
 8environment:
 9  EMAIL: aaron@sipsorcery.com
10  APPVEYOR_SAVE_CACHE_ON_ERROR: true
11  DUMMY1: dummy
12cache: C:\Tools\vcpkg\installed
13before_build:
14- cmd: >-
15    dir c:\tools\vcpkg
16
17    dir c:\tools\vcpkg\installed
18
19
20    vcpkg install boost:x64-windows-static
21
22    vcpkg install libevent:x64-windows-static
23
24    vcpkg install openssl:x64-windows-static
25
26    vcpkg install zeromq:x64-windows-static
27
28    vcpkg install berkeleydb:x64-windows-static
29
30    vcpkg install secp256k1:x64-windows-static
31
32    vcpkg install leveldb:x64-windows-static
33
34
35    git pull origin pull/11526/head
36build:
37  project: build_msvc\bitcoin.sln
38  parallel: true
39  verbosity: minimal
40artifacts:
41- path: build_msvc\x64\Release\*.exe
42  name: Executables

MarcoFalke commented at 4:44 pm on March 13, 2018: member

It seems they are not running any tests at all

NicolasDorier commented at 8:43 am on March 14, 2018: contributor

No, this would be done in a second step (as I saw you worked to make things runnable on windows)

Having it only compiling is already giving us good feedback on constructs which might break on windows though.

NicolasDorier closed this on Aug 14, 2018

ken2812221 referenced this in commit e393a18b51 on Aug 15, 2018

linuxsh2 referenced this in commit b70411b627 on Jul 29, 2021

DrahtBot locked this on Sep 8, 2021

[CI] Adding MSVC build to CI check with Appveyor #12613