On 02/07/2012 22:37, Sami Tikka wrote:
Your choices are (in no particular order):
A) Use git submodules
B) Use git subtrees
>> More importantly, would changes pushed to any of the submodules
cause that repo to issue a request-to-build to the Jenkins server?
>> (which is ultimately what I'm after here: I want to make sure that
changes pushed to the repos of both xlrd and xlwt cause the xlutils
(which depends on both packages) jobs to kick off)
>
> Yes, it would. You would configure Jenkins with the address of the
parent repo. Any change in the submodule repos does not take effect
until the parent repo has been updated to refer to the new version of
the submodule repo.
Doesn't feel like the correct solution here, and won't build the job
when commits are made to the child repositories... (we disagree about
this, requiring commits to a "container" repo is not the right thing
here...)
D) Implement the "right" thing
Well, I can't, I don't have the knowledge or experience, but would the
maintainers of the git plugin do this if I raised a bug for it?
I wish I could understand what the current multi-repository support in
the plugin is supposed to do... Where can I find out?
E) Use something else than Jenkins
Well, nothing else comes even close in my opinion ;-)
C) Use repo
About C: repo is the tool Android project uses to manage multiple git
repositories (http://source.android.com/source/version-control.html). There is
a Jenkins plugin for that:
https://wiki.jenkins-ci.org/display/JENKINS/Repo+Plugin
Thanks, I'll take a look :-)
cheers,
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk
