What is the best practice for multiple-instance developing on ServiceNow ?

[Duong Vu]

Hello everyone,

My team and I have just started learning ServiceNow for a new project. So far I have done everything in the training course and this platform is quite promising. But since this project requires multiple developers working at the same time, i wonder how should we control the source version if each developer working on his/her own dev instance ?

I have been searching for a while and there are some approaches to this problem:

- Everyone working on a same instance. Make sure their works don't overlap.

- Link the application to Git. This seems to be quite straight forward but only non-global application can be linked.

- Export update sets from dev instances and merge into main instance.

This project requires working on both global scope (customize incident, problem, etc) and custom application (specific requirements) so i am really confused which way should we tackle the problem. 

I would love to hear some best practices in this case from you guys.

Thanks in advance !

[Jon Barnes]

you can also use team development (plugin) which will allow developers to develop in their own instances and then can allow them to be code reviewed and pulled into the main DEV instance/merged there. I haven't used it much, but you could look around at that to see if it fits your needs.

https://docs.servicenow.com/bundle/kingston-application-development/page/build/team-development/conc...

[Christophe_E]

Hello,

To people that consult this post, please be aware of following:

(Source: ServiceNow Development Pipeline Management Guide)

"

Note: ServiceNow also offers a feature called Team Development. Team Development was implemented to support such a use case but is no longer actively developed. While it is still fully supported, we do not recommend customers
to start using Team Development. Please consider using the newer Source Control Integration capabilities which also addresses this scenario.

"