Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Windows CI using GitHub Actions #61

Closed
traversaro opened this issue Apr 18, 2018 · 6 comments
Closed

Add Windows CI using GitHub Actions #61

traversaro opened this issue Apr 18, 2018 · 6 comments

Comments

@traversaro
Copy link
Member

No description provided.

@traversaro
Copy link
Member Author

It is worth to check if it is possible to install the superbuild in a directory with spaces, so we check for a classical reason for which CMake-based build system can fail: robotology-legacy/codyco-superbuild#101 .

@traversaro
Copy link
Member Author

Old AppVeyor file that was working for codyco-superbuild: https://github.com/robotology/codyco-superbuild/blob/master/appveyor.yml .

@traversaro
Copy link
Member Author

fyi @diegoferigo

@traversaro traversaro changed the title Add Windows CI using AppVeyor Add Windows CI using Azure Jan 11, 2019
@traversaro
Copy link
Member Author

Given that Azure Pipelines has no time limit, for the superbuild it is probably a better choice w.r.t AppVeyor. As soon as we have the green light to enable Azure Pipelines, we can proceed.
It is important to remember to include 32 bit Windows tests to avoid problems such as #136 .

@traversaro
Copy link
Member Author

As soon as we have the green light to enable Azure Pipelines, we can proceed.

We can start using Azure for repos in the robotology organization from the 1st of June.

@traversaro traversaro changed the title Add Windows CI using Azure Add Windows CI using GitHub Actions Nov 5, 2019
@traversaro
Copy link
Member Author

Fixed by #296 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant