> Question: When Lucene no longer has the Solr test suite to help catch bugs, > how long time would it take from a Lucene commit, before Solr/ES Jenkins > instances would have had time to produce a build and run tests? Would it be > possible to setup a trigger in Solr Jenkins?
It depends how the code is organized after Lucene becomes a subcomponent. If it's a regular dependency (on a *-SNAPSHOT version) then the trigger would have to be dual (any commit on Solr or any commit on Lucene). If the code is organized around a git submodule with Lucene then bumping a version on a submodule would effectively trigger a CI build. This "bumping" can be automated on certain branches (such as master) so effectively it'd be immediately ready for testing... It's not really that relevant to this discussion but if you're curious what this looks like I created an example submodule setup reflecting current master here, try it: git clone [email protected]:dweiss/lucene-solr.git -b split/solr cd lucene-solr/ you'll see the 'lucene/ folder is empty. It is a submodule. When you issue: git submodule status you'll see which git revision that submodule is on: -e5092db7915ac49d0ade0591e7b52176657c380c lucene You can get the sub repositories in their respective versions by doing: git submodule init git submodule update When you cd into lucene now you'll see it is a separate repository (that things can be committed to, branches switched, etc.). git status HEAD detached at e5092db791 nothing to commit, working tree clean Submodules in git have an extra advantage over snapshot dependencies: they always point at a given revision of a submodule *exactly* so each and every commit in the parent repository has exact versions of each submodule recorded in git history. Of course not everything is rosy - working with submodule-organized repositories does have a darker side too (new git workflows to be learned, switching incompatible branches can be tricky, etc.). D. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
