[
https://issues.apache.org/jira/browse/ARROW-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16570246#comment-16570246
]
Max Risuhin commented on ARROW-2991:
------------------------------------
The idea was to cover all supported generators to make sure that new changes
don't break build process, for example, by adding some new external projects.
On time of adding new Appveyor build jobs, if I recall correctly, there were
some issues, like build with NMake generator worked fine, but Visual Studio
2015 64 generator build failed.
If such Appveyor build regressions never happened, probably, there is no a lot
worries about that.
> [CI] Cut down number of AppVeyor jobs
> -------------------------------------
>
> Key: ARROW-2991
> URL: https://issues.apache.org/jira/browse/ARROW-2991
> Project: Apache Arrow
> Issue Type: Task
> Components: C++, Continuous Integration
> Affects Versions: 0.10.0
> Reporter: Antoine Pitrou
> Priority: Major
> Labels: windows
>
> AppVeyor builds all jobs serially so it's important not to have too many of
> them to avoid builds taking too much time and queuing up.
> I suggest to remove the following jobs:
> - the Release build with Ninja and VS2015; we already have both a Release
> build with Ninja and VS2017, and a Debug build with Ninja and VS2015
> - the two NMake builds: we already exercise the Ninja (cross-platform,
> fastest) and Visual Studio (standard under Windows) build chains
> [~Max Risuhin] you added some of those jobs, do you have any concerns?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
