Automated Salesforce development process from Development, through Test and QA to Production

Modernize your Salesforce CI/CD process with CloudBees or Jenkins

Get insight and control over your Salesforce development -and deployment processes with CloudBees/Jenkins

How to use Cloudbees/Jenkins as a CI/CD solution for Salesforce

Solution components

CloudBees icon


CloudBees/Jenkins is the automation server responsible for orchestrating the entire CI/CD flow. All steps in the pipelines are executed by delegating the IKAN Salesforce plugins.

IKAN Salesforce plugins for CloudBees

IKAN Salesforce Plugins

The Salesforce plugins are Model-driven. This means that the actions which handle the Salesforce continuous integration and deployment, are driven by customizable models and related parameter files. This approach makes the steps in your pipeline versatile and easily customizable.

Start Jenkins, import the Salesforce plugins and you’re done!

Considering you have a working CloudBees/Jenkins instance set up, it doesn’t take much effort to start using modern CI/CD practices on Salesforce. Once the IKAN Salesforce plugins are installed and configured to meet your requirements, you’re ready.

Salesforce development lifecycle automation and devops toolchain orchestration

CloudBees or Jenkins based CI/CD for Salesforce

Salesforce is a vital part of today's software ecosystem, alongside mobile -and web applications. The digital world expects agility, Continuous Integration and Continuous Deployment. CloudBees + IKAN Salesforce plugins brings agility to Salesforce implementations.

  • Contemporary versioning safeguards your code and makes parallel development and the use of modern Salesforce IDE's possible
  • Automated Build scripts are generated. We run the script and collect all objects in an archive.
  • Automated Promote scripts are generated.
Salesforce development lifecycle automation and devops toolchain orchestration

Orchestrate your Salesforce toolchain

CloudBees + IKAN Salesforce plugins use standardized scripts to automate your existing tools, there's no need to change anything. The only difference is that you will be using Jenkins/Cloudbees to launch Build (CI) and Promote (CD) actions.

Every step is logged, including Build and Promote, to be consulted at any time.

All you need to do is enter the related ticket (identifier) from your favorite requirements or issue tracking tool when commiting code.

Jenkins/CloudBees plugins to JIRA or other will commence the process flow, update the ticket in your requirement or issue tracking tool, and inform you about which builds and deploys the ticket is part of.

Source code can be written in any Salesforce IDE. The code is stored in a VCR and then get scanned to generate a script following your standards and naming conventions.

The generated script is started and when finished, the results are retrieved by CloudBees + IKAN plugins and collected in an archive. Every step of this process is logged.

As part of the process you can deploy code to test environments or you can write a script to run the SalesForce testing tool of your choice.

Packaging is done during the Build process and creates an archive. Archives are then used by the deploy process as “source”.

The generated script is started for Deployment. This entire process is logged.

Leading you from idea to implementation in 3 simple steps


Together we analyze your current development and release process and define the optimal Salesforce DevOps solution for your company. We clearly draw the roadmap on how to get there.

Form by ChronoForms - OK, let's start

Pilot (POC)

Next we proof that the proposed solution works, by example. It takes only one week to deliver our proof-of-concept!


After the POC is finished we have your business case ready, give you a commercial proposal and begin implementing the solution.

Faster Salesforce development

Developing with Salesforce IDE

Keep developing using your trusted Salesforce IDE.

Get a live demo!

Let us give you personal insight on how DevOps can accelerate your SalesForce development -and release process.

Form by ChronoForms - Yes, give me insight
SalesForce build script archive

The result of a CloudBees + IKAN SalesForce plugins build script is an archive, including all related info.

Plugin model to configure your deployment

The Salesforce plugin model to configure your deployment.

The Build archive process

Every single action is logged. In this example we see the details for every step in the Build archive process.


What our customers are saying

  • RMA client picture

    Antonio Motta - ICT infrastructure manager, RMA (Italy)

    "Our goal was to have one product, that managed the whole build and deploy process for all the platforms we used to deliver our IT services. We saved more than 2/3 on the software maintenance cost."

  • Constellation Brands client picture

    Jim McGrath - Data Warehouse Manager, Constellation Brands (USA)

    "My internal team was excited about the possibilities your software offers and is anxious to hear next steps. Additionally, you should know that I have ensured my team knows the level of effort and support your team has provided.

    It is hands down the best support I have seen from any vendor I’ve worked with."

  • Vivium client picture

    Willy Mutsaerts - Technology Architect and Software asset management, P&V (Belgium)

    "IKAN allowed us to modernize our mainframe development as we wanted to use an eclipse based development environment and needed to have a compatible life cycle management solution to replace our current mainframe only version control software.

    And IKAN allowed us to interface with the mainframe and has extensive customization possibilities."

    Watch Mr. Mutsaerts talk about IKAN:

    Benefits of IKAN ALM Business Case What makes IKAN ALM unique
  • GMF client picture

    Jerome Rouil - IT Team Manager, GMF COVEA group (France)

    "We did a POC to verify if IKAN could support our different ways of deploying (on different types of platforms), our current way of doing development and the build and deploy scripts we were currently using.

    IKAN allows us to work from everywhere, and to reuse existing scripts. We could use our existing security system (LDAP), SMTP for messaging and notifications.

    We use IKAN for all our JAVA applications and SAS reporting that are deployed to 30 different locations"

People are choosing DevOps because they want

Higher quality

As developers will version their code and as parallel development is supported you will have a more sound code base. Managing the many different releases and hot fixes becomes fast, transparent and reliable.

More frequent deploys

A complete and automated process (build, deploy, approval and notification) is triggered once a developer commits his code to the version control repository. This process is reliable, repeatable and auditable so you can you can deploy more frequently.

Lower development costs

More frequent and qualitative deploys means happy business people since they'll have their desired functionality available faster. The automated process eliminates human mistakes and allows people to do more interesting work. A true win/win.

These companies already use our solutions

A list of our clients: Vivium, Reale Mutua, GMF and Constellation Brands