How do we connect a new ServiceNow instance to ADO Repository for my cusotm app movement
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-24-2023 11:50 PM
Hi,
We have a new instance and client wants us to connect the new instance to ADO repo so that the cusotm apps that were developed in other instances can be easily moved through the ADO Repo into the new instance.
Could someone assist me with the setps to configure ADO Repo on a fresh instance for the same client ?
Many Thanks,
Dhruv
1 REPLY 1
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-13-2024 08:17 PM
Steps to Configure ADO Repo on a Fresh Instance
1. Prerequisites
- Access to ADO Repo: Ensure you have the repository URL and necessary credentials (PAT - Personal Access Token or access permissions).
- Studio Access: Ensure you can access the ServiceNow Studio on the new instance.
- Repository Branch Info: Confirm the branch where custom apps are stored in ADO.
2. Enable Source Control in the Instance
- Log in to ServiceNow:
- Use an account with admin rights.
- Go to System Applications:
- Navigate to System Applications > Studio.
- Open the Application:
- If no application exists, create a new placeholder application for connecting to the repo.
3. Connect the Application to ADO Repo
- In Studio, open the application.
- Click on Source Control in the top-right menu.
- Select Link to Source Control.
4. Configure the Repository
- Fill in Repository Details:
- Repository URL: Enter the ADO repo URL (e.g., https://dev.azure.com/{organization}/{project}/_git/{repository}).
- Branch Name: Specify the branch (e.g., main or dev).
- Authentication:
- Use a Personal Access Token (PAT) to authenticate. Create a PAT in ADO with necessary permissions for the repository (code read/write).
- Review and confirm the setup.
5. Pull Applications from the Repository
- After linking, the system will check for existing changes.
- Choose to Import Repository Changes if the ADO repo contains the custom apps.
- Resolve any merge conflicts (if applicable).
6. Validate and Test the Connection
- Verify that all custom applications are pulled into the new instance.
- Test the functionality of the apps to ensure proper import.
7. Optional: Automate Deployments
- Set up CI/CD pipelines in ADO for automated deployments using the ServiceNow DevOps Integration plugin.
- This involves configuring pipelines in ADO and mapping them to the ServiceNow instance for automated testing and deployments.
Additional Resources
- Azure DevOps Personal Access Token Setup:
- Refer to Azure DevOps Documentation for creating PATs.
- ServiceNow Source Control Documentation:
- Visit ServiceNow Docs for detailed steps on linking to source control.