Benefits of integrating ServiceNow with Git

[dkhanna01]

Can someone explain me the benefits of integrating Git with Servicenow. We are considering   Git --> bitbucket --> JIRA --> Bamboo integration for our team development, now if we use this tools set, how ServiceNow will going to help.

[Chuck Tomasi]

Hi Deepak,

I can answer this. I presented this material several times last week at Knowledge 16.

The biggest benefit of the Git integration with ServiceNow is source code control of all application files on your dev instance. Tables, fields, ACLs, business rules, properties, etc. everything that is saved to the application record (and related update sets) is also available to commit to the repo. During sprints and releases you can use the branching and tagging feature to manage your release cycle.

Scenario: Production is running the April '16 release and you're half way through building features for the May '16 release when someone discovers a critical issue in production. Your May release is not ready and production cannot wait. You can quickly stash your work, flip to the April release, make and release the update, then go back to your May work.

This may help:

Source control integration

Ask the Expert: Source Control New Platform Feature in Helsinki, TechNow Ep26  

[Chuck Tomasi]

Here's another benefit based on what I read in the community... personal developer instances. You can use Git as an "offline storage" for your work in the event your instance goes away. Just get a new instance, link to the repo, and you're back in business with your original work in a few minutes. Way easier than exporting and importing update sets all over.

[dkhanna01]

Your answers does help .

Thanks

[stinky2nine]

Just to add that as far as I know, you can only use Git on scoped app. It does not currently work with global scope. You will have to continue using update sets (there is also Team Development).