Hi,

Hi,

RTC+Jenkins+maven+UCD all work together and can all be used to construct a CI/CD pipeline.  You configure RTC to use a Hudson/Jenkins Build Engine.  The RTC build engine is configured to connect to your Jenkins master.  Then you define a Jenkins Maven job.  The jenkins implementation will need the Team Concert plugin and the job should reference a Hudson/Jenkins build definition (the next step) back in RTC.  Additionally, you will need to install the RTC Build System Toolkit on the target machine(s) (Jenkins Master and Slaves).   Next you define a Hudson/Jenkins build definition that identifies the Repo workspace to use and load directory, etc.  Then you need to modify your jenkins job to reference the build definition you just created. There are Ant examples out there but no good Maven examples as there are certain parameters that Jenkins needs to pass to RTC and other things you need to do so that the build works from RTC or from Jenkins.  At this point you have RTC kicking off Maven builds in Jenkins and vice versa.

If you are using Maven, then I am assuming there is repository manager in your space.  I prefer Artifactory because it supports more integration possibilities.  Add the Artifactory plugin to Jenkins and maven install into your repository manager.  Add the UCD plugin into Jenkins.  This will allow you to trigger a post build UCD deploy process.  What actually happens is defined in the process.  You can have processes that simply install components or install and deploys them in one shot.  There are two ways to leverage the repo manager - there is a maven source config plugin and an Artifactory source config plugin.  They behave differently in terms of what they import into UCD so you will have to experiment a bit.

I built this pipeline around the JPetStore application and a plethora of different online resources.  There are also a bunch of videos out there.  The problem is none of them address maven.  Hope you find this answer helpful.