LinkedIn
Copied!

Table of Contents

Understanding development best practices working in a shared environment

Version:

Only available versions of this content are shown in the dropdown

Development environments can be shared by one or more teams collaborating on the production application. To practice continuous integration, use a team application layer, branches, and release toggles.

  • Build a team application layer that is built on top of the main production application. The team application layer contains branches, tests, and other development rulesets that are not intended to go into production. For more information, see Using multiple built-on applications.
  • Create a branch of your production ruleset in the team application. For more information, see Adding development branches to your application.
  • Optional: Use release toggles to disable features that are not ready for general use. Using toggles allows you to merge branch content frequently even if some content is not final. For more information, see Toggling features on and off.
  • Optional: Create formal review tasks for other members of the development team to review your content. For more information, see Creating a branch review.
  • Optional: Use the branch developer tools to review the content and quality of your branch. For more information, see Reviewing branches.
  • Optional: Lock the branch. For more information, see Locking a branch.
  • Frequently merge the branch from the team application layer to the production rulesets. For more information, see Merging branches into target rulesets.

No more than two or three scrum teams should share a development environment to improve version control stability.

Have a question? Get answers now.

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