It's all about the answers!

Ask a question

Use Jazz Build engine with SVN

Dr. Hans-Joachim Pross (1.1k4458) | asked Sep 01 '14, 11:57 a.m.
Is there a way to use the Jazz Build engine (with or without Jenkins), when the source code files are in SVN?
When with Jenkins, what is the benefit of using the Jazz Build engine and not only Jenkins?

3 answers

permanent link
Arne Bister (2.6k12832) | answered Sep 01 '14, 12:56 p.m.
while you can use a regular ANT build definition or Jenkins definition to run with SVN there is no particular JBE integration with SVN as with the Jazz SCM. You would have to run your own commands within the ANT script or other build scripts to load the right sources from SVN.
The main benefits of using the Jazz Build engine: build result objects which can link to work items within Jazz, have downloads / links attached to them, store properties ; can be started from any jazz client ; dashboard widgets to display latest build results ; can use build toolkit with custom ant tasks (also your own java classes extending custom ant task) to communicate with build result object at build run time.

If this is helpful please accept the answer.

- Arne 

permanent link
sam detweiler (12.5k6195201) | answered Sep 01 '14, 1:59 p.m.
I would only use JBE when there is no other option..  but you can get almost all the benefit out of the box when using Jenkins and the RTC plugin, and ant builds as Arne mentions.  

the only thing missing is the linkage to  SVN changes in workitems.. which could be created very similarly to how the git hook does it.  there are rest apis to create links, and the hook will tell u the revision and the commit comment must include a specific phrase for the rtc workitem.

permanent link
Spencer Murata (2.3k115971) | answered Sep 03 '14, 10:08 a.m.
 If you have SVN, there is no reason to use JBE.  Stick with SVN and use Ant tasks or the RTC API to pull in additional information to RTC.  Or if you are okay directing users to Jenkins, you can just use the integration to link the RTC build to the Jenkins build and leave it at that.

The JBE integrates well with the RTC SCM which is really the only compelling reason to use it since it handles all the contributions to RTC build.  But if you will stick with SVN, then Jenkins is the best solution.

Your answer

Register or to post 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.