deployment issue with github
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-06-2025 04:52 AM - edited ‎05-06-2025 04:57 AM
I have issue with servicenow when publishing app to app repo and this happened recently after specific upgrade that as been done one year ago and we tried to fix it but with no success, so briefly the issue is; we have 4 environment of servicenow for my company dev, test, stag and prod, dev is for development and initial test integrated with github for deployment so in dev we do the development in a local update set and then push and commit those changes to github repo, then test env. is for testing and publishing the scoped app to app repo in servicenow so in test we pull the changes from github repo by applying from remote in studio then after success test we create a new version of app package using publish to app repo to be available for stag and prod env. to be installed.
so before the upgrade we only push a commit to github repo from dev environment but after upgrade test changes its behaviour and push a new commit to the github repo when we publish to app repo ! so i tried to do a workaround to continue our work but I need to fix this issue so can you please help me to sort this out
this is the upgrade that cause the issue
glide-washingtondc patch1-hotfix2a
let me know if you need more clarification
- Labels:
-
Deployment
-
Upgrades
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-12-2025 08:45 AM
for who may face the same issue like me I can show you what is the work around that I did
I create a read token in the test environment for the github repo and for the dev I use the read and write token but before it was the same token with read and write
so please if someone from servicenow expert can help me know why it has been changed since the patch i have provided above