In fact it works for multiple Hudson builds. We have serveral hudson builds running concurrently: one for the currently released version, one for the trunk, and others for customer-specific builds. Only one maven profile is needed for the Hudson builds because these builds pass the version in to maven.
On Mon, Sep 21, 2009 at 9:42 AM, Indrajit Raychaudhuri <[email protected]>wrote: > > Ryan, > > Nice workflow! But I guess this works better when one is a Hudson build > and the other a manual build. What David was looking for is involves two > Hudson builds. > > Do you think this would serve the purpose using Maven profile (mvn -P > instead of mvn -D)? > > http://github.com/dpp/liftweb/commit/45dc2e55bd37104aa2a56990914b38a1895b18f6 > > > Cheers, Indrajit > > > On 21/09/09 6:28 PM, Ryan Donahue wrote: > > > > We pass the release version into maven from hudson. > > > > In the POM: > > <version>${releaseVersion}</version> > > > > In the hudson build's maven goals and options field: > > -DreleaseVersion=1.1-SNAPSHOT > > > > Actually, we go a little further by creating a hudson build property > > called releaseVersion. Then the maven options include: > > -DreleaseVersion=${releaseVersion}. > > This results in a prompt whenever you do a manual build, allowing you > > to change the releaseVersion property (good for release builds). > > > > If you go this route, you'll want to have at least 2 profiles in the > > POM, one for hudson builds invoked when the releaseVersion property is > > present and a default profile for developers that sets the > > releaseVersion property to some default (we just use "dev" so local > > developers' .war files are built as "utipu-dev.war"). We use this > > strategy for utipu.com (not a lift app) as well as for our internal > > lift apps. It works well for us, but may or may not be appropriate > > for a framework build. > > > > > > > > On Sep 18, 7:38 pm, David Pollak<[email protected]> > > wrote: > >> Folks, > >> Is there a clean and easy way that anyone knows of to have Hudson do > >> alternate builds from different Git branches and put them in SNAPSHOTS > with > >> different versions (e.g., 1.1-SNAPSHOT_DPP_ACTOR)? > >> > >> I am making some wholesale changes to Lift's use of Actors (basically > >> getting rid of all Scala Actors and creating some simple traits that > Akka or > >> other systems can implement so that Lift-based systems can choose > different > >> Actor implementations. > >> > >> Given that these changes are non-trivial, I'd like to run a parallel > version > >> of Lift for at least a few weeks and get feedback on the API changes and > >> performance before committing the code to the main branch, but I want > the > >> code to available in Hudson. > >> > >> So... any ideas? > >> > >> Thanks, > >> > >> David > >> > >> -- > >> Lift, the simply functional web frameworkhttp://liftweb.net > >> Beginning Scalahttp://www.apress.com/book/view/1430219890 > >> Follow me:http://twitter.com/dpp > >> Git some:http://github.com/dpp > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
