Note that the Jenkinsfile is not operational - #85
Merged
Conversation
The Jenkins server it ran on was decommissioned in August 2026. It performed a build-and-archive step nothing downstream consumed; publishing has always run through GitHub Actions. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
1 participant
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.
The Jenkins server this
Jenkinsfileran on was decommissioned in August 2026, so it no longer executes.It performed a build-and-archive step - install, build, pack, archive the tarball on the Jenkins box - that nothing downstream consumed. Publishing has always run through the GitHub Actions workflows in
.github/workflows, which were never affected.Keeping the file, adding a README note so nobody reads it as the current build process.
🤖 Generated with Claude Code