You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "James E. King, III (JIRA)" <ji...@apache.org> on 2017/03/10 11:21:04 UTC
[jira] [Resolved] (THRIFT-4081) Provide a MinGW 64-bit Appveyor CI
build for better pull request validation
[ https://issues.apache.org/jira/browse/THRIFT-4081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James E. King, III resolved THRIFT-4081.
----------------------------------------
Resolution: Fixed
Fix Version/s: 0.11.0
We now build msvc2015 and mingw64 as separate appveyor jobs in the same build request. This will prevent mingw64 builds from rotting.
> Provide a MinGW 64-bit Appveyor CI build for better pull request validation
> ---------------------------------------------------------------------------
>
> Key: THRIFT-4081
> URL: https://issues.apache.org/jira/browse/THRIFT-4081
> Project: Thrift
> Issue Type: Improvement
> Components: Build Process
> Affects Versions: 0.10.0
> Environment: Appveyor
> Reporter: James E. King, III
> Assignee: James E. King, III
> Fix For: 0.11.0
>
>
> We currently build in Visual Studio 2015 on Appveyor. We do not use the Windows CI environment to verify that MinGW still builds successfully (there is a 32-bit job on linux, #16, which runs on every pull request). I would recommend that we add a CI build job to Appveyor and/or extend the existing job to build with the latest MinGW 64-bit environment which includes gcc-6.3.0; we could perhaps remove Travis job #16 which is using 32-bit mingw on linux as a result?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)