Re: Fully automated building from Source Control
+1 Personally, I took some time to try to do this with scripts, etc. as described above, being somewhat daunted by the prospect of yet another learning curve (CI). I found it's certainly doable, but I keep having to invest time in coming up with my own solution for one issue or another (e.g., having a different settings.xml for enterprise (official) builds than for individual developers, who wouldn't be free to deploy to the corporate repo, etc. Once I decided to take a look at CI, I found that the learning curve wasn't bad at all, and in the course of a few hours put an end to all that tinkering with scripts, etc. I happen to use Hudson, and I like it, but there's other good ones out there. I would suggest that you want ready support for release builds. Mark -- View this message in context: http://old.nabble.com/Fully-automated-building-from-Source-Control-tp28122844p28141642.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Fully automated building from Source Control
+1 CI server is the best way to support such process with full automation +1 I could argue the using a CI server is the only reasonable solution. Another +1 Any other solution is a hack! ;-) Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Fully automated building from Source Control
Hi, You could use Maven SCM plugin for bootstrapping the project with minimal pom. http://maven.apache.org/scm/maven-scm-plugin/examples/bootstrapping-with-pom.html rgds, Markku On 3.4.2010 0:09, Steve Cohen wrote: Ok, your needs are probably more extreme than mine. I HAPPEN at present to be the only developer actively engaged on this project so I can get away with non-holy-grail stuff - which explains why I stayed so long with the Eclipse setup, but I would still like to get to the single-command-line total rebuild from scratch. I have less need for CI and as the only developer I can even get away with a local repository (for now) but I would still like to move this ball down the field so it would be easier to extend should things get more complicated. Are you saying then, that managing of builds at this level must depend on something outside of Maven? I'm not likely to find funding for anything more sophisticated than that (I work for a budget-strapped small team inside a large corporation that is off to the side), so I am interested in a solution that depends on nothing beyond Maven itself. We have and use Subversion, and that's about it. David Hoffer wrote: That holy grail is the only way to use maven, imho. I don't know about a single documentation source but there is lots of info available on the web to achieve this. In short we use TeamCity for CI, Artifactory for corporate maven repo, SVN Maven. -Dave On Fri, Apr 2, 2010 at 2:48 PM, Steve Cohensco...@javactivity.org wrote: Over the past few months I have slowly and, on the whole successfully, migrated a project that was based on Eclipse to one that is based on maven (and m2eclipse), in the process, learning much about Maven and I'm generally quite happy with it. It's a nice improvement. The one step I haven't taken yet is generating a fully automated build starting with pristine sources, checking everything it needs out from Source Control and then building it. That has always seemed to me to be the holy grail of automated building, going back to the make days. You nuke all the source, get a fresh copy from the source control (tied to a given tag) and build from scratch. We don't want anything from a developer's working copy involved in any way. I haven't done this with Maven yet and to be fair, I also hadn't done it with the earlier Eclipse-based system in use here but I still want to do it. And yes, I understand that there is a bit of a chicken-egg problem here - where is this definition of everything to be version controlled and how do you avoid nuking that? So there has to be something of a two-tier setup. I know this and accept it. I hadn't spent much time looking at the Maven SCM plugin, but now that I have, I don't really see what I'm looking for there. The examples tend to be very sparse, and Maven - The Definitive Guide doesn't even touch the SCM plugin. Can someone point me at documentation directed toward achieving this holy grail with Maven? Thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Fully automated building from Source Control
mvn scm:bootstrap -DconnectionUrl=maven-scm-url-to-your-soruce -Dgoals=-B release:prepare release:perform will checkout your project, tag it, build from the tag, and finally deploy your artifact to your maven repo. (please look up for the precise syntax) mvn scm:bootstrap -DconnectionUrl=maven-scm-url-to-your-soruce -Dgoals=install will check out your project and built it On Fri, Apr 2, 2010 at 11:28 PM, Markku Saarela markku.saar...@iki.fi wrote: Hi, You could use Maven SCM plugin for bootstrapping the project with minimal pom. http://maven.apache.org/scm/maven-scm-plugin/examples/bootstrapping-with-pom.html rgds, Markku On 3.4.2010 0:09, Steve Cohen wrote: Ok, your needs are probably more extreme than mine. I HAPPEN at present to be the only developer actively engaged on this project so I can get away with non-holy-grail stuff - which explains why I stayed so long with the Eclipse setup, but I would still like to get to the single-command-line total rebuild from scratch. I have less need for CI and as the only developer I can even get away with a local repository (for now) but I would still like to move this ball down the field so it would be easier to extend should things get more complicated. Are you saying then, that managing of builds at this level must depend on something outside of Maven? I'm not likely to find funding for anything more sophisticated than that (I work for a budget-strapped small team inside a large corporation that is off to the side), so I am interested in a solution that depends on nothing beyond Maven itself. We have and use Subversion, and that's about it. David Hoffer wrote: That holy grail is the only way to use maven, imho. I don't know about a single documentation source but there is lots of info available on the web to achieve this. In short we use TeamCity for CI, Artifactory for corporate maven repo, SVN Maven. -Dave On Fri, Apr 2, 2010 at 2:48 PM, Steve Cohensco...@javactivity.org wrote: Over the past few months I have slowly and, on the whole successfully, migrated a project that was based on Eclipse to one that is based on maven (and m2eclipse), in the process, learning much about Maven and I'm generally quite happy with it. It's a nice improvement. The one step I haven't taken yet is generating a fully automated build starting with pristine sources, checking everything it needs out from Source Control and then building it. That has always seemed to me to be the holy grail of automated building, going back to the make days. You nuke all the source, get a fresh copy from the source control (tied to a given tag) and build from scratch. We don't want anything from a developer's working copy involved in any way. I haven't done this with Maven yet and to be fair, I also hadn't done it with the earlier Eclipse-based system in use here but I still want to do it. And yes, I understand that there is a bit of a chicken-egg problem here - where is this definition of everything to be version controlled and how do you avoid nuking that? So there has to be something of a two-tier setup. I know this and accept it. I hadn't spent much time looking at the Maven SCM plugin, but now that I have, I don't really see what I'm looking for there. The examples tend to be very sparse, and Maven - The Definitive Guide doesn't even touch the SCM plugin. Can someone point me at documentation directed toward achieving this holy grail with Maven? Thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Fully automated building from Source Control
But those for for demo only to show off the holygrail maven commands :-) Use a CI server to do you checkout and cut your release. On Sat, Apr 3, 2010 at 12:10 AM, Dan Tran dant...@gmail.com wrote: mvn scm:bootstrap -DconnectionUrl=maven-scm-url-to-your-soruce -Dgoals=-B release:prepare release:perform will checkout your project, tag it, build from the tag, and finally deploy your artifact to your maven repo. (please look up for the precise syntax) mvn scm:bootstrap -DconnectionUrl=maven-scm-url-to-your-soruce -Dgoals=install will check out your project and built it On Fri, Apr 2, 2010 at 11:28 PM, Markku Saarela markku.saar...@iki.fi wrote: Hi, You could use Maven SCM plugin for bootstrapping the project with minimal pom. http://maven.apache.org/scm/maven-scm-plugin/examples/bootstrapping-with-pom.html rgds, Markku On 3.4.2010 0:09, Steve Cohen wrote: Ok, your needs are probably more extreme than mine. I HAPPEN at present to be the only developer actively engaged on this project so I can get away with non-holy-grail stuff - which explains why I stayed so long with the Eclipse setup, but I would still like to get to the single-command-line total rebuild from scratch. I have less need for CI and as the only developer I can even get away with a local repository (for now) but I would still like to move this ball down the field so it would be easier to extend should things get more complicated. Are you saying then, that managing of builds at this level must depend on something outside of Maven? I'm not likely to find funding for anything more sophisticated than that (I work for a budget-strapped small team inside a large corporation that is off to the side), so I am interested in a solution that depends on nothing beyond Maven itself. We have and use Subversion, and that's about it. David Hoffer wrote: That holy grail is the only way to use maven, imho. I don't know about a single documentation source but there is lots of info available on the web to achieve this. In short we use TeamCity for CI, Artifactory for corporate maven repo, SVN Maven. -Dave On Fri, Apr 2, 2010 at 2:48 PM, Steve Cohensco...@javactivity.org wrote: Over the past few months I have slowly and, on the whole successfully, migrated a project that was based on Eclipse to one that is based on maven (and m2eclipse), in the process, learning much about Maven and I'm generally quite happy with it. It's a nice improvement. The one step I haven't taken yet is generating a fully automated build starting with pristine sources, checking everything it needs out from Source Control and then building it. That has always seemed to me to be the holy grail of automated building, going back to the make days. You nuke all the source, get a fresh copy from the source control (tied to a given tag) and build from scratch. We don't want anything from a developer's working copy involved in any way. I haven't done this with Maven yet and to be fair, I also hadn't done it with the earlier Eclipse-based system in use here but I still want to do it. And yes, I understand that there is a bit of a chicken-egg problem here - where is this definition of everything to be version controlled and how do you avoid nuking that? So there has to be something of a two-tier setup. I know this and accept it. I hadn't spent much time looking at the Maven SCM plugin, but now that I have, I don't really see what I'm looking for there. The examples tend to be very sparse, and Maven - The Definitive Guide doesn't even touch the SCM plugin. Can someone point me at documentation directed toward achieving this holy grail with Maven? Thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Fully automated building from Source Control
+1 CI server is the best way to support such process with full automation 2010/4/3 Dan Tran dant...@gmail.com But those for for demo only to show off the holygrail maven commands :-) Use a CI server to do you checkout and cut your release. On Sat, Apr 3, 2010 at 12:10 AM, Dan Tran dant...@gmail.com wrote: mvn scm:bootstrap -DconnectionUrl=maven-scm-url-to-your-soruce -Dgoals=-B release:prepare release:perform will checkout your project, tag it, build from the tag, and finally deploy your artifact to your maven repo. (please look up for the precise syntax) mvn scm:bootstrap -DconnectionUrl=maven-scm-url-to-your-soruce -Dgoals=install will check out your project and built it On Fri, Apr 2, 2010 at 11:28 PM, Markku Saarela markku.saar...@iki.fi wrote: Hi, You could use Maven SCM plugin for bootstrapping the project with minimal pom. http://maven.apache.org/scm/maven-scm-plugin/examples/bootstrapping-with-pom.html rgds, Markku On 3.4.2010 0:09, Steve Cohen wrote: Ok, your needs are probably more extreme than mine. I HAPPEN at present to be the only developer actively engaged on this project so I can get away with non-holy-grail stuff - which explains why I stayed so long with the Eclipse setup, but I would still like to get to the single-command-line total rebuild from scratch. I have less need for CI and as the only developer I can even get away with a local repository (for now) but I would still like to move this ball down the field so it would be easier to extend should things get more complicated. Are you saying then, that managing of builds at this level must depend on something outside of Maven? I'm not likely to find funding for anything more sophisticated than that (I work for a budget-strapped small team inside a large corporation that is off to the side), so I am interested in a solution that depends on nothing beyond Maven itself. We have and use Subversion, and that's about it. David Hoffer wrote: That holy grail is the only way to use maven, imho. I don't know about a single documentation source but there is lots of info available on the web to achieve this. In short we use TeamCity for CI, Artifactory for corporate maven repo, SVN Maven. -Dave On Fri, Apr 2, 2010 at 2:48 PM, Steve Cohensco...@javactivity.org wrote: Over the past few months I have slowly and, on the whole successfully, migrated a project that was based on Eclipse to one that is based on maven (and m2eclipse), in the process, learning much about Maven and I'm generally quite happy with it. It's a nice improvement. The one step I haven't taken yet is generating a fully automated build starting with pristine sources, checking everything it needs out from Source Control and then building it. That has always seemed to me to be the holy grail of automated building, going back to the make days. You nuke all the source, get a fresh copy from the source control (tied to a given tag) and build from scratch. We don't want anything from a developer's working copy involved in any way. I haven't done this with Maven yet and to be fair, I also hadn't done it with the earlier Eclipse-based system in use here but I still want to do it. And yes, I understand that there is a bit of a chicken-egg problem here - where is this definition of everything to be version controlled and how do you avoid nuking that? So there has to be something of a two-tier setup. I know this and accept it. I hadn't spent much time looking at the Maven SCM plugin, but now that I have, I don't really see what I'm looking for there. The examples tend to be very sparse, and Maven - The Definitive Guide doesn't even touch the SCM plugin. Can someone point me at documentation directed toward achieving this holy grail with Maven? Thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Fully automated building from Source Control
On Sat, Apr 3, 2010 at 09:30, nicolas de loof nicolas.del...@gmail.com wrote: +1 CI server is the best way to support such process with full automation +1 I could argue the using a CI server is the only reasonable solution. There are many free alternatives out there. Take a look at http://en.wikipedia.org/wiki/Continuous_integration#Software for some options. My personal favorite is Hudson. /Thomas 2010/4/3 Dan Tran dant...@gmail.com But those for for demo only to show off the holygrail maven commands :-) Use a CI server to do you checkout and cut your release. On Sat, Apr 3, 2010 at 12:10 AM, Dan Tran dant...@gmail.com wrote: mvn scm:bootstrap -DconnectionUrl=maven-scm-url-to-your-soruce -Dgoals=-B release:prepare release:perform will checkout your project, tag it, build from the tag, and finally deploy your artifact to your maven repo. (please look up for the precise syntax) mvn scm:bootstrap -DconnectionUrl=maven-scm-url-to-your-soruce -Dgoals=install will check out your project and built it On Fri, Apr 2, 2010 at 11:28 PM, Markku Saarela markku.saar...@iki.fi wrote: Hi, You could use Maven SCM plugin for bootstrapping the project with minimal pom. http://maven.apache.org/scm/maven-scm-plugin/examples/bootstrapping-with-pom.html rgds, Markku On 3.4.2010 0:09, Steve Cohen wrote: Ok, your needs are probably more extreme than mine. I HAPPEN at present to be the only developer actively engaged on this project so I can get away with non-holy-grail stuff - which explains why I stayed so long with the Eclipse setup, but I would still like to get to the single-command-line total rebuild from scratch. I have less need for CI and as the only developer I can even get away with a local repository (for now) but I would still like to move this ball down the field so it would be easier to extend should things get more complicated. Are you saying then, that managing of builds at this level must depend on something outside of Maven? I'm not likely to find funding for anything more sophisticated than that (I work for a budget-strapped small team inside a large corporation that is off to the side), so I am interested in a solution that depends on nothing beyond Maven itself. We have and use Subversion, and that's about it. David Hoffer wrote: That holy grail is the only way to use maven, imho. I don't know about a single documentation source but there is lots of info available on the web to achieve this. In short we use TeamCity for CI, Artifactory for corporate maven repo, SVN Maven. -Dave On Fri, Apr 2, 2010 at 2:48 PM, Steve Cohensco...@javactivity.org wrote: Over the past few months I have slowly and, on the whole successfully, migrated a project that was based on Eclipse to one that is based on maven (and m2eclipse), in the process, learning much about Maven and I'm generally quite happy with it. It's a nice improvement. The one step I haven't taken yet is generating a fully automated build starting with pristine sources, checking everything it needs out from Source Control and then building it. That has always seemed to me to be the holy grail of automated building, going back to the make days. You nuke all the source, get a fresh copy from the source control (tied to a given tag) and build from scratch. We don't want anything from a developer's working copy involved in any way. I haven't done this with Maven yet and to be fair, I also hadn't done it with the earlier Eclipse-based system in use here but I still want to do it. And yes, I understand that there is a bit of a chicken-egg problem here - where is this definition of everything to be version controlled and how do you avoid nuking that? So there has to be something of a two-tier setup. I know this and accept it. I hadn't spent much time looking at the Maven SCM plugin, but now that I have, I don't really see what I'm looking for there. The examples tend to be very sparse, and Maven - The Definitive Guide doesn't even touch the SCM plugin. Can someone point me at documentation directed toward achieving this holy grail with Maven? Thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To
Fully automated building from Source Control
Over the past few months I have slowly and, on the whole successfully, migrated a project that was based on Eclipse to one that is based on maven (and m2eclipse), in the process, learning much about Maven and I'm generally quite happy with it. It's a nice improvement. The one step I haven't taken yet is generating a fully automated build starting with pristine sources, checking everything it needs out from Source Control and then building it. That has always seemed to me to be the holy grail of automated building, going back to the make days. You nuke all the source, get a fresh copy from the source control (tied to a given tag) and build from scratch. We don't want anything from a developer's working copy involved in any way. I haven't done this with Maven yet and to be fair, I also hadn't done it with the earlier Eclipse-based system in use here but I still want to do it. And yes, I understand that there is a bit of a chicken-egg problem here - where is this definition of everything to be version controlled and how do you avoid nuking that? So there has to be something of a two-tier setup. I know this and accept it. I hadn't spent much time looking at the Maven SCM plugin, but now that I have, I don't really see what I'm looking for there. The examples tend to be very sparse, and Maven - The Definitive Guide doesn't even touch the SCM plugin. Can someone point me at documentation directed toward achieving this holy grail with Maven? Thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Fully automated building from Source Control
That holy grail is the only way to use maven, imho. I don't know about a single documentation source but there is lots of info available on the web to achieve this. In short we use TeamCity for CI, Artifactory for corporate maven repo, SVN Maven. -Dave On Fri, Apr 2, 2010 at 2:48 PM, Steve Cohen sco...@javactivity.org wrote: Over the past few months I have slowly and, on the whole successfully, migrated a project that was based on Eclipse to one that is based on maven (and m2eclipse), in the process, learning much about Maven and I'm generally quite happy with it. It's a nice improvement. The one step I haven't taken yet is generating a fully automated build starting with pristine sources, checking everything it needs out from Source Control and then building it. That has always seemed to me to be the holy grail of automated building, going back to the make days. You nuke all the source, get a fresh copy from the source control (tied to a given tag) and build from scratch. We don't want anything from a developer's working copy involved in any way. I haven't done this with Maven yet and to be fair, I also hadn't done it with the earlier Eclipse-based system in use here but I still want to do it. And yes, I understand that there is a bit of a chicken-egg problem here - where is this definition of everything to be version controlled and how do you avoid nuking that? So there has to be something of a two-tier setup. I know this and accept it. I hadn't spent much time looking at the Maven SCM plugin, but now that I have, I don't really see what I'm looking for there. The examples tend to be very sparse, and Maven - The Definitive Guide doesn't even touch the SCM plugin. Can someone point me at documentation directed toward achieving this holy grail with Maven? Thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Fully automated building from Source Control
Ok, your needs are probably more extreme than mine. I HAPPEN at present to be the only developer actively engaged on this project so I can get away with non-holy-grail stuff - which explains why I stayed so long with the Eclipse setup, but I would still like to get to the single-command-line total rebuild from scratch. I have less need for CI and as the only developer I can even get away with a local repository (for now) but I would still like to move this ball down the field so it would be easier to extend should things get more complicated. Are you saying then, that managing of builds at this level must depend on something outside of Maven? I'm not likely to find funding for anything more sophisticated than that (I work for a budget-strapped small team inside a large corporation that is off to the side), so I am interested in a solution that depends on nothing beyond Maven itself. We have and use Subversion, and that's about it. David Hoffer wrote: That holy grail is the only way to use maven, imho. I don't know about a single documentation source but there is lots of info available on the web to achieve this. In short we use TeamCity for CI, Artifactory for corporate maven repo, SVN Maven. -Dave On Fri, Apr 2, 2010 at 2:48 PM, Steve Cohen sco...@javactivity.org wrote: Over the past few months I have slowly and, on the whole successfully, migrated a project that was based on Eclipse to one that is based on maven (and m2eclipse), in the process, learning much about Maven and I'm generally quite happy with it. It's a nice improvement. The one step I haven't taken yet is generating a fully automated build starting with pristine sources, checking everything it needs out from Source Control and then building it. That has always seemed to me to be the holy grail of automated building, going back to the make days. You nuke all the source, get a fresh copy from the source control (tied to a given tag) and build from scratch. We don't want anything from a developer's working copy involved in any way. I haven't done this with Maven yet and to be fair, I also hadn't done it with the earlier Eclipse-based system in use here but I still want to do it. And yes, I understand that there is a bit of a chicken-egg problem here - where is this definition of everything to be version controlled and how do you avoid nuking that? So there has to be something of a two-tier setup. I know this and accept it. I hadn't spent much time looking at the Maven SCM plugin, but now that I have, I don't really see what I'm looking for there. The examples tend to be very sparse, and Maven - The Definitive Guide doesn't even touch the SCM plugin. Can someone point me at documentation directed toward achieving this holy grail with Maven? Thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Fully automated building from Source Control
IMHO, you need a maven repo to effectively use Maven...and Artifactory is free so why not? There is a free version of TeamCity too for smaller usages then as your needs change you are ready. -Dave On Fri, Apr 2, 2010 at 3:09 PM, Steve Cohen sco...@javactivity.org wrote: Ok, your needs are probably more extreme than mine. I HAPPEN at present to be the only developer actively engaged on this project so I can get away with non-holy-grail stuff - which explains why I stayed so long with the Eclipse setup, but I would still like to get to the single-command-line total rebuild from scratch. I have less need for CI and as the only developer I can even get away with a local repository (for now) but I would still like to move this ball down the field so it would be easier to extend should things get more complicated. Are you saying then, that managing of builds at this level must depend on something outside of Maven? I'm not likely to find funding for anything more sophisticated than that (I work for a budget-strapped small team inside a large corporation that is off to the side), so I am interested in a solution that depends on nothing beyond Maven itself. We have and use Subversion, and that's about it. David Hoffer wrote: That holy grail is the only way to use maven, imho. I don't know about a single documentation source but there is lots of info available on the web to achieve this. In short we use TeamCity for CI, Artifactory for corporate maven repo, SVN Maven. -Dave On Fri, Apr 2, 2010 at 2:48 PM, Steve Cohen sco...@javactivity.org wrote: Over the past few months I have slowly and, on the whole successfully, migrated a project that was based on Eclipse to one that is based on maven (and m2eclipse), in the process, learning much about Maven and I'm generally quite happy with it. It's a nice improvement. The one step I haven't taken yet is generating a fully automated build starting with pristine sources, checking everything it needs out from Source Control and then building it. That has always seemed to me to be the holy grail of automated building, going back to the make days. You nuke all the source, get a fresh copy from the source control (tied to a given tag) and build from scratch. We don't want anything from a developer's working copy involved in any way. I haven't done this with Maven yet and to be fair, I also hadn't done it with the earlier Eclipse-based system in use here but I still want to do it. And yes, I understand that there is a bit of a chicken-egg problem here - where is this definition of everything to be version controlled and how do you avoid nuking that? So there has to be something of a two-tier setup. I know this and accept it. I hadn't spent much time looking at the Maven SCM plugin, but now that I have, I don't really see what I'm looking for there. The examples tend to be very sparse, and Maven - The Definitive Guide doesn't even touch the SCM plugin. Can someone point me at documentation directed toward achieving this holy grail with Maven? Thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Fully automated building from Source Control
On Fri, Apr 2, 2010 at 4:48 PM, Steve Cohen sco...@javactivity.org wrote: The one step I haven't taken yet is generating a fully automated build starting with pristine sources, checking everything it needs out from Source Control and then building it. That has always seemed to me to be the holy grail of automated building, going back to the make days. You nuke all the source, get a fresh copy from the source control (tied to a given tag) and build from scratch. We don't want anything from a developer's working copy involved in any way. Any continuous integration server (Continuum, Hudson, etc.) will do that for you. Reading your second mail, perhaps a simple shell script run on a schedule would do? cd /path/to/somedir rm -rf project svn co project-url cd project mvn clean install You could probably do the checkout with the scm plugin if you insist on doing it all with Maven, but something has to invoke it, or it's not automated... and that's usually a CI server. -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Fully automated building from Source Control
You could use Hudson which is free and setup a job that checks out your repo and does a build. You could use Archiva which is a free repo for a repository or you could do something like have an ant build file which checks out your code and executes maven on it. If it was me though I would use a CI server running locally or on some server somewhere to check out the code and build it so I could also keep an ongoing track of number of tests, test coverage, etc. Check out Hudson and see how easy it is :) Date: Fri, 2 Apr 2010 16:09:28 -0500 From: sco...@javactivity.org To: users@maven.apache.org Subject: Re: Fully automated building from Source Control Ok, your needs are probably more extreme than mine. I HAPPEN at present to be the only developer actively engaged on this project so I can get away with non-holy-grail stuff - which explains why I stayed so long with the Eclipse setup, but I would still like to get to the single-command-line total rebuild from scratch. I have less need for CI and as the only developer I can even get away with a local repository (for now) but I would still like to move this ball down the field so it would be easier to extend should things get more complicated. Are you saying then, that managing of builds at this level must depend on something outside of Maven? I'm not likely to find funding for anything more sophisticated than that (I work for a budget-strapped small team inside a large corporation that is off to the side), so I am interested in a solution that depends on nothing beyond Maven itself. We have and use Subversion, and that's about it. David Hoffer wrote: That holy grail is the only way to use maven, imho. I don't know about a single documentation source but there is lots of info available on the web to achieve this. In short we use TeamCity for CI, Artifactory for corporate maven repo, SVN Maven. -Dave On Fri, Apr 2, 2010 at 2:48 PM, Steve Cohen sco...@javactivity.org wrote: Over the past few months I have slowly and, on the whole successfully, migrated a project that was based on Eclipse to one that is based on maven (and m2eclipse), in the process, learning much about Maven and I'm generally quite happy with it. It's a nice improvement. The one step I haven't taken yet is generating a fully automated build starting with pristine sources, checking everything it needs out from Source Control and then building it. That has always seemed to me to be the holy grail of automated building, going back to the make days. You nuke all the source, get a fresh copy from the source control (tied to a given tag) and build from scratch. We don't want anything from a developer's working copy involved in any way. I haven't done this with Maven yet and to be fair, I also hadn't done it with the earlier Eclipse-based system in use here but I still want to do it. And yes, I understand that there is a bit of a chicken-egg problem here - where is this definition of everything to be version controlled and how do you avoid nuking that? So there has to be something of a two-tier setup. I know this and accept it. I hadn't spent much time looking at the Maven SCM plugin, but now that I have, I don't really see what I'm looking for there. The examples tend to be very sparse, and Maven - The Definitive Guide doesn't even touch the SCM plugin. Can someone point me at documentation directed toward achieving this holy grail with Maven? Thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org _ Hotmail Messenger are available on your phone. Try now. http://go.microsoft.com/?linkid=9724461
RE: Fully automated building from Source Control
Good Evening Mr Cohen if you're a small shop Maven (or Ant) will satisfy your build needs if you're supporting an Enterprise Corporation with lots of codebases to merge and produce artifacts you'll want to look at using Continuous Integration tools such as http://cruisecontrol.sourceforge.net/ hth! Martin Gainty __ Jogi és Bizalmassági kinyilatkoztatás/Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Ez az üzenet bizalmas. Ha nem ön az akinek szánva volt, akkor kérjük, hogy jelentse azt nekünk vissza. Semmiféle továbbítása vagy másolatának készítése nem megengedett. Ez az üzenet csak ismeret cserét szolgál és semmiféle jogi alkalmazhatósága sincs. Mivel az electronikus üzenetek könnyen megváltoztathatóak, ezért minket semmi felelöség nem terhelhet ezen üzenet tartalma miatt. Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Fri, 2 Apr 2010 14:56:20 -0600 Subject: Re: Fully automated building from Source Control From: dhoff...@gmail.com To: users@maven.apache.org That holy grail is the only way to use maven, imho. I don't know about a single documentation source but there is lots of info available on the web to achieve this. In short we use TeamCity for CI, Artifactory for corporate maven repo, SVN Maven. -Dave On Fri, Apr 2, 2010 at 2:48 PM, Steve Cohen sco...@javactivity.org wrote: Over the past few months I have slowly and, on the whole successfully, migrated a project that was based on Eclipse to one that is based on maven (and m2eclipse), in the process, learning much about Maven and I'm generally quite happy with it. It's a nice improvement. The one step I haven't taken yet is generating a fully automated build starting with pristine sources, checking everything it needs out from Source Control and then building it. That has always seemed to me to be the holy grail of automated building, going back to the make days. You nuke all the source, get a fresh copy from the source control (tied to a given tag) and build from scratch. We don't want anything from a developer's working copy involved in any way. I haven't done this with Maven yet and to be fair, I also hadn't done it with the earlier Eclipse-based system in use here but I still want to do it. And yes, I understand that there is a bit of a chicken-egg problem here - where is this definition of everything to be version controlled and how do you avoid nuking that? So there has to be something of a two-tier setup. I know this and accept it. I hadn't spent much time looking at the Maven SCM plugin, but now that I have, I don't really see what I'm looking for there. The examples tend to be very sparse, and Maven - The Definitive Guide doesn't even touch the SCM plugin. Can someone point me at documentation directed toward achieving this holy grail with Maven? Thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org _ The New Busy is not the old busy. Search, chat and e-mail from your inbox. http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_3
Re: Fully automated building from Source Control
Wendy Smoak wrote: On Fri, Apr 2, 2010 at 4:48 PM, Steve Cohen sco...@javactivity.org wrote: The one step I haven't taken yet is generating a fully automated build starting with pristine sources, checking everything it needs out from Source Control and then building it. That has always seemed to me to be the holy grail of automated building, going back to the make days. You nuke all the source, get a fresh copy from the source control (tied to a given tag) and build from scratch. We don't want anything from a developer's working copy involved in any way. Any continuous integration server (Continuum, Hudson, etc.) will do that for you. Reading your second mail, perhaps a simple shell script run on a schedule would do? cd /path/to/somedir rm -rf project svn co project-url cd project mvn clean install You could probably do the checkout with the scm plugin if you insist on doing it all with Maven, but something has to invoke it, or it's not automated... and that's usually a CI server. You make good sense here. Having gained some proficiency with Maven, I now want to use it for everything. Probably a mistake. If your only tool is a hammer, everything looks like a nail. Etc. Etc. Probably best to go outside of Maven to resolve chicken vs egg. CI can be added later as needed. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Fully automated building from Source Control
Martin Gainty wrote: Good Evening Mr Cohen if you're a small shop Maven (or Ant) will satisfy your build needs if you're supporting an Enterprise Corporation with lots of codebases to merge and produce artifacts you'll want to look at using Continuous Integration tools such as http://cruisecontrol.sourceforge.net/ Hah. We're an afterthought - a small shop inside a mega-corporation with few resources and too much red tape inherited from our parent. Our line of business gets good-corporate-citizen points for the megacorp so we're not watched as closely as are other teams more closely associated with the bottom-line. But not many resources flow our way either. We're a team that makes do with what we've got and on the positive side have less interaction with the process police. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
