Continuous Integration

Kentico’s out-of-the-box Continuous Integration module, combined with Source Control, offers you the ability to move development coding and data changes automatically from Development through QA, Staging, and on to Production. It supports the synchronization of work between developers and development teams with the same workflow, by allowing them to store code and data in a file system, commit them to Source Control, and import them back into a different Kentico installation within a second environment.

Support for All Operations

Continuous Integration in Kentico allows you to move changes made during development automatically from one environment to another. It supports all operations, from the creation and updating of objects to their deletion, and automatically synchronizes these changes locally before storing them in the Source Control.

Rollback Functionality

All changes made are stored in the Source Control and are preserved even when new versions are created. This gives you the power to rollback the system in the case of any errors or mistakes. Unlike normal versioning, the rollback functionality of Kentico’s Continuous Integration gives you the ability to restore any previous version, so you can always return to a working environment.

Conflict Resolution

During manual synchronization of developers’ work, there are sometimes conflicts in the system that need to be solved. With Kentico’s Continuous Integration, following collision detection, you can resolve any conflicts in the Source Control rather than just overwrite each other’s work. This means that numerous developers can work on the same project, and their work can be synchronized automatically without any data lost.

Advanced Filtering

Continuous Integration in Kentico allows you to select only the data you want to be synchronized, meaning if you don’t need all of it synchronized, you don’t need to. This helps improve performance and allows you to be more efficient when working on certain project elements. You are not forced to synchronize all elements of the development build continuously. Actions supported by this advanced filtering are the ability to exclude object types, exclude individual pages, exclude custom modules, exclude groups or sites, and exclude individual objects.

Stable and Readable XML Files

Using stable and readable XML files in Kentico’s Continuous Integration process means you can see and merge their changes more quickly, allowing for increased productivity among the development team.

Support for TFS, GIT, VS, and Any CI Server

With Kentico’s Continuous Integration, you are not limited by which tools you can use. Kentico fully supports the use of Team Foundation Server (TFS), GIT Source Control, Visual Studio, and any Continuous Integration server.

Development Team Collaboration

By supporting the use of Continuous Integration, Kentico removes the problem of all data being stored on local machines only. All code and data changes made are stored in the Source Control and can be accessed at any time by any other team member to continue the development process. This reduced dependency on individual developers, combined with automatic Source Control synchronization reduces development time by up to 30%.

Staging Support

Stay on the safe side and use Staging  to synchronize the page data changes with a production server. Continuous Integration logs staging tasks during the restoration of the continuous integration repository, and lets you synchronize the changes with the chosen production site.

We're named a Strong Performer in the Q4 2018
Forrester Wave™ for WCM!