Proposal: Deprecating/Removing OS X packaging for Jenkins

[Oleg Nenashev]

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). There are also a homebrew formula being maintained by the HomeBrew community, these packages are even listed in our installation guide.

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

[Mark Waite]

This sounds like the right plan to me.  +1

--
You received this message because you are subscribed to the Google Groups "Jenkins Platform SIG" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkins-platform...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkins-platform-sig/CAPfivLC_G-MGPH_GOiZkjba%2BcA4SbUpxpLFVj%3D0vC81Y48%2BufQ%40mail.gmail.com.

--

Thanks!

Mark Waite

[Gavin Mogan]

Are there any download stats? If its barely used (and i suspect thats true), then +1

Otherwise, I'm sure one of the cloud mac providers would be up for donating a tiny bit of infra to build the package in exchange for advertising to jenkins users.

Gavin

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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFZt%3DOq3NCSD%2BwQGeKH6QkBBGaVBHZCwbFxvDTV751P_A%40mail.gmail.com.

[Daniel Beck]

On Tue, Nov 19, 2019 at 5:02 PM Oleg Nenashev <o.v.ne...@gmail.com> wrote:

There are also a homebrew formula being maintained by the HomeBrew community, these packages are even listed in our installation guide.

I'm confused that this advertises building and running Jenkins from master sources, which probably should never be done in any sort of prod environment. OTOH, it's no worse than OpenBSD offering a package of Jenkins 2.122…

A potential blocker for "real" use on Mac OS X could be that it seems to limit the listening interface to localhost, i.e. it doesn't allow access from other systems.

That said, other than "nothing" I have no better alternative. But I'm not sure that advertising the Homebrew package makes much sense either.

FWIW it could be possible to rather easily detect a Jenkins instance installed via the Mac package. If so, perhaps an admin monitor could be added to core to show a notice?

[Oleg Nenashev]

FWIW it could be possible to rather easily detect a Jenkins instance installed via the Mac package. If so, perhaps an admin monitor could be added to core to show a notice?

 We could check the filesystem to detect control files, but it does not look to be that reliable. Better than nothing, but not sure the effort would be justified until we have some usage stats or recent download stats.

 I'm confused that this advertises building and running Jenkins from master sources, which probably should never be done in any sort of prod environment. OTOH, it's no worse than OpenBSD offering a package of Jenkins 2.122…

Link?

--

You received this message because you are subscribed to the Google Groups "Jenkins Platform SIG" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkins-platform...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkins-platform-sig/CAMo7Pt%2B4Dan_%2Bap%2BdwSCcB7K8QpNrvfp49ooR_O6bZLZ2DwSBg%40mail.gmail.com.

[Daniel Beck]

On Tue, Nov 19, 2019 at 7:57 PM Oleg Nenashev <o.v.ne...@gmail.com> wrote:

 I'm confused that this advertises building and running Jenkins from master sources, which probably should never be done in any sort of prod environment. OTOH, it's no worse than OpenBSD offering a package of Jenkins 2.122…

Link?

Yours. "Stable" (a term we generally use for LTS, but could be a Homebrew convention) is the weekly release, "HEAD" is building from source:

https://github.com/Homebrew/homebrew-core/blob/0c5930b3e5dd9bc366924a2d7a99acc6b55d77d9/Formula/jenkins.rb#L7-L10

https://github.com/Homebrew/homebrew-core/blob/0c5930b3e5dd9bc366924a2d7a99acc6b55d77d9/Formula/jenkins.rb#L17-L18

But if the analytics are correct, one in 10k seems to choose this, so perhaps not that big of a deal…

[R. Tyler Croy]

(replies inline)

On Tue, 19 Nov 2019, Oleg Nenashev wrote:

> 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 ([1]download link). There are also a
> [2]homebrew formula being maintained by the HomeBrew community, these packages
> are even listed in our [3]installation guide.



I'm strongly in favor of removing the macOS packaging. From a time management
and benefit standpoint, I don't think its worth any time to support it.


--
GitHub: https://github.com/rtyler

GPG Key ID: 0F2298A980EE31ACCA0A7825E5C92681BEF6CEA2