It does if you use the newly created parameterized build where you can specify the branch ;-)
http://jenkins.buildacloud.org/view/parameterized/job/build-systemvm-parameterized/ Cheers, Hugo > On 3 dec. 2014, at 15:52, Will Stevens <wstev...@cloudops.com> wrote: > > It has not been merged into 4.5 yet, so kicking off a system vm build will > not be using this code yet. :) > > ws > > > *Will STEVENS* > Lead Developer > > *CloudOps* *| *Cloud Solutions Experts > 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 > w cloudops.com *|* tw @CloudOps_ > > On Wed, Dec 3, 2014 at 3:25 AM, Hugo Trippaers <h...@trippaers.nl> wrote: > >> Kicking of a systemvm build of this branch on jenkins. >> >> (Created a parameterized systemvm build job where you can specify a branch) >> >> >> Cheers, >> >> Hugo >> >>> On 3 dec. 2014, at 00:42, Will Stevens <wstev...@cloudops.com> wrote: >>> >>> I have tested the equivalent fix in master and it is working perfectly. >>> The code in 4.5 is a bit different, but this should fix it in 4.5. I >> have >>> tested the basic logic on my system, but once this gets merged I will >> kick >>> off a 4.5 build of the system vms to verify that it fixes the build >> systems >>> (they are currently broken). >>> >>> This fix is related to this issue: >>> https://issues.apache.org/jira/browse/CLOUDSTACK-7959 >>> >>> --- >>> >>> I have created a separate topic in the dev list to discuss the workflow I >>> am using here... >>> >>> *Will STEVENS* >>> Lead Developer >>> >>> *CloudOps* *| *Cloud Solutions Experts >>> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 >>> w cloudops.com *|* tw @CloudOps_ >> >>
