tag:blogger.com,1999:blog-637417304187784899.post5976677730187439652..comments2024-01-04T09:04:42.121+00:00Comments on James Strachan's Blog: LazyWeb: spawning maven builds via VMWare in your CI toolJames Strachanhttp://www.blogger.com/profile/12591119339035350067noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-637417304187784899.post-53580514879825232502007-06-25T06:41:00.000+00:002007-06-25T06:41:00.000+00:00Awesome, thanks Mark!Awesome, thanks Mark!James Strachanhttps://www.blogger.com/profile/12591119339035350067noreply@blogger.comtag:blogger.com,1999:blog-637417304187784899.post-53479740646632928522007-06-25T02:56:00.000+00:002007-06-25T02:56:00.000+00:00James I've added a page about adding variables to ...James I've added a page about adding variables to your Bamboo build <A HREF="http://confluence.atlassian.com/display/BAMBOO/Using+custom+build+variables" REL="nofollow">here</A><BR/><BR/>Basically, you should be able use the Maven goal<BR/><BR/>clean package -DbambooBuildNumber=${bamboo.buildNumber}<BR/><BR/>and then access the passed property in your pom.xml by using: <BR/><BR/>${env.bambooBuildNumber}<BR/><BR/>which you could then use to calculate a port number.<BR/><BR/><A HREF="http://www.atlassian.com/software/bamboo/" REL="nofollow">Give us a yell</A> if you have any problems here.Unknownhttps://www.blogger.com/profile/02053024598976943931noreply@blogger.comtag:blogger.com,1999:blog-637417304187784899.post-9799194554673631922007-06-21T16:14:00.000+00:002007-06-21T16:14:00.000+00:00Thanks for the comments guys.Yeah - ideally I'd re...Thanks for the comments guys.<BR/><BR/>Yeah - ideally I'd refactor all those hundreds of tests in all the various different projects to always take a system property / maven property to define the port to use. One of these days I'll get there & do that... its just gonna take a lot of time.<BR/><BR/>I'd still love to have a bunch of VMWare images of different JDKs / OSes which I can use on a single Bamboo server though! :)<BR/><BR/>BTW Thanks Mike - the build number idea is cool - I"ll definitely use that one of these days. Whats the property its available as?James Strachanhttps://www.blogger.com/profile/12591119339035350067noreply@blogger.comtag:blogger.com,1999:blog-637417304187784899.post-84242711400778898572007-06-21T15:28:00.000+00:002007-06-21T15:28:00.000+00:00Mate - isn't there a simpler solution here? Bamboo...Mate - isn't there a simpler solution here? <BR/><BR/>Bamboo can pass the build number into your build (and a number of other parameters too), so just do that as a system property.<BR/><BR/>Then, inside your build just bind to a port that's some function of the build number. For example, bind to 10000 + the last 3 digits of the build number? <BR/><BR/>Everything in your build and tests could simply look at that system property (or else use a default) to then determine what ports to run against. <BR/><BR/>Voila - individual, parallel builds. Or did I miss something?<BR/><BR/>mmcannonhttps://www.blogger.com/profile/09632212659779265722noreply@blogger.comtag:blogger.com,1999:blog-637417304187784899.post-10245922530858103562007-06-21T14:57:00.000+00:002007-06-21T14:57:00.000+00:00Perhpas if the VMWare box is setup to use a remote...Perhpas if the VMWare box is setup to use a remote file system like NFS or SMB that maps to the Bamboo file system then all Bamboo would have to do is to use ssh to issue a remote maven build command.Hiram Chirinohttps://www.blogger.com/profile/16983993595849131879noreply@blogger.comtag:blogger.com,1999:blog-637417304187784899.post-71536460705633931582007-06-21T11:25:00.000+00:002007-06-21T11:25:00.000+00:00as a middle ground, how about binding each test to...as a middle ground, how about binding each test to a different IP address? then the ports can conflict and you can have, even, a dynamic hosts file with logical hostnames per test..Ken Hornhttps://www.blogger.com/profile/00583097214217195779noreply@blogger.com