Find your content:

Search form

You are here

Is there a way to setup continous integration for apex tests?


I would like to have continous integration (with Jenkins) for my apex code in order to run them automatically after each push to my git repository. Does anyone know a way how to do that?

Attribution to: Andree Wille

Possible Suggestion/Solution #1

I wrote an article describing how to achieve this: We are using this in our company and deploying more than 10000 components every month including objects, fields, workflow and classes

Attribution to: Francisco Riccomagno

Possible Suggestion/Solution #2

Check out the sample code for the ApexTestQueueItem sObject here:

and the more involved cookbook recipe:

Attribution to: Rich Unger

Possible Suggestion/Solution #3

RABIT [ Rapid Automated Build Install and Test ] has a salesforce specific edition which has all the CI needs like meta deployment , Apex Unit Testing , scheduled dataloading bundled into a product . you can visit for the documentation

Attribution to: Niranjan

Possible Suggestion/Solution #4

We're trying to set up the same, and while we still have to get some configurations right, I do think we have gotten the overall setup.

Using github plugins to jenkins you can poll for repository changes. We're using ssh keys between jenkins and github as authentication.

Jenkins uses ANT, and so does the migration tool, you can use the deploy xml file you'd write for the migration tool to run with ant from jenkins, this can include that all tests need to be ran.

I believe this is the setup used by quite some teams already, yet no one seems to have written a full description on how to set it up publicly (at least, I've not found one). I may give it a try once we have our system fully running

Attribution to: Samuel De Rycke

Possible Suggestion/Solution #5

Download the Migration Toolkit and start tinkering with it. The salesforce-ant jar contains a component for deploying code, but that component also allows you to run either all tests or individual tests (specified by a child element under the deploy component).

Unfortunately, there is no component for explicitly running tests, so it looks like (I havent tried this myself) that you must deploy something in order to run the tests.

Hope that helps.

More info on the migration toolkit:

Attribution to: James Loghry

Possible Suggestion/Solution #6

There are a couple of decent Dreamforce presentations here: Team Development: Possible, Probable, and Painless and Continuous Integration in the Cloud.

We ran into some issues with this in practice and there was no way to get true automation (i.e., set it and forget it). We were also setting it up with Selenium.

Here were the issues that I remember.

  1. Some features aren't supported in the metadata API and cannot be moved via the ant migration. If you have any unit tests that work with those features, you have to manually work on your CI org.

  2. Deletions are harder to maintain. You have to manually update and apply a destructiveChanges.xml file or replicate the deletion in the CI org.

  3. We ran into a situation where some metadata XML files had 'invalid' data in them. The suggested solution was to build a post checkout script that manipulates the offending XMLs into valid XMLs. Not ideal.

  4. On projects, we wanted to track just our changes and push out just our changes in source control. In theory, this would allow much easier rebaselining. This would have required more manual maintenance of XML files (e.g., 2 new fields added on Account and only want to push those 2 fields not all (*) fields).

My conclusion is that it is worth doing if you can get it set up, but if you are working on shorter term projects and don't have a decent amount of time budgeted in for it, it probably isn't worth setting up.

Although it isn't CI, check out You could set it up to run every hour or something like that.

Attribution to: Peter Knolle

Possible Suggestion/Solution #7

I'm doing a presentation at Dreamforce '12 on this exact subject: Team Development and Release Management for ISVs

In the session I'll outline going through a complete CI life-cycle (develop, version control, build, package, deploy to AppExchange).

This session is mostly geared to AppExchange releases but could easily be a good building block for anyone whom wants to do CI. I'm hoping to get the Github repo up which will include a link to the Amazon AMI preconfigured like the one we use to manage multiple devs and builds with Jenkins at Bracket Labs

Attribution to: jordan.baucke

Possible Suggestion/Solution #8

I feel that continuous integration for Salesforce is a lot of work given the nature of the platform, metadata, cloud based architecture with everything being routed by web services. However, I have used Flosum and it is an excellent solution for automated builds, much better than using Jenkins for Salesforce. We found that it not only automates the apex tests, but also helps with many activities for Salesforce release management. I would encourage you to try it out.

Attribution to: Kevin Bellati
This content is remixed from stackoverflow or stackexchange. Please visit

My Block Status

My Block Content