Proposal: Deprecating/Removing OS X packaging for Jenkins

classic Classic list List threaded Threaded
16 messages Options
Reply | Threaded
Open this post in threaded view
|

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



--
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 [hidden email].
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.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Deprecating/Removing OS X packaging for Jenkins

Mark Waite-2
This sounds like the right plan to me.  +1

On Tue, Nov 19, 2019 at 9:02 AM Oleg Nenashev <[hidden email]> 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). 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



--
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 [hidden email].
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

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFZt%3DOq3NCSD%2BwQGeKH6QkBBGaVBHZCwbFxvDTV751P_A%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Deprecating/Removing OS X packaging for Jenkins

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


On Tue, Nov 19, 2019 at 9:26 AM Mark Waite <[hidden email]> wrote:
This sounds like the right plan to me.  +1

On Tue, Nov 19, 2019 at 9:02 AM Oleg Nenashev <[hidden email]> 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). 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



--
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 [hidden email].
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

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

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DutpNoXBNV%3Dio0J345CsvzuPmTUdB5JpuHUngJni5BAFCw%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Deprecating/Removing OS X packaging for Jenkins

Oliver Gondža-2
In reply to this post by Mark Waite-2
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 <[hidden email]
> <mailto:[hidden email]>> 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 [hidden email]
>     <mailto:[hidden email]>.
>     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 [hidden email]
> <mailto:[hidden email]>.
> 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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/a0a0059a-aa99-efb5-a8f4-71e2891a0332%40gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Deprecating/Removing OS X packaging for Jenkins

Daniel Beck-2
In reply to this post by Oleg Nenashev


On Tue, Nov 19, 2019 at 5:02 PM Oleg Nenashev <[hidden email]> 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?

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7Pt%2B4Dan_%2Bap%2BdwSCcB7K8QpNrvfp49ooR_O6bZLZ2DwSBg%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Deprecating/Removing OS X packaging for Jenkins

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?




On Tue, Nov 19, 2019 at 7:44 PM Daniel Beck <[hidden email]> wrote:


On Tue, Nov 19, 2019 at 5:02 PM Oleg Nenashev <[hidden email]> 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?

--
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 [hidden email].
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.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLBiFBG6qhb85s3ZPBSfcVweVZte%3DgeShur%2BhWX8gbmAPQ%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Deprecating/Removing OS X packaging for Jenkins

Daniel Beck-2


On Tue, Nov 19, 2019 at 7:57 PM Oleg Nenashev <[hidden email]> 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:

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

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtLoGCsdfKewdfNCGUupRHwk1hmZLMD9N66Lbkg3Mf8MKQ%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Deprecating/Removing OS X packaging for Jenkins

R. Tyler Croy-2
In reply to this post by Oleg Nenashev
(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

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/20191119215435.fprugebmzkhs5jqa%40grape.

signature.asc (858 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Deprecating/Removing OS X packaging for Jenkins

Oleg Nenashev
Added the topic to the tomorrow's governance meeting just to have more discussion and to sign it off
https://wiki.jenkins.io/display/JENKINS/Governance+Meeting+Agenda#GovernanceMeetingAgenda-November20

On Tuesday, November 19, 2019 at 10:54:51 PM UTC+1, R. Tyler Croy wrote:
(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:  <a href="https://github.com/rtyler" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Frtyler\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFtsnCUZ085B8982iTQ2KFqz5gYhw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Frtyler\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFtsnCUZ085B8982iTQ2KFqz5gYhw&#39;;return true;">https://github.com/rtyler

GPG Key ID: 0F2298A980EE31ACCA0A7825E5C92681BEF6CEA2

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/0dce4867-9d03-4ae0-8a74-7bf65c360c40%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Deprecating/Removing OS X packaging for Jenkins

Rick
Remove MacOS package, plus from me. A native package is a pretty heavy way.

On Wed, Nov 20, 2019 at 6:42 AM Oleg Nenashev <[hidden email]> wrote:
Added the topic to the tomorrow's governance meeting just to have more discussion and to sign it off
https://wiki.jenkins.io/display/JENKINS/Governance+Meeting+Agenda#GovernanceMeetingAgenda-November20

On Tuesday, November 19, 2019 at 10:54:51 PM UTC+1, R. Tyler Croy wrote:
(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

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/0dce4867-9d03-4ae0-8a74-7bf65c360c40%40googlegroups.com.


--

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTGUTbkjeSGZPt9N-d3LP1V42RyVwF%2BD-TovrJ%2Bt_FSSLw%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Deprecating/Removing OS X packaging for Jenkins

YanJun Shi
+1 from me. I think almost all used MacOS people is very simple uses the 'Generic Java package'. It's much more convenient than Mac OS package

On Wed, Nov 20, 2019 at 8:39 AM Rick <[hidden email]> wrote:
Remove MacOS package, plus from me. A native package is a pretty heavy way.

On Wed, Nov 20, 2019 at 6:42 AM Oleg Nenashev <[hidden email]> wrote:
Added the topic to the tomorrow's governance meeting just to have more discussion and to sign it off
https://wiki.jenkins.io/display/JENKINS/Governance+Meeting+Agenda#GovernanceMeetingAgenda-November20

On Tuesday, November 19, 2019 at 10:54:51 PM UTC+1, R. Tyler Croy wrote:
(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

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/0dce4867-9d03-4ae0-8a74-7bf65c360c40%40googlegroups.com.


--

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTGUTbkjeSGZPt9N-d3LP1V42RyVwF%2BD-TovrJ%2Bt_FSSLw%40mail.gmail.com.


--
Shi Yanjun(yJunS)

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CALfBRDpj1gbsYNXHUb_NU8iEYF08vGTBg9tBr%2BmoBwyY083EoQ%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Deprecating/Removing OS X packaging for Jenkins

Richard Bywater-3
In reply to this post by Daniel Beck-2
> 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.

Not sure where it says that? Homebrew *can* build and run from master sources if the `--HEAD` option is specified but otherwise the default just downloads the "latest" version (as specified in the formula) of `jenkins.war` from the Jenkins mirrors.

Also, as far as I can tell, the default for Homebrew runs of Jenkins is to listen on all interfaces.

So basically +1 for removing package and just sticking with Homebrew for the majority of OSX users.

Richard.

On Wed, 20 Nov 2019 at 07:44, Daniel Beck <[hidden email]> wrote:


On Tue, Nov 19, 2019 at 5:02 PM Oleg Nenashev <[hidden email]> 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?

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7Pt%2B4Dan_%2Bap%2BdwSCcB7K8QpNrvfp49ooR_O6bZLZ2DwSBg%40mail.gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hwcb_XB6tYaFD3a-eR-NHwUqD3x96gb32V36knqjnLLwFw%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Deprecating/Removing OS X packaging for Jenkins

Olblak-2
I am happy to see that we all agree on this. \o/

---
gpg --keyserver keys.gnupg.net --recv-key 52210D3D
---


On Wed, Nov 20, 2019, at 3:09 AM, Richard Bywater 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.

Not sure where it says that? Homebrew *can* build and run from master sources if the `--HEAD` option is specified but otherwise the default just downloads the "latest" version (as specified in the formula) of `jenkins.war` from the Jenkins mirrors.

Also, as far as I can tell, the default for Homebrew runs of Jenkins is to listen on all interfaces.

So basically +1 for removing package and just sticking with Homebrew for the majority of OSX users.

Richard.

On Wed, 20 Nov 2019 at 07:44, Daniel Beck <[hidden email]> wrote:


On Tue, Nov 19, 2019 at 5:02 PM Oleg Nenashev <[hidden email]> 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?


--
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 [hidden email].


--
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 [hidden email].

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/466537c1-284f-40b1-8372-b28e55417812%40www.fastmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Deprecating/Removing OS X packaging for Jenkins

Oleg Nenashev
Package deprecation was approved at the Governance meeting. I will go ahead and submit a PR with changes

On Wednesday, November 20, 2019 at 9:09:13 AM UTC+1, Olblak wrote:
I am happy to see that we all agree on this. \o/

---
gpg --keyserver <a href="http://keys.gnupg.net" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fkeys.gnupg.net\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGGvem0n8cSWWfyOfhzR-uVSpk4NQ&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fkeys.gnupg.net\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGGvem0n8cSWWfyOfhzR-uVSpk4NQ&#39;;return true;">keys.gnupg.net --recv-key 52210D3D
---


On Wed, Nov 20, 2019, at 3:09 AM, Richard Bywater 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.

Not sure where it says that? Homebrew *can* build and run from master sources if the `--HEAD` option is specified but otherwise the default just downloads the "latest" version (as specified in the formula) of `jenkins.war` from the Jenkins mirrors.

Also, as far as I can tell, the default for Homebrew runs of Jenkins is to listen on all interfaces.

So basically +1 for removing package and just sticking with Homebrew for the majority of OSX users.

Richard.

On Wed, 20 Nov 2019 at 07:44, Daniel Beck <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="GC3QucEFBQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">db...@...> wrote:


On Tue, Nov 19, 2019 at 5:02 PM Oleg Nenashev <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="GC3QucEFBQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">o.v.n...@...> wrote:
There are also a <a href="https://formulae.brew.sh/formula/jenkins" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fformulae.brew.sh%2Fformula%2Fjenkins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNED2ZZ8AgYqGbFk6KXk8cN8pK9qkQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fformulae.brew.sh%2Fformula%2Fjenkins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNED2ZZ8AgYqGbFk6KXk8cN8pK9qkQ&#39;;return true;">homebrew formula being maintained by the HomeBrew community, these packages are even listed in our <a href="https://jenkins.io/doc/book/installing/#macos" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fdoc%2Fbook%2Finstalling%2F%23macos\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHydAnjJuWtRx1fQBfeWRbGjdb9lQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fdoc%2Fbook%2Finstalling%2F%23macos\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHydAnjJuWtRx1fQBfeWRbGjdb9lQ&#39;;return true;">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?


--
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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="GC3QucEFBQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkin...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7Pt%2B4Dan_%2Bap%2BdwSCcB7K8QpNrvfp49ooR_O6bZLZ2DwSBg%40mail.gmail.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7Pt%2B4Dan_%2Bap%2BdwSCcB7K8QpNrvfp49ooR_O6bZLZ2DwSBg%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7Pt%2B4Dan_%2Bap%2BdwSCcB7K8QpNrvfp49ooR_O6bZLZ2DwSBg%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7Pt%2B4Dan_%2Bap%2BdwSCcB7K8QpNrvfp49ooR_O6bZLZ2DwSBg%40mail.gmail.com.


--
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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="GC3QucEFBQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkin...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hwcb_XB6tYaFD3a-eR-NHwUqD3x96gb32V36knqjnLLwFw%40mail.gmail.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hwcb_XB6tYaFD3a-eR-NHwUqD3x96gb32V36knqjnLLwFw%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hwcb_XB6tYaFD3a-eR-NHwUqD3x96gb32V36knqjnLLwFw%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hwcb_XB6tYaFD3a-eR-NHwUqD3x96gb32V36knqjnLLwFw%40mail.gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/44aba368-b265-406a-a0d6-2dd0b25262a1%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Deprecating/Removing OS X packaging for Jenkins

Oleg Nenashev
Hi all,

Documentation updates are ready for review:

Thanks a lot to everyone for feedback and reviews.

On Wednesday, November 20, 2019 at 9:50:06 PM UTC+1, Oleg Nenashev wrote:
Package deprecation was approved at the Governance meeting. I will go ahead and submit a PR with changes

On Wednesday, November 20, 2019 at 9:09:13 AM UTC+1, Olblak wrote:
I am happy to see that we all agree on this. \o/

---
gpg --keyserver <a href="http://keys.gnupg.net" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fkeys.gnupg.net\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGGvem0n8cSWWfyOfhzR-uVSpk4NQ&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fkeys.gnupg.net\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGGvem0n8cSWWfyOfhzR-uVSpk4NQ&#39;;return true;">keys.gnupg.net --recv-key 52210D3D
---


On Wed, Nov 20, 2019, at 3:09 AM, Richard Bywater 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.

Not sure where it says that? Homebrew *can* build and run from master sources if the `--HEAD` option is specified but otherwise the default just downloads the "latest" version (as specified in the formula) of `jenkins.war` from the Jenkins mirrors.

Also, as far as I can tell, the default for Homebrew runs of Jenkins is to listen on all interfaces.

So basically +1 for removing package and just sticking with Homebrew for the majority of OSX users.

Richard.

On Wed, 20 Nov 2019 at 07:44, Daniel Beck <[hidden email]> wrote:


On Tue, Nov 19, 2019 at 5:02 PM Oleg Nenashev <[hidden email]> wrote:
There are also a <a href="https://formulae.brew.sh/formula/jenkins" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fformulae.brew.sh%2Fformula%2Fjenkins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNED2ZZ8AgYqGbFk6KXk8cN8pK9qkQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fformulae.brew.sh%2Fformula%2Fjenkins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNED2ZZ8AgYqGbFk6KXk8cN8pK9qkQ&#39;;return true;">homebrew formula being maintained by the HomeBrew community, these packages are even listed in our <a href="https://jenkins.io/doc/book/installing/#macos" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fdoc%2Fbook%2Finstalling%2F%23macos\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHydAnjJuWtRx1fQBfeWRbGjdb9lQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fdoc%2Fbook%2Finstalling%2F%23macos\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHydAnjJuWtRx1fQBfeWRbGjdb9lQ&#39;;return true;">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?


--
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 [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7Pt%2B4Dan_%2Bap%2BdwSCcB7K8QpNrvfp49ooR_O6bZLZ2DwSBg%40mail.gmail.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7Pt%2B4Dan_%2Bap%2BdwSCcB7K8QpNrvfp49ooR_O6bZLZ2DwSBg%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7Pt%2B4Dan_%2Bap%2BdwSCcB7K8QpNrvfp49ooR_O6bZLZ2DwSBg%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7Pt%2B4Dan_%2Bap%2BdwSCcB7K8QpNrvfp49ooR_O6bZLZ2DwSBg%40mail.gmail.com.


--
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 [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hwcb_XB6tYaFD3a-eR-NHwUqD3x96gb32V36knqjnLLwFw%40mail.gmail.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hwcb_XB6tYaFD3a-eR-NHwUqD3x96gb32V36knqjnLLwFw%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hwcb_XB6tYaFD3a-eR-NHwUqD3x96gb32V36knqjnLLwFw%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hwcb_XB6tYaFD3a-eR-NHwUqD3x96gb32V36knqjnLLwFw%40mail.gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/761f1575-2235-400e-ba2c-f00db759f763%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Deprecating/Removing OS X packaging for Jenkins

Oleg Nenashev
Thanks to everybody who helped with reviews!
The blogpost is now live. macOS packaging is now officially deprecated in 2,206+ and 2.204.1+

Best regards,
Oleg


On Thursday, November 21, 2019 at 1:13:21 AM UTC+1, Oleg Nenashev wrote:
Hi all,

Documentation updates are ready for review:
  • Documentation patch: <a href="https://github.com/jenkins-infra/jenkins.io/pull/2666" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fjenkins.io%2Fpull%2F2666\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFEqfnPFM1aDCsk2lW24CHxEUx42A&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fjenkins.io%2Fpull%2F2666\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFEqfnPFM1aDCsk2lW24CHxEUx42A&#39;;return true;">https://github.com/jenkins-infra/jenkins.io/pull/2666
  • Deprecation announcement blogpost: <a href="https://github.com/jenkins-infra/jenkins.io/pull/2667" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fjenkins.io%2Fpull%2F2667\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHALTkJ9OMWldd4RoS_UQvUqh4L6A&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fjenkins.io%2Fpull%2F2667\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHALTkJ9OMWldd4RoS_UQvUqh4L6A&#39;;return true;">https://github.com/jenkins-infra/jenkins.io/pull/2667

Thanks a lot to everyone for feedback and reviews.

On Wednesday, November 20, 2019 at 9:50:06 PM UTC+1, Oleg Nenashev wrote:
Package deprecation was approved at the Governance meeting. I will go ahead and submit a PR with changes

On Wednesday, November 20, 2019 at 9:09:13 AM UTC+1, Olblak wrote:
I am happy to see that we all agree on this. \o/

---
gpg --keyserver <a href="http://keys.gnupg.net" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fkeys.gnupg.net\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGGvem0n8cSWWfyOfhzR-uVSpk4NQ&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fkeys.gnupg.net\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGGvem0n8cSWWfyOfhzR-uVSpk4NQ&#39;;return true;">keys.gnupg.net --recv-key 52210D3D
---


On Wed, Nov 20, 2019, at 3:09 AM, Richard Bywater 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.

Not sure where it says that? Homebrew *can* build and run from master sources if the `--HEAD` option is specified but otherwise the default just downloads the "latest" version (as specified in the formula) of `jenkins.war` from the Jenkins mirrors.

Also, as far as I can tell, the default for Homebrew runs of Jenkins is to listen on all interfaces.

So basically +1 for removing package and just sticking with Homebrew for the majority of OSX users.

Richard.

On Wed, 20 Nov 2019 at 07:44, Daniel Beck <[hidden email]> wrote:


On Tue, Nov 19, 2019 at 5:02 PM Oleg Nenashev <[hidden email]> wrote:
There are also a <a href="https://formulae.brew.sh/formula/jenkins" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fformulae.brew.sh%2Fformula%2Fjenkins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNED2ZZ8AgYqGbFk6KXk8cN8pK9qkQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fformulae.brew.sh%2Fformula%2Fjenkins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNED2ZZ8AgYqGbFk6KXk8cN8pK9qkQ&#39;;return true;">homebrew formula being maintained by the HomeBrew community, these packages are even listed in our <a href="https://jenkins.io/doc/book/installing/#macos" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fdoc%2Fbook%2Finstalling%2F%23macos\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHydAnjJuWtRx1fQBfeWRbGjdb9lQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fdoc%2Fbook%2Finstalling%2F%23macos\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHydAnjJuWtRx1fQBfeWRbGjdb9lQ&#39;;return true;">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?


--
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 [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7Pt%2B4Dan_%2Bap%2BdwSCcB7K8QpNrvfp49ooR_O6bZLZ2DwSBg%40mail.gmail.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7Pt%2B4Dan_%2Bap%2BdwSCcB7K8QpNrvfp49ooR_O6bZLZ2DwSBg%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7Pt%2B4Dan_%2Bap%2BdwSCcB7K8QpNrvfp49ooR_O6bZLZ2DwSBg%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7Pt%2B4Dan_%2Bap%2BdwSCcB7K8QpNrvfp49ooR_O6bZLZ2DwSBg%40mail.gmail.com.


--
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 [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hwcb_XB6tYaFD3a-eR-NHwUqD3x96gb32V36knqjnLLwFw%40mail.gmail.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hwcb_XB6tYaFD3a-eR-NHwUqD3x96gb32V36knqjnLLwFw%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hwcb_XB6tYaFD3a-eR-NHwUqD3x96gb32V36knqjnLLwFw%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hwcb_XB6tYaFD3a-eR-NHwUqD3x96gb32V36knqjnLLwFw%40mail.gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/47e053ca-c442-4c6b-b979-0eba0735e292%40googlegroups.com.