What do you need help with?

Continuous Integration





One of the major pain points of Salesforce deployments is the Big Bang integration of features towards the end of the release cycle. In Big Bang integration, all components are integrated simultaneously at the end of the release and testing is done as a whole. This Big Bang integration results in unpredictable release convergence owing to code merge problems, issues of code coverage and the execution of Apex test.

Flosum mitigates this by providing the framework for Continuous Integration and Testing where in developers commit code throughout the development lifecycle. It removes the painful surprises by committing more often and building the changes and testing it in real-time to ensure a high degree of quality, transparency and predictability.

If developers commit their changes frequently to version control and those changes are periodically deployed to production, there will be fewer integration issues.


Setup for Continuous Integration:

    1. Click on the Settings tab
    2. Specify the Build Organization on the Settings page. This Build Organization should be a replica (or have the baseline) as your source organization.

Steps for Continuous Integration:

    1. Go to the source organization
    2. Change the Visualforce page
    3. Go to Flosum organization
    4. Create a snapshot with the Visualforce page code changes. Commit the changes to a branch, and then commit the changes to the Repository

Results: Go to the Builds tab. You will see the new code changes that were created, automatically packaged and automatically deployed to the Build Organization. Also, all the test classes for that organization were run automatically. Your QA team could now auto-execute all the test classes on that Build Organization.

Congratulations, you have just automated continuous integration! This will decrease the work for your team, and improve your software quality.

Print Friendly and PDF
Was this article helpful?
0 out of 0 found this helpful