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

ARROW-8089: [C++] Port the toolchain build from Appveyor to Github Actions #6592

Closed
wants to merge 17 commits into from

Conversation

kszucs
Copy link
Member

@kszucs kszucs commented Mar 12, 2020

No description provided.

@github-actions
Copy link

@pitrou
Copy link
Member

pitrou commented Mar 12, 2020

See conda-forge/gtest-feedstock#43

@kszucs
Copy link
Member Author

kszucs commented Mar 12, 2020

@pitrou I ended up porting the appveyor toolchain build to GHA.

@pitrou
Copy link
Member

pitrou commented Mar 12, 2020

What does that change? It's a problem in the conda-forge package AFAIU

@pitrou
Copy link
Member

pitrou commented Mar 12, 2020

Also, AppVeyor is less of a problem now, there are only 3 jobs remaining, and they're fast (and benefit from caching).

@kszucs kszucs changed the title ARROW-6941: [C++] Unpin gtest in build environment ARROW-8089: [C++] Port the toolchain build from Appveyor to Github Actions Mar 12, 2020
@github-actions
Copy link

@kszucs kszucs force-pushed the ARROW-6941 branch 2 times, most recently from 95418d9 to f86fa0f Compare March 13, 2020 12:19
@wesm
Copy link
Member

wesm commented Mar 19, 2020

Needs rebase. It seems like this would improve maintainability of CI scripts

@kszucs
Copy link
Member Author

kszucs commented Apr 13, 2020

I almost have a working windows container locally, so we may be able use the docker based workflow for windows as well.

@wesm
Copy link
Member

wesm commented Jun 24, 2020

@kszucs do you intend to keep working on this? I'll close the PR until it can be rehabilitated

@wesm wesm closed this Jun 24, 2020
@kszucs
Copy link
Member Author

kszucs commented Jun 24, 2020

This PR was outdated, I will keep working on the windows docker containers instead.

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

Successfully merging this pull request may close these issues.

None yet

3 participants