On 18 June 2014 13:48, 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. >
It takes a small (but not negligible) amount of time to haul the release jars from you local Maven Repository - likely also hosted on your CI server. Plus pulling in any snapshots previously deployed. I'm not familiar enough your tools, or workflow. If your CI server can't work out that two projects share a dependency relationship are in the build queue then you are left with manual workarounds. Sharing a local maven cache (~/.m2/repo) feels wrong for two independent projects. And if they are dependent they should be built together in the same reactor project. You can manually wait for build-success to be received from the build server before you checkin Project B. As for review, if they are independent why do they need to be reviewed together? Perhaps rethinking the workflow is an option?
