Hudson on github

[Jason Dillon]

Why does http://github.com/kohsuke/hudson not include the full svn src tree?  Specifically, the plugins seem to be missing.  It would be helpful if your svn mirror included the entire src tree so that folks could use git more easily to submit patches back for plugins.

--jason
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[R. Tyler Croy]

On Sat, 12 Jun 2010, Jason Dillon wrote:

> Why does http://github.com/kohsuke/hudson not include the full svn src tree?  Specifically, the plugins seem to be missing.  It would be helpful if your svn mirror included the entire src tree so that folks could use git more easily to submit patches back for plugins.

The primary problem with mirroring the entire source tree is that it's just so
enormous, and there's no real benefit (IMHO).

Secondly, there is a means for plugins to exist in the GitHub ecosystem, but
it's not through Kohsuke's git-svn mirror. See: http://github.com/hudson

Submitting patches through Git is likely going to have to be left to the plugin
maintainers themselves if they elect to allow that and/or do the foot-work.
Providing a "toll-free bridge" for patches in and out of Subversion from Git
for the entire code base would be a nightmare (I've done this with a tree 3x
larger than Hudson's, it sucks).

Cheers,
-R. Tyler Ballance
--------------------------------------
  Jabber: [hidden email]
  GitHub: http://github.com/rtyler
Identica: http://identi.ca/dero
 Twitter: http://twitter.com/agentdero
    Blog: http://unethicalblogger.com

[Jason Dillon]

On Jun 13, 2010, at 11:31 PM, R. Tyler Ballance wrote:
> On Sat, 12 Jun 2010, Jason Dillon wrote:
>
>> Why does http://github.com/kohsuke/hudson not include the full svn src tree?  Specifically, the plugins seem to be missing.  It would be helpful if your svn mirror included the entire src tree so that folks could use git more easily to submit patches back for plugins.
>
> The primary problem with mirroring the entire source tree is that it's just so
> enormous, and there's no real benefit (IMHO).

The benefit is that others don't have to go setup their own clone mirrors.  Which is what I did.  I do agree though that the source tree is large, but IMO its not enormous.  It could probably benefit from being split up a little.


> Secondly, there is a means for plugins to exist in the GitHub ecosystem, but
> it's not through Kohsuke's git-svn mirror. See: http://github.com/hudson

I don't see how this is related to my question.


> Submitting patches through Git is likely going to have to be left to the plugin
> maintainers themselves if they elect to allow that and/or do the foot-work.
> Providing a "toll-free bridge" for patches in and out of Subversion from Git
> for the entire code base would be a nightmare (I've done this with a tree 3x
> larger than Hudson's, it sucks).

Git is a tool that can easily generate normal patches which can be attached to JIRA and then applied to svn... so I don't really understand what you are talking about here.  I'm certainly not suggesting that any automated merges from anyone via git should be enabled... yikes that would be horrible.

--jason


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]