Asking for Feedback on Mesos Plugin 2.0

[Karsten Jeschkies]

Marathon/Mesosphere engineer here 👋

As you might know Mesosphere has a fork of the Mesos plugin on mesosphere/mesos-plugin. It is used to support Jenkins on DC/OS. Unfortunately the code diverged over time. Furthermore user feature requests and load tests pushed us to rethink the architecture of the plugin. For instances we want to support suppress/revive or be non-blocking to scale up. Thus we decided to rewrite the plugin based on USI, a new second level scheduler for Mesos built with the learning from Marathon. You can find a working prototype in our branch mesosphere/mesos-plugin#usi-jenkins.

We would love to make this new plugin the 2.0 of the Mesos Plugin for Jenkins to avoid confusion among users, give back to the community but also receive feedback. That's why I'm reaching out to you to understand what we should do so that the plugin can be merged back upstream.

Who is the owner of jenkinsci/mesos-plugin? What is your take?

Thanks.

Karsten.

PS: This was posted originally to https://github.com/jenkinsci/mesos-plugin/issues/343.

[Vincent Latombe]

Hi Karsten,

I used to give time to this plugin, but I no longer have interest in it so it would be great for someone else to pick it up. As with most Jenkins plugins, if a 2.0 of the plugin gets released, I would expect a working migration path to avoid headaches for users. As long as we have this, I think it would make perfect sense to leverage your work and make it the 2.0 of the mesos plugin.

Unfortunately, the link you provided (https://github.com/mesosphere/mesos-plugin/tree/usi-jenkins) doesn't seem to be publicly available.

Vincent

--
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-meso...@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/d5cfc164-80a9-4fe7-9fbe-12280eb02c68%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Karsten Jeschkies]

Hi,

thanks for the feedback. We are thinking about a migration path as well. The branch was removed in favor of master: https://github.com/mesosphere/jenkins-mesos-plugin.

How shall we go forward from here? Should we create a pull request for master once we feel it’s time? Could I get a contributor or similar status for the repository?

Best.

Karsten.

[Vincent Latombe]

You can request commit access to the repository by following the process described here: https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin#AdoptaPlugin-Requestcommitaccess. I'll give my +1 to the request.

If we don't have a migration path yet, my suggestion would be to create a 2.0 branch in the main repository. We could release beta versions of the plugin from there (available through experimental update center - https://jenkins.io/doc/developer/publishing/releasing-experimental-updates/).

Once we have a migration path, this can be merged to the master branch.

Vincent

[Vinod Kone]

Karsten, I'm happy to give you commit access to the project. I'll do so shortly. And thanks for stepping up to take the plugin forward.

Regarding versioning, we can either call the USI based one 1.x or 2.x series. We never had a 1.0 of this plugin. We can do a 1.0 release off master after we merge some outstanding PRs with bug fixes and branch off 1.x. Master can then be updated to be USI based one and we can call it 2.x series.

To unsubscribe from this group and stop receiving emails from it, send an email to jenkins-mesos+unsubscribe@googlegroups.com.

[Vinod Kone]

I've released 1.0 of the plugin and branched off 1.x from that commit.

The master branch now has the version as 2.0.0-SNAPSHOT. @karsten, feel free to update this branch to use USI.