Skip to content

ci: build deb and rpm packages and a Homebrew formula - #3

Merged
colinjlacy merged 1 commit into
runtimeconditions:mainfrom
itvi-1234:release-packages
Nov 18, 2026
Merged

colinjlacy merged 1 commit into
runtimeconditions:mainfrom
itvi-1234:release-packages

Conversation

@itvi-1234

@itvi-1234 itvi-1234 commented Nov 17, 2026 •

Copy link
Copy Markdown
Member

Add system packages for the Java profiler, as the TypeScript profiler has them.

scripts/release-package.py builds, from the jar of a release, the jar, rc-profiler-java_.tar.gz (the launcher and the jar, which the Homebrew formula installs), and SHA256SUMS; and for a stable tag with --system-packages also a deb and an rpm for amd64 and arm64, and the formula. The deb and rpm carry a Java runtime made with jlink from the Temurin JDK 21.0.13 pinned by checksum in distribution/jdk.lock.json, holding only the modules the jar needs (jdeps, plus jdk.compiler), so they need nothing else installed. The launcher finds the jar and that runtime through ../lib/rc-profiler-java. The formula depends on openjdk@21 and sets JAVA_HOME to it unless the user has set one.

The release workflow builds these for a stable tag, installs the packages in clean Ubuntu, Debian and Rocky Linux containers, and publishes SHA256SUMS in place of checksums.txt, because the Homebrew and package repositories look for that name. A prerelease still gets the jar and the archive. After a stable release it dispatches rc-profiler-java-release-published to homebrew-tools and packages, as the TypeScript profiler does; that needs the package-distribution environment and a HOMEBREW_REPO_DISPATCH_TOKEN secret, and skips with a notice without one.

test.yml gets a packages job that builds and installs the packages on every pull request, so a change to the packaging is checked before a release. The helpers have 19 unit tests.

…eleases

Add system packages for the Java profiler, as the TypeScript profiler has them.

scripts/release-package.py builds, from the jar of a release, the jar, rc-profiler-java_<v>.tar.gz (the launcher and
the jar, which the Homebrew formula installs), and SHA256SUMS; and for a stable tag with --system-packages also a deb
and an rpm for amd64 and arm64, and the formula. The deb and rpm carry a Java runtime made with jlink from the
Temurin JDK 21.0.13 pinned by checksum in distribution/jdk.lock.json, holding only the modules the jar needs
(jdeps, plus jdk.compiler), so they need nothing else installed. The launcher finds the jar and that runtime through
../lib/rc-profiler-java. The formula depends on openjdk@21 and sets JAVA_HOME to it unless the user has set one.

The release workflow builds these for a stable tag, installs the packages in clean Ubuntu, Debian and Rocky Linux
containers, and publishes SHA256SUMS in place of checksums.txt, because the Homebrew and package repositories look for
that name. A prerelease still gets the jar and the archive. After a stable release it dispatches
rc-profiler-java-release-published to homebrew-tools and packages, as the TypeScript profiler does; that needs the
package-distribution environment and a HOMEBREW_REPO_DISPATCH_TOKEN secret, and skips with a notice without one.

test.yml gets a packages job that builds and installs the packages on every pull request, so a change to the
packaging is checked before a release. The helpers have 19 unit tests.

Not verified locally: building the real packages downloads and runs the pinned JDK's jlink and jdeps, which this
change's author could not do, so the first real run of the packages job is the check.
@colinjlacy
colinjlacy merged commit 6250281 into runtimeconditions:main Nov 18, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants