Re: Best strategy for using lots of modules/projects with some private and some OSS

Some time before November is the plan... But certainly before the end of November if there is any slippage. The demo I saw this week looked almost done On Friday 25 September 2015, Ben Podgursky wrote: > Scanning a github org to generate builds would be pretty slick.

Re: Best strategy for using lots of modules/projects with some private and some OSS

Scanning a github org to generate builds would be pretty slick. Definitely interested in taking a look at that when it's released. On Fri, Sep 25, 2015 at 5:20 AM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > Aha! This is where >

Re: Best strategy for using lots of modules/projects with some private and some OSS

Hello Ben, 2015-09-23 0:28 GMT+02:00 Ben Podgursky : > +1 for aggressive SNAPSHOT use > > Our setup. YMMV: > > ... > - All developers have all code checked out in intellij, source linked > - If you push changes to a library, you update all downstream usages. No >

Re: Best strategy for using lots of modules/projects with some private and some OSS

On Fri, Sep 25, 2015 at 10:53 AM, Bernd wrote: > Hello Ben, > > 2015-09-23 0:28 GMT+02:00 Ben Podgursky : > > > +1 for aggressive SNAPSHOT use > > > > Our setup. YMMV: > > > > ... > > > > > - All developers have all code checked out in intellij,

Re: Best strategy for using lots of modules/projects with some private and some OSS

Aha! This is where https://github.com/jenkinsci/workflow-plugin/tree/master/multibranch and/or https://github.com/jenkinsci/literate-plugin/tree/master come into play... and shortly too there will be the multi-repo job type (which (wearing cloudbees hat) we are in the process of open sourcing

Re: Best strategy for using lots of modules/projects with some private and some OSS

Pretty impressive. I think another issue I hadn't thought of is the overhead of having a CI server/project for each project. If anything, you have to enumerate each project so you can see inside of it and what's happening. Having one macro one means you can see everything in one place but of

Re: Best strategy for using lots of modules/projects with some private and some OSS

Shouldn't require any additional CI servers -- we have one master with hundreds of builds. Depending on build frequency, you likely want a couple slaves -- we have 7 but easily get by with 4. Setting up all the builds is some work but Jenkins will help you a lot. We have a template project

Re: Best strategy for using lots of modules/projects with some private and some OSS

I turned off the block. Ron On 22/09/2015 3:40 PM, Kevin Burton wrote: Weird. Looks like the blog.artifact-software.com isn’t responding to DNS . At least on our network.. On Tue, Sep 22, 2015 at 11:29 AM, Ron Wheeler < rwhee...@artifact-software.com> wrote: You have clearly given this a lot

Re: Best strategy for using lots of modules/projects with some private and some OSS

Hi Kevin, My projects opt for independent versioning of modules to facilitate "release early, release often." To do this for large sets of components like yours requires a Bill of Materials -- i.e., common parent POM with dependencyManagement section. FWIW, the docs we have about our projects

Re: Best strategy for using lots of modules/projects with some private and some OSS

Thanks for pointing that out. I am getting lots of e-mail but perhaps not all. I have some SPAM sites blocked at the firewall for all ports and I may have shut out some innocent people. I was pretty crude in my targeting. Whole /24 nets got blocked. What is the IP that your browser would be

Re: Best strategy for using lots of modules/projects with some private and some OSS

You have clearly given this a lot of thought and your project is just a bit less than twice as large as ours so I am not sure about giving advice. http://blog.artifact-software.com/tech/?p=84 is an article that I wrote a few years ago dealing with our approach to the same problem. Our

Re: Best strategy for using lots of modules/projects with some private and some OSS

Weird. Looks like the blog.artifact-software.com isn’t responding to DNS . At least on our network.. On Tue, Sep 22, 2015 at 11:29 AM, Ron Wheeler < rwhee...@artifact-software.com> wrote: > You have clearly given this a lot of thought and your project is just a > bit less than twice as large as

Re: Best strategy for using lots of modules/projects with some private and some OSS

+1 (probably better and more complete than my description) Has anyone else looked at using an installer like izPack for assembling test setups? It integrates with Maven and will pick up all the right versions of jars and configuration files and build an installer that will drop the whole set

Re: Best strategy for using lots of modules/projects with some private and some OSS

+1 for aggressive SNAPSHOT use Our setup. YMMV: - We have ~75 independent projects and each of them is versioned and deployed independently. Few million lines of code. - We have CI jenkins builds + unit test suites for every project, and we deploy SNAPSHOT artifacts as soon as a build

Re: Best strategy for using lots of modules/projects with some private and some OSS

I have some ruby scripts that we use to detect all the modules with changes (i.e. the seed set of modules that need a release) and computes the release dependency tree for all the pom.xml files. Then it will start with the first module with changes and release that (by forking release:prepare