Well one of the features I want to write for the literate project type in Jenkins is a smarter Maven awareness...
Thus you can declare upstream literate projects and branch matching criteria... an upstream project's local repository cache will then be exposed to downstream projects... but on a branch for branch basis based on the branch matching rules... The UX I am aiming for is that you start working on a feature branch, find you need a change in an upstream library, create a matching feature branch in the upstream library's SCM and now... presto-chango your build stays working as they both have the same local repository cache (with layers on so that downstream does not pollute upstream)... of course since both projects are literate project type, you've also got your own auto-created project in each for your feature branch (which you can have configured to stay retained or be removed X days after the branch is closed) Of course I am searching for a better name than "literate" as while the primary build descriptor format is a literate build in a README file... it also works for other documented build definitions (e.g. there is a .travis.yml parser - if not fully functional - in the code base from day 0) On 18 June 2014 05:18, Mark Derricutt <[email protected]> wrote: > You assume CI servers have intelligence and deep knowledge of Maven. Or > that you have deep control over their configuration. > > You can't do that with Travis CI, nor with Code-review tools such as > Gerrit ( not cleanly, not without doing evil things with maven configs like > I mention in [1] ). > > Starting from a complete clean local repo is also kinda horrible as a > small commit will now take 10 minutes or so to download deps just so a > 15second build could fail. That feels WRONG. > > "Living without SNAPSHOTs" should include the CI server, otherwise you're > just (IMHO) lying to yourself about not using SNAPSHOTs. > > [1] http://www.theoryinpractice.net/post/76092272646/intra- > repository-review-builds-with-gerrit-and-apache > > > On 18 Jun 2014, at 15:05, Barrie Treloar wrote: > > Your CI should know that project B depends upon A. >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
