CODEWITHSUNDEEP
jenkinscontinuous-integrationrtc
Dênis Vilela
Dênis Vilela

Reputation: 23

Why to use Jenkins with RTC for Continuous Integration

I'm trying to convince my Configuration Manager to use Jenkins with RTC (witch we already use for Source Control, manual builds and many other things), as my boss asked.

I'd like to know why to use the Jenkins with RTC. I know RTC can do Continuous Integration, but what Jenkins can add to it?

Upvotes: 2

Views: 1976

Answers (1)

VonC
VonC

Reputation: 1324128

RTC doesn't have a build engine in itself. It has a build engine toolkit which abstract the actual build engine (BuildForge, Hudson, Jenkins, ...)

If you want to do continuous integration from RTC, you need a build engine.
The official one is IBM BuildForge (not free).
Since RTC4, Jenkins (free) is also officially supported, with an RTC plugin for Jenkins to install on the Jenkins side (as well as the Build System Toolkit in the RTC downloads)

What Jenkins can add is:

  • a greater familiarity with the tool
  • a great list of plugins
  • the possibility to experiment locally (even without RTC)
  • a good connectivity with other source control tools (SVN, Git) in addition of Jazz RTC.

Upvotes: 1

Related Questions