How to manage version control if a rollback is required?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
6 hours ago
hello servicenow community,
i am looking for guidance on best practices for managing version control when a rollback is required. if i deploy the release of version x.2, but then encounter an issue and am required to rollback to version x.1, how do i manage the release of x.2?
i have searched through much of the documentation, the community, and the f.a.q. and could not find much information on this topic. can you provide any insights and best practices?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago - last edited an hour ago
Hi @simonboisve
If X.2 is rolled back, don’t reuse the X.2 version.
Keep X.2 in the release history, fix the issue, and create X.3:
X.1 > X.2 > rollback to X.1 > fix > X.3
This keeps the deployment history clear and traceable.
This helps other users find accurate and useful information more easily
