yes, we could set this up. However there's 2 things: - We're working with "SNAPSHOT" versions most of the time with CI you can hardly control when to use YOUR code versus from the repo in a big projcet - I'm working in a client's office and the network latency between our office and clients office would make it slow
I could run a CI / Hundson / whatever other build management server on my laptop...but then it would not be quicker then just the full build :) Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: [email protected] On Wed, Feb 16, 2011 at 11:41 AM, Thiessen, Todd (Todd) <[email protected]> wrote: > If you have a CI server already building everything, why do you need to build > everything every morning? Can't you just checkout only the one module you > need to change and build that? > >> -----Original Message----- >> From: Zilvinas Vilutis [mailto:[email protected]] >> Sent: Wednesday, February 16, 2011 1:37 PM >> To: a.geo >> Cc: Maven Users List; Jeff >> Subject: Re: subversion vs maven >> >> trust me, not so easy :) >> >> our project has like 20 subsystems which all have 5-10 sub-projects. >> >> Our "core" is extracted into a separate dependency maintained by >> another team, it is also managed by maven ( ~30 subsystems, 10-50 >> projects each ). >> >> Yes, daily updates happen on 5-10 projects, that is why I don't want >> to build the "full" build but only the changed projects and their >> dependents ( web apps ). >> >> Žilvinas Vilutis >> >> Mobile: (+370) 652 38353 >> E-mail: [email protected] >> >> >> >> On Wed, Feb 16, 2011 at 10:37 AM, a.geo <[email protected]> wrote: >> > You mus consider a "core" section, that contain your business main >> code, >> > usually you don't change it. Around it, is the implementation of the >> > requirement. >> > >> > >> > >> > 2011/2/16 Jeff <[email protected]> >> >> >> >> Maybe this question will expose my ignorance, but I thought most build >> >> systems only build the things that have changed unless you do a >> "clean" >> >> each >> >> time or are starting from a fresh checkout as opposed to doing an "svn >> >> update" and then running the build. >> >> >> >> Being new to Maven myself, there could there be an option in the POM >> that >> >> might be forcing a full build each time? >> >> >> >> I would think that as long as you aren't specifying "clean" in your >> build >> >> kickoff process or otherwise forcing a full biuld, you should only be >> >> getting the incremental build, no? Am I off in my understanding? >> >> On Wed, Feb 16, 2011 at 10:18 AM, Zilvinas Vilutis >> >> <[email protected]>wrote: >> >> >> >> > Yes, >> >> > >> >> > However it does a "full build" which takes ~30-40 minutes. But I >> want >> >> > to build only specific projects and their dependents. >> >> > >> >> > Regards >> >> > >> >> > Žilvinas Vilutis >> >> > >> >> > Mobile: (+370) 652 38353 >> >> > E-mail: [email protected] >> >> > >> >> > >> >> > >> >> > On Wed, Feb 16, 2011 at 9:54 AM, Leon Rosenberg >> >> > <[email protected]> wrote: >> >> > > How about hudson? >> >> > > >> >> > > Hudson can watch for svn changes and trigger builds on commit. >> >> > > >> >> > > regards >> >> > > Leon >> >> > > >> >> > > On Wed, Feb 16, 2011 at 5:46 PM, Zilvinas Vilutis >> <[email protected]> >> >> > wrote: >> >> > >> Hello Maven Users! >> >> > >> >> >> > >> Probably this question was already asked, so if there is an >> answer >> >> > >> which I could not find - please point me to the right place. >> >> > >> >> >> > >> >> >> > >> I'm working on an enterprise project where maven integration >> plays a >> >> > huge role. >> >> > >> >> >> > >> However the project is big as a lot of teams are working on it >> and it >> >> > >> takes quite some time to build it ( 30-40 minutes ), which I need >> to >> >> > >> do every morning after an svn update. >> >> > >> >> >> > >> >> >> > >> So I was thinking - is there any way to configure maven to build >> only >> >> > >> the projects which were updated by SVN ( e.g. in the script time >> )? >> >> > >> >> >> > >> >> >> > >> Most likely there is no direct answer...however, I think that I >> could >> >> > >> find a way to gather the project names which were updated in the >> >> > >> shell >> >> > >> script - then I could pass the list of project names to maven >> >> > >> command. >> >> > >> Is there any way to make sure that those and dependent projects >> would >> >> > >> be built in the right order? >> >> > >> >> >> > >> >> >> > >> The project structure is: >> >> > >> >> >> > >> parent >> >> > >> -- subsystem1 >> >> > >> -- s1-project1 >> >> > >> -- s1-project2 >> >> > >> -- subsystem2 >> >> > >> -- s2-project1 >> >> > >> -- s2-project2 >> >> > >> -- s2-project3 >> >> > >> -- subsystem3 >> >> > >> -- s3-project1 >> >> > >> >> >> > >> >> >> > >> Thank you for any ideas! >> >> > >> >> >> > >> >> >> > >> Žilvinas Vilutis >> >> > >> >> >> > >> Mobile: (+370) 652 38353 >> >> > >> E-mail: [email protected] >> >> > >> >> >> > >> ----------------------------------------------------------------- >> ---- >> >> > >> To unsubscribe, e-mail: [email protected] >> >> > >> For additional commands, e-mail: [email protected] >> >> > >> >> >> > >> >> >> > > >> >> > >> >> > -------------------------------------------------------------------- >> - >> >> > To unsubscribe, e-mail: [email protected] >> >> > For additional commands, e-mail: [email protected] >> >> > >> >> > >> >> >> >> >> >> -- >> >> Jeff Vincent >> >> [email protected] >> >> See my LinkedIn profile at: >> >> http://www.linkedin.com/in/rjeffreyvincent >> > >> > >> > >> > -- >> > Cesar De la Cruz Rojas >> > ----------------------------------------------------------------------- >> ------ >> > Sennior Software Engineer >> > ----------------------------------------------------------------------- >> ------ >> > Follow me in Facebook : http://www.facebook.com/aquiles.geo >> > Twitter http://twitter.com/ageo >> > Picture blog http://ageo.deviantart.com >> > >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
