Hi all,
As you probably know, there is ongoing work on automating Jenkins Core
releases within the Jenkins infrastructure. Apart from Linux and Windows
distributions, there is also a OS X installer which is being produced for
each Weekly and LTS release in the current release environment (download
link
<https://jenkins.io/download/thank-you-downloading-osx-installer-stable/>).
There are also a homebrew formula <https://formulae.brew.sh/formula/jenkins>
being maintained by the HomeBrew community, these packages are even listed
in our installation guide <https://jenkins.io/doc/book/installing/#macos>.
In the new environment we use MS Azure, and there is no good way to produce
OS X builds there, because they require MacOS. We could use an external
service for that, but it would add additional point of failure and
implementation/maintenance overhead. Since the HomeBrew is a defacto
standard in MacOS, I do not think it worth the effort. What f we just stop
shipping them?
Implementation plan:
- Deprecate in the next weekly releases
- It requires a changelog entry in one of the next weekly releases +
LTS upgrade guideline entry + likely a deprecation blogpost
- Use HomeBrew as a recommended source of MacOS installers, mark it as a
3rd-party installer like we do for other downloads
-
- Remove MacOS native packaging from Jenkins release Pipelines once we
fully switch to automated releases
WDYT?
Best regards,
Oleg
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLC_G-MGPH_GOiZkjba%2BcA4SbUpxpLFVj%3D0vC81Y48%2BufQ%40mail.gmail.com.
