RTC build engine vs Jenkins build (via RTC source control)
Hi all,
I have a small project starting up in RTC, using RTC for all aspects of the life cycle.
There are some other projects using RTC as well, but at the moment only for planning/tasking purposes (and still in Clearcase for source control, or other CM tooling).
The other projects, for the mostpart, also use Jenkins for automated building.
This newer small project in RTC is being used as a pilot project to test out the built in RTC build engine features.
Ultimately (in the next few weeks) a decision will be made if all the projects will move to the RTC build engine (as the plan is to move the rest from Clearcase source control to RTC as well in near future) ... or, stick with the Jenkins build engine, with the understanding RTC is fully featured to allow source control from RTC to kick off Jenkins builds and whatnot.
From what i've seen so far (still using RTC 4.0.2, soon upgrading to 5.x and hopefully 6.x in coming weeks) there is no comparison, Jenkins appears much better and fully featured whereas RTC build engine seems to be lagging behind (keeping in mind i'm not familiar with 6.x yet).
Does this sound about right, and/or can you provide suggestions, feedback or experience in the above?
thanks!
Paul N
I have a small project starting up in RTC, using RTC for all aspects of the life cycle.
There are some other projects using RTC as well, but at the moment only for planning/tasking purposes (and still in Clearcase for source control, or other CM tooling).
The other projects, for the mostpart, also use Jenkins for automated building.
This newer small project in RTC is being used as a pilot project to test out the built in RTC build engine features.
Ultimately (in the next few weeks) a decision will be made if all the projects will move to the RTC build engine (as the plan is to move the rest from Clearcase source control to RTC as well in near future) ... or, stick with the Jenkins build engine, with the understanding RTC is fully featured to allow source control from RTC to kick off Jenkins builds and whatnot.
From what i've seen so far (still using RTC 4.0.2, soon upgrading to 5.x and hopefully 6.x in coming weeks) there is no comparison, Jenkins appears much better and fully featured whereas RTC build engine seems to be lagging behind (keeping in mind i'm not familiar with 6.x yet).
Does this sound about right, and/or can you provide suggestions, feedback or experience in the above?
thanks!
Paul N
2 answers
The JBE build engine is designed to be a maximally simple and easy to use. The Jenkins build engine is designed to be maximally powerful. So each has its own place (and you can easily use both for different types of builds). Your end users (developers) often don't have to know/care which one is being used for a given build. They just ask for a given build to be performed, and the appropriate build engine picks up the build request. So you should feel free to use whichever one you prefer. A team that doesn't think it needs the power of Jenkins can just start with the JBE, and if they eventually discover they need the power of Jenkins, they can largely just take their existing JBE build scripts and have them be invoked by the Jenkins build engine.
I recommend going to Jenkins. you will go there eventually.
JBE is easy, true, but thats because you can only do a limited amount of things.
thats the first step on Jenkins, just the extract and compile.
the plugin support in Jenkins makes this a real CI system, and you will want to be there sooner, no point setting yourself up for rework.
JBE is easy, true, but thats because you can only do a limited amount of things.
thats the first step on Jenkins, just the extract and compile.
the plugin support in Jenkins makes this a real CI system, and you will want to be there sooner, no point setting yourself up for rework.