ServiceNow Expeditions #19 - Protecting the work with GitHub Repo скачать в хорошем качестве

ServiceNow Expeditions #19 - Protecting the work with GitHub Repo

This episode is a comprehensive guide to integrating ServiceNow with GitHub to safeguard your development work, particularly when using Personal Developer Instances (PDIs). Join the ServiceNow crew as they transition from the legacy Studio to the modern development experience, demonstrating how to establish a robust source control connection. You’ll learn the step-by-step process of configuring a GitHub repository, generating fine-grained Personal Access Tokens, setting up Basic Authentication credentials in the ServiceNow platform, and successfully linking your application. The team also dives into the nuances of the "name-based" update set system that replaces traditional update sets once a Git connection is active, and how to perform your first commit to ensure your progress is never lost. ✳ 𝐓𝐀𝐊𝐄𝐀𝐖𝐀𝐘𝐒 ✳ PDI Data Safety: Personal Developer Instances (PDIs) are provided free of charge but can be reclaimed by ServiceNow after 10 days of inactivity or reset without formal warning. Using a Git repository is the only reliable way to back up and store application data on a PDI. GitHub Integration Process: To connect ServiceNow to GitHub, you must create a blank repository, generate a Personal Access Token (PAT) with "Read and Write" permissions for contents and metadata, and then create a corresponding Basic Authentication credential record within the ServiceNow platform. Automated Update Set Management: Once an application is linked to source control, ServiceNow automatically manages "name-based" update sets for each developer. These act as a local repository, and you should never manually close, rename, or delete them to avoid damaging the application structure. Commit & Push Workflow: Instead of manually moving update sets between instances, developers use the "Commit Changes" feature. This allows you to select specific artifacts, leave a meaningful comment (such as a story number), and push the updates directly to the remote GitHub repository. Collaborative Development Nuances: In ServiceNow, all developers on a single instance might work on the same active branch. When committing changes, the system displays all modified artifacts from all developers, requiring careful selection to ensure only intended updates are pushed. Connection Troubleshooting: Configuration details for source control are stored in the sys_repo_config table. In rare cases of "checkout" conflicts - such as when a Flow becomes locked- deleting and recreating the repository configuration from this table may be necessary to resolve the issue. ✳ 𝐂𝐇𝐀𝐏𝐓𝐄𝐑𝐒 ✳ 0:00 - Intro 01:25 - Topic introduction 03:03 - Showing the legacy Studio IDE option 03:54 - Switching to the new ServiceNow Studio 04:50 - Creating a new repository in GitHub 07:25 - Creating an access token for the GitHub repository 10:30 - Creating a credential in ServiceNow and linking the app 13:00 - Inspecting the GitHub repository after the commit 13:34 - Discussing Update sets after linking an app to a repository 15:55 - Testing an additional commit to the repository 18:51 - Looking at the updated data in GitHub 20:30 - Disconnecting an app from a repository 22:35 - Risks, odd-cases when a repository gets out of sync 24:22 - Wrapping up ✳ 𝐑𝐄𝐅𝐄𝐑𝐄𝐍𝐂𝐄 ✳ SN Utils - https://www.arnoudkooi.com/ ✳ *𝐃𝐈𝐒𝐂𝐋𝐀𝐈𝐌𝐄𝐑* ✳ This video is for educational purposes only. Information is provided as-is without any warranty of accuracy or completeness. Use of this information is at your own risk. We do not hold rights to third-party materials used under fair use for educational objectives. We are not liable for any loss or damage arising from your actions based on the content of this video.