Skip to content

Comments

Set up CI with Azure Pipelines#903

Merged
SamCarlberg merged 1 commit intoWPIRoboticsProjects:masterfrom
SamCarlberg:azure-pipelines
Jan 14, 2019
Merged

Set up CI with Azure Pipelines#903
SamCarlberg merged 1 commit intoWPIRoboticsProjects:masterfrom
SamCarlberg:azure-pipelines

Conversation

@SamCarlberg
Copy link
Member

@SamCarlberg SamCarlberg commented Jan 13, 2019

The pipeline is configured to use Linux, 32- and 64-bit Windows, and macOS.
Code generation tests will run on mac and both Windows platforms, but not Linux
Native installer packages are generated and published as build artifacts

Preview at https://dev.azure.com/SamCarlberg/GRIP/_build

Upgrade Gradle to 4.10.2 to allow use of the -Dorg.gradle.java.home property on the Linux

Note: conflicts with #900 due to some changes to the build script


An Azure pipeline for this project will be created after this PR is merged. This will replace the Travis and Appveyor integrations

Rename native installers to an understandable format
Upgrade Gradle to 4.10.2
}
mainClassName = jfx.mainClass

tasks.withType(de.dynamicfiles.projects.gradle.plugins.javafx.tasks.JfxNativeTask) {
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This isn't great, but it works and I don't want to put too much effort into it since it'll need to be rewritten for the Gradle 5 upgrade

@SamCarlberg SamCarlberg merged commit f3b70d8 into WPIRoboticsProjects:master Jan 14, 2019
@JLLeitschuh
Copy link
Member

@SamCarlberg How do you want to handle releases which used to be completely executed through and uploaded by Travis CI?

@SamCarlberg
Copy link
Member Author

Using Azure releases

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants