Table of Contents

Configuring continuous integration and continuous deployment


Only available versions of this content are shown in the dropdown

Incorporate the effects of work of your development teams by implementing continuous integration and deployment. Additionally, to speed application development and minimize the risk of conflicts, you can provide separate sandboxes in which developers can work on multiple features simultaneously.

  • Branches and branch rulesets

    Branches help you manage work in development environments in which multiple teams contribute to a single application. You use branches to develop software in parallel in a version-controlled environment. For example, your team

  • Understanding continuous integration and delivery pipelines

    DevOps is a culture of collaboration by development, quality, and operations teams to address issues in their respective areas. To sustain progress and bring continued improvement, tools and processes are put in place. Use DevOps practices such as continuous integration and delivery (CI/CD) pipelines to break down code into pieces and automate testing tasks, so that multiple teams can work on the same features and achieve faster deployment to production.

  • Creating a toggle

    To enable or disable functionality that is under development, or to control access to a feature, create a toggle. When you create a toggle, a when rule for the toggle instance is created by default.

  • Optimizing application load time

    Improve the performance of your application by reducing content that is difficult to render. By running preflight optimization, you eliminate unnecessary static content and improve load times, which creates a better user experience.

  • Improving your compliance score

    Follow development best practices to improve your compliance score. By eliminating risks, such as custom code or degraded performance, you can improve quality and resolve issues before your application goes into production.

  • Unit testing individual rules

    An incorrect rule configuration in an application can cause delays in case processing. To avoid configuration errors such as incorrectly routed assignments, unit test individual rules as you develop them. To expedite future rules testing, you can create reusable test cases from the unit test.

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.