Repository navigation
Migrate CI to GitHub Actions and release via GitHub releases - #694
Merged
Merged
Conversation
Replace azure-pipelines.yml with .github/workflows/build.yml: - Build, test, Spotless, Checkstyle and JaCoCo on Java 25 (windows-latest) - Publish JUnit results with the Windows variant of the test-result action (the default variant is a Linux-only Docker action, which broke #681) - Upload JaCoCo and Javadoc as artifacts - On pushes to main, publish to the existing XBot Azure Artifacts Maven feed using the AZURE_ARTIFACTS_TOKEN secret, with yyyyMMdd.HHmmss versions so new builds sort after the existing yyyyMMdd.N ones Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
JUnit results 72 files 72 suites 5s ⏱️ Results for commit 66d98f6. ♻️ This comment has been updated with latest results. |
The generated settings.xml uses ${env.GITHUB_TOKEN}, which the
maven-settings plugin treats as an encrypted password and fails
project configuration.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
overwrite-settings: false still creates the file when none exists. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Each push to main now creates a GitHub release tagged with the version (yyyyMMdd.HHmmss) with the jar, sources, javadoc and POM attached. Robot projects resolve the jar directly from the release URL via an Ivy pattern repository (see README), with no credentials needed. Drops Azure feed publishing, the AZURE_ARTIFACTS_TOKEN secret, and the net.linguica.maven-settings plugin (only used for Azure credentials, and the cause of the setup-java settings.xml failure). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Author
|
Follow-up PRs that point robot projects at the new GitHub releases (safe to merge before this one; they keep the Azure feed for the currently pinned versions):
After this PR merges and the first release exists, each project can bump |
NormalDuck
enabled auto-merge (squash)
November 7, 2026 22:42
aschokking
approved these changes
Nov 7, 2026
aschokking
left a comment
Contributor
There was a problem hiding this comment.
looks reasonable, and we can always revert if something goes wrong
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why are we doing this?
To get off Azure DevOps: CI moves to GitHub Actions, and published builds move from the XBot Azure Artifacts Maven feed to GitHub releases. Robot projects can then reference the library from GitHub with no tokens or Maven feed.
This supersedes draft #681. That PR's build step passed, but the job failed because
EnricoMi/publish-unit-test-result-action@v2is a Linux-only Docker action running on a Windows runner. #681 also predates Java 25 / GradleRIO 2027.Whats changing?
azure-pipelines.yml; added.github/workflows/build.yml. It runs on PRs tomain, pushes tomain, and manual dispatch.windows-latest, same as the Azure job./gradlew buildcovers compile, Spotless, Checkstyle, tests, and JaCoCogradle/actions/setup-gradlereplaces the AzureCache@2step. Onlymainwrites the cache.mainonly): each merge creates a GitHub release.yyyyMMdd.HHmmss(UTC), so they sort after the old Azure versions (yyyyMMdd.N).SeriouslyCommonLib-<ver>.jar,-sources.jar,-javadoc.jar, and.pom.build.gradle:net.linguica.maven-settingsplugin. It only supplied Azure credentials, and it also broke CI: it treats the${env.GITHUB_TOKEN}placeholder in setup-java's generatedsettings.xmlas an encrypted password.publishToMavenLocalstill works.Robot projects
Replace the Azure feed
maven { ... }block with:ivy { name = 'SeriouslyCommonLibReleases' url = 'https://github.com/Team488/SeriouslyCommonLib/releases/download/' patternLayout { artifact '[revision]/[module]-[revision](-[classifier]).[ext]' } metadataSources { artifact() } content { includeGroup 'xbot.common' } }The
xbot.common:SeriouslyCommonLib:<version>coordinates and theincludeBuild('../SeriouslyCommonLib')composite-build setup are unchanged.Notes:
+doesn't work against release URLs. TeamXbot2026, FRCRobotTemplate, and XbotEdu already pin.artifact jar, notcomponents.java), so nothing is lost by resolving the bare jar.Questions/notes for reviewers
GITHUB_TOKENwithcontents: write.main, so the first real release happens on merge.How this was tested
🤖 Generated with Claude Code