Upstream Mesosphere Changes

43 views
Skip to first unread message

bw...@mesosphere.io

unread,
Apr 16, 2018, 12:45:13 PM4/16/18
to Jenkins Mesos Plugin
Hey Folks,

We (Mesosphere) have identified a number of issues with the Jenkins plugin that we've corrected by merging in behavior from our scheduler SDK (https://github.com/mesosphere/dcos-commons). 

These issues are fairly severe at scale, and we'd like to get them merged into the upstream asap. Here's an open PR: https://github.com/jenkinsci/mesos-plugin/pull/315. We've tested these changes in our own internal Jenkins environments as well as in a customer's cluster where they were seeing issues at scale.

It would be great to get some eyeballs on this and move it forward :).

- Ben

Vinod Kone

unread,
Apr 16, 2018, 5:02:23 PM4/16/18
to bw...@mesosphere.io, Manivannan, Vincent Latombe, Jenkins Mesos Plugin
@Mani, @Vincent

Would either of you have cycles to review and merge this? The PR seems to have critical improvements and fixes. I do not have enough context about the latest state of the codebase to be able to review myself unfortunately.

Thanks,
Vinod


-- Vinod

--
You received this message because you are subscribed to the Google Groups "Jenkins Mesos Plugin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkins-mesos+unsubscribe@googlegroups.com.
To post to this group, send email to jenkin...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkins-mesos/c5a9ea8c-5bd1-412e-b4da-919bdde1fbe9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Manivannan

unread,
Apr 16, 2018, 5:23:46 PM4/16/18
to Vinod Kone, bw...@mesosphere.io, Vincent Latombe, Jenkins Mesos Plugin
Sure Vinod. I'll review it. 
Reply all
Reply to author
Forward
0 new messages