Add CI builds on Windows using Visual Studio 2017 #1691
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add complete configuration files for AppVeyor and Azure Pipelines.
Closed
kevinkreiser
approved these changes
Jan 21, 2019
There was a problem hiding this comment.
I'll see about enabling CI this week, amazing work @mloskot!
|
I've re-enabled builds on Azure Pipelines for my fork, it's all as green as the AppVeyor's |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add complete configuration files for AppVeyor and Azure Pipelines.
Tasklist
.appveyor.yml.azure-pipelines.ymlvalhalla/valhalla, notmloskot/valhalla, of course)Requirements / Relations
Build Dependencies
Both configurations provided in this PR install minimum dependencies required to build the library.
Both install dependencies using https://github.com/Microsoft/vcpkg
The AppVeyor is a bit faster because it uses caches
C:\Tools\vcpkgwith upgradedvcpkgand the installed dependencies, so subsequent builds just restore it from the cache, instead of rebuilding.The AppVeyor cache is invalidated if
CMakeLists.txtor.appveyor.ymlchanges.Build Status
The configuration has been verified on both, AppVeyor and Azure Pipelines, using my fork https://github.com/mloskot/valhalla
UPDATE 2019-10-04: I have updated my private AzP setup
No idea why the Azure Pipelines badge says "never built" while the two builds succeeded there.It updates fine for two AP-enabled repos I maintain, https://github.com/mloskot/ci-test and https://github.com/boostorg/gil, so it must be some temporary issue. It's minor, we will sort it out as we go :)
Setting up CI services
@kevinkreiser If you approve this PR and commit as it is without setting the services, nothing will happen. That is, the
.ymlfiles can live in the repo anyway.To setup the services to do the builds, it takes being a member of https://github.com/valhalla/valhalla/ developers, then:
For AppVeyor, it takes https://www.appveyor.com/docs/ and also https://www.appveyor.com/docs/team-setup/
For Azure, it needs the free tier from https://dev.azure.com
If you will need help with setting up the services, let me know.