Windows distribution via scoop

[jonesbusy]

What feature do you want to see added?

The CLI is distributed by Homebrew which support Linux (and Windows users with WSL2) and MacOSX.

It would be great to not let Windows user left behind and allow to distribute the CLI via a windows package manager.

I woulds suggest scoop because it's very similar to Homebrew (a Tap is a Bucket, a Formala is an app manifest)

It also work with JRelease : https://jreleaser.org/guide/latest/reference/packagers/scoop.html

Good first issue if anyone is interested by packaging

Upstream changes

No response

Are you interested in contributing this feature?

No response

[CodexRaunak]

Hey @jonesbusy I am interested in working on this one

[jonesbusy]

Sure feel free to open a PR

[gounthar]

What about Chocolatey?
It is also supported by JReleaser.
https://jreleaser.org/guide/latest/reference/packagers/chocolatey.html

That's what I use with my Windows machine.

[jonesbusy]

The point with Chocolatey is packages need to be packaged and pushed to https://push.chocolatey.org/ (A bit like maven central). So it means managing an API key

With scoop it's downloaded through anywhere (a bit like Homebrew) so we can reuse the uber jar already

What we miss is "just" creating the app manifest and updating the jrelease configuration

I think scoop is much simplier for now

[gounthar]

This issue was discussed during the Infra Weekly Meeting.
https://www.youtube.com/watch?v=TjFgyWU4vTw
https://community.jenkins.io/t/infrastructure-team-meeting-january-07-2025/25515/1

In Jenkins, we currently utilize package managers such as Chocolatey and Homebrew, alongside the default Windows package manager.

If we decide to incorporate Scoop, we, as a community, must commit to keeping it updated and functioning properly. I am concerned that our infra team may not have the necessary bandwidth to manage this additional responsibility effectively. Should we successfully maintain Scoop, it could then be feasible to consider migrating the official Jenkins clients to a Scoop registry.

[jonesbusy]

Yes but here we are not talking about Jenkins for end user but a tool for plugin maintainer. I think it's a bit different.

Using scoop for one tool doesn't mean we should also use scoop to distribute Jenkins right ?

For HomeBrew, Jenkins is not managed by the infra-team since it's packaged by a 3rd party (See https://www.jenkins.io/download/lts/macos/) right ? It's the same for scoop https://bjansen.github.io/scoop-apps/main/jenkins/. A 3rd party decided to package it and make it available (with a very outdated version by the way)

I will check the recording when published because I'm not sure to understand. In therm of maintenance it's fully automated by JReleaser : https://github.com/jenkins-infra/plugin-modernizer-tool/pull/515/files We are not even supposed to commit on the scoop git repository since it's done during the release process