Jenkins to automate Pega Robotics build?

Hi Team,

We use Jenkins as an organization standard for build automation. Are there any plugins or support for Jenkins? Has anybody used it?


***Updated by moderator: Lochan to add Categories***

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.


Keep up to date on this post and subscribe to comments

July 7, 2017 - 4:46pm

There aren't any plugins for us explicitly, but since we're written in C# that would probably be the best case to start with. I don't see any reason why you couldn't use Jenkins, but to my knowledge there's no documentation to show it has been used before.

July 13, 2017 - 2:00pm

Thanks, Grona. Is there any documentation around command-line/scripts that can be used to initiate a build? Trying to  comb through documentation, but cannot find anything.

July 14, 2017 - 1:38pm

There is currently no documented way or support for an automated build process (to create Pega Robotics deployment packages). If this is functionality you require, I would suggest making a product request through your account management to get it added to the pipeline.

July 21, 2017 - 7:48am

Aravind, I have created a custom build script which I use to both pull the latest code down from TFS/Git and then run a small command-line application that uses the "MSBuild.exe" very similar to what occurs within Visual Studio (in our case we're using VS2015 with the 8.0.1028 plug-in).  It works very well, the only issue I have is that each time I run it the DeploymentVersion value is updated.

Let me know if you have any further questions.


August 11, 2017 - 7:39am
Response to ErikS855

Thanks, Erik. We were able to do something similar. Renaming the project file extension to  .sln helped resolve a compilation error when using MSBuild for us.



March 6, 2018 - 8:52am

You can use the MSBuild plugin for Jenkins to build Pega projects. The build machine needs the pega visual studio plugin installed on it, along with msbuild. Once a Pega project is in the Jenkins workspace, MSBuild just needs to point to the solutions .sln file.

To get an understanding of how this works, I would recommend firing up command prompt, navigating to the directory your automation lives on your development machine, and invoking MSBuild on the .sln file to see how the build process works. You can also use the command

msbuild.exe /h

to see different command line arguments that you might need to pass (like whether or not to build in Debug or Release mode). Jenkins is essentially doing what you would be doing on the command line, and anything you can do from the command line you can do from Jenkins.

August 15, 2018 - 9:14pm