[
https://issues.apache.org/jira/browse/MESOS-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13779070#comment-13779070
]
Benjamin Hindman commented on MESOS-704:
----------------------------------------
Thanks [~jfarrell]! I'm not sure the best path forward for building on the
Jenkins build slaves. A couple of options that I see:
(1) Package libsasl2 with Mesos (as we do for some other 3rdparty libraries).
(2) Conditionally compile code depending on whether or not we have libsasl2.
(3) Get libsasl2 onto the Jenkins slaves (either via help from Apache
infrastructure/builds guys or via doing our own install?).
I'm not excited about (1) because we're explicitly trying to get away from
packaging 3rdparty libs. The unfortunate thing about (2) is that we won't be
testing important code. And I'm not whether (3) is even feasible!
Suggestions? Other options? Thanks so much!
> Add authentication support using SASL and CRAM-MD5
> --------------------------------------------------
>
> Key: MESOS-704
> URL: https://issues.apache.org/jira/browse/MESOS-704
> Project: Mesos
> Issue Type: Sub-task
> Reporter: Vinod Kone
> Assignee: Vinod Kone
> Fix For: 0.15.0
>
>
> This adds support to both scheduler and masters.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
