Contents Now Platform Custom Business Applications Previous Topic Next Topic Instance hierarchies Subscribe Log in to subscribe to topics and get notified when content changes. ... SAVE AS PDF Selected Topic Topic & Subtopics All Topics in Contents Share Instance hierarchies Team Development allows you to set up a distributed version control system between multiple ServiceNow instances where each instance acts as a source repository, or branch. Developers use separate instances to work on different features, applications, or product releases at the same time. With Team Development, developers can share code between these instances and resolve collisions throughout the development process. Team Development allows you to establish hierarchical relationships between instances and provides a mechanism for transferring changes between instances that integrates with the Update Set process where necessary. In a Team Development instance hierarchy, each non-production instance has a parent instance. Instances that have the same parent instance are peer instances. The shared parent instance becomes the central hub, or repository, and all peer instances synchronize to it. Related TasksTeam Development processRelated ConceptsTeam Development overviewTeam Development setupCode reviewsCode review notificationsCode review workflowExclusion policiesPulls and pushesTeam Development rolesVersionsVersions and local changes On this page Send Feedback Previous Topic Next Topic
Instance hierarchies Team Development allows you to set up a distributed version control system between multiple ServiceNow instances where each instance acts as a source repository, or branch. Developers use separate instances to work on different features, applications, or product releases at the same time. With Team Development, developers can share code between these instances and resolve collisions throughout the development process. Team Development allows you to establish hierarchical relationships between instances and provides a mechanism for transferring changes between instances that integrates with the Update Set process where necessary. In a Team Development instance hierarchy, each non-production instance has a parent instance. Instances that have the same parent instance are peer instances. The shared parent instance becomes the central hub, or repository, and all peer instances synchronize to it. Related TasksTeam Development processRelated ConceptsTeam Development overviewTeam Development setupCode reviewsCode review notificationsCode review workflowExclusion policiesPulls and pushesTeam Development rolesVersionsVersions and local changes
Instance hierarchies Team Development allows you to set up a distributed version control system between multiple ServiceNow instances where each instance acts as a source repository, or branch. Developers use separate instances to work on different features, applications, or product releases at the same time. With Team Development, developers can share code between these instances and resolve collisions throughout the development process. Team Development allows you to establish hierarchical relationships between instances and provides a mechanism for transferring changes between instances that integrates with the Update Set process where necessary. In a Team Development instance hierarchy, each non-production instance has a parent instance. Instances that have the same parent instance are peer instances. The shared parent instance becomes the central hub, or repository, and all peer instances synchronize to it. Related TasksTeam Development processRelated ConceptsTeam Development overviewTeam Development setupCode reviewsCode review notificationsCode review workflowExclusion policiesPulls and pushesTeam Development rolesVersionsVersions and local changes