Update Sets Deployment or convert the Global application into git using now-sdk and DevOps Tools

[VamsiRajuPeetha]

Hi Everyone,

Could you please suggest me a better solution or approach for automating the Deployment of update sets using DevOps tools such as Gitlab, Git as source control and some orchestration tools if possible?

As we rely much on the Global application and as we cannot convert the Global application into source control code using now-sdk, we are looking for some better alternatives to achieve the Deployment automation.

[ersureshbe]

Hi,

My perception and experience in landscape - The scoped application github plays significant role but global application. Update set movement use servicenow platform capability. Please use below link to understand.

https://www.youtube.com/watch?v=MSz-y8F29qg

https://www.youtube.com/watch?v=pct5iyXhnQc

i) Update Set vs. GitHub Repository: Considering the complexity of your project involving new tables, service catalogs, KB articles, and various configurations, I recommend using a GitHub repository. Git provides a robust version control system, allowing you to manage changes efficiently and collaborate seamlessly. By using GitHub, you can maintain different branches for different features, ensuring a well-organized development process.

ii) Organization of Update Sets: If you opt for an update set, it's advisable to split changes logically. Create separate update sets for different scopes such as Service Catalog, Now-Mobile changes, flows, etc. This approach enhances clarity, making it easier to manage and track changes related to specific components of your application.

iii) General Differences between Update Sets and GitHub:

• Update Sets: These are specific to the ServiceNow platform and are used for capturing and moving configuration changes between instances. Update sets are efficient for ServiceNow-specific configurations.
• GitHub Repository: GitHub is a version control system widely used for collaborative software development. It provides a centralized location for your code, enabling versioning, collaboration, and easier management of complex projects. Unlike update sets, GitHub offers a broader range of version control features and is not limited to ServiceNow configurations.

iv) Additional Considerations:

• Regularly commit your changes to the GitHub repository to maintain a comprehensive version history.
• Clearly document your commits and changes made in each branch, making it easier for collaborators to understand the progress.
• Consider setting up a Continuous Integration (CI) pipeline to automate the testing process, ensuring code quality and stability.

I hope this guidance helps you in making an informed decision for your development process. If you have further questions or need more specific advice, please feel free to ask. Best of luck with your project, and I hope the development process goes smoothly for you. Explore the difference between GitHub vs Git.