Not being a Mac OS user myself, I cannot argue how useful this is for its user-base. But provided most of the the Mac users can or do use homebrew, I say go for it!

On 19/11/2019 18.26, Mark Waite wrote:
This sounds like the right plan to me.  +1

On Tue, Nov 19, 2019 at 9:02 AM Oleg Nenashev <[email protected] <mailto:[email protected]>> wrote:

    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
          o 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 Platform SIG" group.
    To unsubscribe from this group and stop receiving emails from it,
    send an email to [email protected]
    <mailto:[email protected]>.
    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
    
<https://groups.google.com/d/msgid/jenkins-platform-sig/CAPfivLC_G-MGPH_GOiZkjba%2BcA4SbUpxpLFVj%3D0vC81Y48%2BufQ%40mail.gmail.com?utm_medium=email&utm_source=footer>.



--
Thanks!
Mark Waite

--
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] <mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFZt%3DOq3NCSD%2BwQGeKH6QkBBGaVBHZCwbFxvDTV751P_A%40mail.gmail.com <https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFZt%3DOq3NCSD%2BwQGeKH6QkBBGaVBHZCwbFxvDTV751P_A%40mail.gmail.com?utm_medium=email&utm_source=footer>.


--
oliver

--
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/a0a0059a-aa99-efb5-a8f4-71e2891a0332%40gmail.com.

Reply via email to