When developing a plug-in you only need access to the source code
repository, i.e. if you want to use git then you need a github account,
if you want to use subversion, then you need a java.net account.
> * Github: how to create a blank plugin repo, Is it best to start with
> your own repo and let hudson fork or ?
> * How to get jira, wiki page, hudson on hudson etc. setup
For Jira and Confluence you need to have a java.net account. Then write
to the dev list that you would like to have a Jira component and a CI job.
> * What needs to be in the pom file in order to release a plugin.
You should derive from the plugin parent pom and you should reference
the license and author of your plug-in. Maybe we should publish an
example pom in the wiki where everybody can start with. Isn't such a pom
part of the maven hpi archetype? Here is an example from one of my plug-ins:
> * What is the requirements for being included in the update center ?
Just one public release of your plug-in.
> * Can I host the code anywhere, and just release to java.net ? if so
This is discouraged since other developers may like to improve your
plug-in or add patches which is easier if the same repository is used.
> I was considering starting collecting the answers on a wiki page (in
> my personal space as a draft), but I don't know if that is the
> preferred way?
Collecting that information in the wiki is very good:-) Please move your
page to the Hudson space and create a corresponding link in the
developers section so everyone will see it.
> Best regards
So far we haven't had this issue before --- we've been politely asking
people to bring their source code to our community, and everyone was OK
with it. We never had a closed source plugin available in our update
center thus far. The JIRA plugin and the sonar plugin lives with us, so
is the Artifactory plugin.
The co-location of the plugin really served us well, in that it ensures
continuity. A lot of time, the original people who wrote the plugin
moves on, and it's taken over by other people. It's a lot harder to
happen if the plugins are scattered around. It also helps us reduce the
risk of having similar but different plugins.
So given that history, I'd say our current requirement is that you do
host the source code with us. But if there's a good case to be made
against that, we'd love to hear.
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Good catch. It is actually open-source (the last time I checked it was
in SourceForge), but you are right that it's not co-located with us.
I should write to them to see what they say.
For unfortunate historical reasons, Wiki uses its own user database and
JIRA is linked to java.net
> Best regards
The format of the plugin is fairly well-established, so fracturing
caused by it is of little concern. The bigger problem is the eventual
divergence of the API, and it's hard to predict if/how that happens.
One approach that works is to restrict yourself to Hudson <= 1.395,
which would work with both versions so long as the backward
compatibility is maintained.