What is the most compatible Version Control tool for ServiceNow?

[david_hreben]

I am in need of using a version control application for a development team in ServiceNow. I have found that Git is compatible with ServiceNow but it is limited to using Studio. Is Jgit a better option? Has anybody used it successfully. Any information would be appreciated.

[Chuck Tomasi]

Hi David,

Currently (as of Helsinki, released in spring 2016) ServiceNow source control supports Git based source control systems via Studio.

Source control integration

Can you provide additional details of what you are looking for beyond what we currently provide?

Common questions include:

Q: Can we use source control with global apps?

A: No, because source control requires old objects (tables, properties, ACLs) to be removed when switching branches. If this were done in global, it could render your system unusable.

Q: Can we use source control repos from a hosted SN instance to a private Git repo?

A: Currently source control does not work through a MID server to repos behind a firewall.

Thanks.

[david_hreben]

We are looking to do set up an environment in order to do Code Versioning, Code Review and testing automations. I have been told that "Team Development" works as well as Git. Would you happen to know about it?

The Tools am trying to use with ServiceNow are: Bamboo, Crucible, Either Git or Team Dev, and FishEye.

[Chuck Tomasi · Accepted solution]

Team Development was originally designed to allow multiple developers on multiple dev instances work together. It is not a formal version control system as it doesn't provide for tags, branches, etc. that a traditional version control system would. What's more Team Development is targeted for global scope changes and the direction of development is scoped apps. As a result, Team Development will be receiving no additional investment from ServiceNow product development.

[david_hreben]

Thanks Chuck! That was very helpful.