Files
allwpilib/DevelopmentBuilds.md
Gold856 97d0b15f7d Add README files for some subprojects and update various other docs (#8640)
Adds a section on design philosophy so we have something to point to
when people suggest features that aren't compatible with the way WPILib
is designed. Fixes some missed reorg changes (although the native-utils
link intentionally points to main as to be up-to-date in the future) and
generally cleans up any outdated information. Also includes wording
about supporting FTC. Per discussion in Slack, the LabVIEW wording has
been removed, and anything to do with LabVIEW is going to have to be
NI's job. And pursuant to #2757 and #5331, additional (light) developer
documentation has been added to some subprojects, mostly being a quick
summary of the what the project does and what it's for (or not for).

---------

Co-authored-by: sciencewhiz <sciencewhiz@users.noreply.github.com>
Co-authored-by: Joseph Eng <91924258+KangarooKoala@users.noreply.github.com>
2026-04-26 16:39:26 -07:00

2.9 KiB

Installing Development Builds

This article contains instructions on building projects using a development build and a local WPILib build.

Note: This only applies to Java/C++ teams.

Warning

There are no stability or compatibility guarantees for builds outside of tagged releases. Changes may not be fully documented. Use them at your own risk!

Development builds may be non-functional between the end of the season and the start of beta testing. Development builds are also likely to be incompatible with vendor libraries during this time.

Development Build

Development builds are the per-commit build hosted every time a commit is pushed to the allwpilib repository. These builds are then hosted on artifactory.

To build a project using a development build, find the build.gradle file and open it. Then, add the following code below the plugin section and replace YEAR with the year of the development version. It is also necessary to use a 2027 GradleRIO version, ie 2027.0.0-alpha-5

wpi.maven.useLocal = false
wpi.maven.useDevelopment = true
wpi.versions.wpilibVersion = 'YEAR.+'

The top of your build.gradle file should now look similar to the code below. Ignore any differences in versions.

Java

plugins {
  id "java"
  id "org.wpilib.GradleRIO" version "2027.0.0-alpha-5"
}

wpi.maven.useLocal = false
wpi.maven.useDevelopment = true
wpi.versions.wpilibVersion = '2027.+'

C++

plugins {
  id "cpp"
  id "google-test-test-suite"
  id "org.wpilib.GradleRIO" version "2027.0.0-alpha-5"
}

wpi.maven.useLocal = false
wpi.maven.useDevelopment = true
wpi.versions.wpilibVersion = '2027.+'

Development Build Documentation

Local Build

Building with a local build is very similar to building with a development build. Ensure you have built and published WPILib by following the instructions attached here. Next, find the build.gradle file in your robot project and open it. Then, add the following code below the plugin section and replace YEAR with the year of the local version.

Java

plugins {
  id "java"
  id "org.wpilib.GradleRIO" version "2027.0.0-alpha-5"
}

wpi.maven.useLocal = false
wpi.maven.useWpilibMavenLocalDevelopment = true
wpi.versions.wpilibVersion = 'YEAR.424242.+'

C++

plugins {
  id "cpp"
  id "google-test-test-suite"
  id "org.wpilib.GradleRIO" version "2027.0.0-alpha-5"
}

wpi.maven.useLocal = false
wpi.maven.useWpilibMavenLocalDevelopment = true
wpi.versions.wpilibVersion = 'YEAR.424242.+'

Systemcore Development

See the developerRobot subproject.