Set up build and deployment for CLI binaries

[odrotbohm]

The CLI artifact needs to be distributed as binary for all operating systems. We need:

• A GitHub Actions workflow that triggers the native image build for the different OSes
• A jReleaser setup to package the binaries up for the different package managers (Homebrew etc.)

Ideally, we tie this workflow to a release branch (release/release) so that pushes to it trigger the distribution.

[aalmiray]

Hi there! Happy to help with the setup. There are several options, please tick any that apply and/or suggest others

• snapshot releases on every push to main branch
• stable releases on push/tag to release branch or on workflow dispatch (other gh events are also possible)
• build native images for all GH supported platforms: linux intel/arm, macos intel/arm, windows intel
• publish to local homebrew tap
• deploy artifacts to Maven Central
• create release notes base on commit messages
• announce releases to Bluesky (other options available)

Ideally the setup will be done using the jreleaser-maven-plugin to keep all concerns aligned, avoid metadata duplication, avoid installing the JReleaser CLI.

[aalmiray]

Would you merge the feature/183-cli branch first or should all work in this regard be done against that branch?

[odrotbohm]

I can take care of the general release procedure (items 1, 2, 5) as I have that set that up for other projects. Do you think we could constrain the jReleaser application to only the CLI artifact?

I'd love to get the PR against the feature branch. Might even be able to add the standard release procedure (release (Java) artifacts published to Central via a branch) this evening. Main challenge really is the build and distribution of the CLI binaries.

[odrotbohm]

The commits for the standard release procedure are in on main. A local mvn release:prepare can be run to produce a tag and a release/release branch pointed to it. That will trigger a build and deploy of the JAR artifacts into Maven Central. Next, the most interesting items to me would be 3 and 4.

[aalmiray]

Will have a look at it next week as I’m currently on the road for the next few days 😅

[maxandersen]

Is the jar for the cli available somewhere ? GitHub Release or maven artifact ? Both enables instant ability to run and install with jbang - something jreleaser can setup too.

[maxandersen]

found the 183 feature branch and can confirm that:

jbang app install --name=jmolecules org.jmolecules.integrations:jmolecules-cli:0.29.0-SNAPSHOT 

just works and give you a jmolecules cli.

I'll suggest you make something similar to what is at unit with jbang junit@junit-team being available. see https://github.com/junit-team/jbang-catalog

If you make a xmolecules/jbang-catalog I'm happy to open PR for it.

Can also start with adding jbang-catalog.json to the repo but then it would be jbang jmolecules@xmolecules/jmolecules-integrations which is bit of a mouthful.

[odrotbohm]

Thanks for trying, Max! I'll give this a spin once I'm back from PTO next week! 🙇‍♂️