Github integration

AnasuyaRampall
Tera Contributor

Hello 

 

I have done two academic projects in ServiceNow. I made two applications in Studio and linked to source control which is my github repository. It was a good learning. However, I began to wonder: ServiceNow has update sets which are pretty versatile. So, why even use github? What I really want to know, is this: How does it happen in the real world? Do most organizations develop scoped applications in Studio and link to source control? or do they simply start an update set and do it on the platform in global scope?

 

I'd appreciate all and any insight and advice.

 

Thank you for stopping by.

 

Best regards

Anu

3 REPLIES 3

Community Alums
Not applicable

From my POV it's a mixed bag - most implementations I still see are update sets only, but newer implementations tend to be scoped applications with an attached code repository. ServiceNow itself pushes more and more for the scoped application and code repository model.

But it is not a distinction between a code repository and update sets as the code repository will still hold update sets, it's more of a question how will you distribute and deploy your solution: As an application from a repository or (half-)manually via update sets.

I'd add that the maturity level and size of the organization plays a big role. Enterprises with compliance requirements often mandate source control, while smaller implementations may stick with update sets for simplicity. The real benefit comes with multi-developer teams where update set conflicts become painful - that's usually when organizations make the switch to source control.

Hi @Community Alums 

Thank you for your response. 

I understand and agree.

 

I will continue to practice both scoped applications in studio and working in global scope on my instance.  Will surely help wherever I end up.

How is it in your organization, though? Do you make a lot of scopped applications? Or do you work on global?