[
https://issues.apache.org/jira/browse/FLINK-6510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16006557#comment-16006557
]
Robert Metzger commented on FLINK-6510:
---------------------------------------
Okay, then I would do a staged approach.
First we enable the integration to make sure it at least compiles. Once the
tests on windows are fixed (again), we run the tests as well with the PRs and
pushes.
Do you want to go ahead and open a PR with the .yml file for the master branch?
> Add CI integration for Windows
> ------------------------------
>
> Key: FLINK-6510
> URL: https://issues.apache.org/jira/browse/FLINK-6510
> Project: Flink
> Issue Type: Improvement
> Components: Build System
> Reporter: Chesnay Schepler
> Assignee: Chesnay Schepler
> Fix For: 1.4.0
>
>
> Several times now the compilation on Windows was broken by accident and only
> detected way down the line. We can use AppVeyor to verify that Flink can be
> compiled on Windows.
> It would require us to add a {{appveyor.yml}} in the root directory of the
> repository with the following contents, and we have to ask infra to add the
> AppVeyor integration.
> {code}
> version: 1.0.{build}
> install:
> - ps: >-
> Add-Type -AssemblyName System.IO.Compression.FileSystem
> if (!(Test-Path -Path "C:\maven" )) {
> (new-object System.Net.WebClient).DownloadFile(
>
> 'http://www.us.apache.org/dist/maven/maven-3/3.3.9/binaries/apache-maven-3.3.9-bin.zip',
> 'C:\maven-bin.zip'
> )
>
> [System.IO.Compression.ZipFile]::ExtractToDirectory("C:\maven-bin.zip",
> "C:\maven")
> }
> $env:JAVA_HOME="C:\Program Files\Java\jdk1.7.0"
> $env:PATH="C:\maven\apache-maven-3.3.9\bin" + ";" + $env:JAVA_HOME +
> "\bin" + ";" + $env:PATH
> $env:MAVEN_OPTS="-XX:MaxPermSize=2g"
> $env:JAVA_OPTS="-XX:MaxPermSize=2g"
> cache:
> - C:\maven\
> - C:\Users\appveyor\.m2
> build_script:
> - ps: mvn clean install -B "-DskipTests" "-Dmaven.javadoc.skip=true"
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
