Procedure for submitting new repositories to github/jenkinsci?

[Jorge Castro]

Hello Jenkins community!

The Ubuntu Cloud team has been maintaining a service deployment script (called a charm) for Jenkins for a few years now:

- https://jujucharms.com/jenkins/

It uses the official Jenkins packages and let's users model a multi-node Jenkins deployment for a variety of clouds. Last year I added it as a deployment option on the Ubuntu page for Jenkins, and I recently updated it with the latest information. We now consider the charm to be production ready, has tests, and is used in production for all of our Jenkins needs at Ubuntu and Canonical. 

We're interested in putting this closer to Jenkins users (like the puppet and chef modules) so that people who are interested in cloud deployments of Jenkins can benefit from the work we've put into it, and of course contribute if they're so inclined. We're committed to maintaining this code in github.com/jenkinsci. Since our charm isn't a plugin per se I just wanted to post on the list for some feedback on how to proceed. 

Thanks! 

[R. Tyler Croy]

(replies inline)

On Tue, 24 Nov 2015, Jorge Castro wrote:

> Hello Jenkins community!
>
> The Ubuntu Cloud team has been maintaining a service deployment script
> (called a charm) for Jenkins for a few years now:
>
> - https://jujucharms.com/jenkins/

I suggest following this procedure:
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Requesthosting
and just mentally redact the word "plugin" from the instructions :)

> It uses the official Jenkins packages and let's users model a multi-node
> Jenkins deployment for a variety of clouds. Last year I added it as a
> deployment option on the Ubuntu page for Jenkins, and I recently updated it
> with the latest information. We now consider the charm to be production
> ready, has tests, and is used in production for all of our Jenkins needs at
> Ubuntu and Canonical.
>
> We're interested in putting this closer to Jenkins users (like the puppet
> and chef modules) so that people who are interested in cloud deployments of
> Jenkins can benefit from the work we've put into it, and of course
> contribute if they're so inclined. We're committed to maintaining this code
> in github.com/jenkinsci. Since our charm isn't a plugin per se I just
> wanted to post on the list for some feedback on how to proceed.
>
> Thanks!
>

> --
> 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 jenkinsci-de...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/2a968b60-b096-4bda-8c59-d4a6c693c42d%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.


- R. Tyler Croy

------------------------------------------------------
Code: <https://github.com/rtyler>
Chatter: <https://twitter.com/agentdero>

% gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
------------------------------------------------------

[domi]

there is also the repos for all kind of scripts: https://github.com/jenkinsci/jenkins-scripts

/Domi

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/20151124195636.GJ23766%40blackberry.coupleofllamas.com.