Jazz local builds stop executing after workbench restart
Jazz local builds appear to stop executing after I restart
the workbench. I have working local build definitions. If I restart TeamConcert and request a build for these local builds, they show as 'Pending' in the build queue forever. If I create a new local build (a simple one, selecting all the defaults and creating the sample build.xml in Local Settings/Temp) that build will execute and then trigger the other pending local builds to execute. Is there another way to kick off an existing build definition after a restart other than creating a new build definition? |
2 answers
On Sun, 21 Oct 2007 14:57:56 +0000, harryk wrote:
If I restart TeamConcert and request a build for these local Just to be sure, you did start the local build server up, right? If I recall correctly, when you create a _new_ local build definition and all, Jazz will kick off a local build server. Regards, Rem |
This is a known issue with the M2 build setup story. The setup wizard is
creating a java launch to run the build engine for you locally. This launch is not automatically run for you every time you start the workbench. If you go to the java perspective and click the "Run" dropdown on the toolbar, you should see a Jazz Build Engine launch. This story has been changed in M3 to reduce the confusion. We no longer create and run this magic launch for you. You must start the build engine yourself on the command line (as you would on a real build machine): jbe -repository http://localhost:9080/jazz -engineId engine1 -userId myUser -pass myPass -sleeptime 1Of course, replace engine1, myUser, and myPass with the appropriate values.You can also start the engine this way in M2 if you like.The getting started doc has been updated for M3 at https://jazz.net/learn/LearnItem.jsp?href=content/docs/build-setup/index.html |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.