[
https://issues.apache.org/jira/browse/MESOS-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727936#comment-13727936
]
Chris Aniszczyk commented on MESOS-608:
---------------------------------------
Good news [~vinodkone], have the repo and have given us both admin access:
https://github.com/jenkinsci/mesos-plugin
I pushed an initial version of the code there (fixed up POM and licensing
headers).
A few things to do:
- which version of Mesos do we want to build against
- we should find a cleaner way of loading the native mesos lib...
- we should find a way to write a simple test to check that the plug-in is
installed: https://wiki.jenkins-ci.org/display/JENKINS/Unit+Test
- we should remove the mesos jenkins plugin from the mesos repo at ASF and
point people to the jenkinsci one
- get the mesos jenkins ci plugin building on BuildHive
Any other thoughts?
> Move Jenkins code out of the mesos repo to Jenkins CI repo
> ----------------------------------------------------------
>
> Key: MESOS-608
> URL: https://issues.apache.org/jira/browse/MESOS-608
> Project: Mesos
> Issue Type: Task
> Reporter: Vinod Kone
> Assignee: Vinod Kone
> Fix For: 0.14.0
>
>
> For better adoption and usage, seems like a good place for this to live is
> under https://github.com/jenkinsci.
--
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
