Linking GitLab and ServiceNow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā07-26-2018 12:34 PM
This page is the guide I'm following for source control configuration. I'm trying to link GitLab, but keep getting this error
I own the group and repo I am trying to link to, and created a personal access token with api access and used it as the password. I also tried using my regular GitLab password but that also failed. The group and project are both marked as Internal. Is there an extra step involved with GitLab that I am perhaps missing?
- Labels:
-
Integrations
-
Scoped App Development
-
Studio

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā08-17-2021 09:51 AM
Thanks for responding. Based on a recommendation from ServiceNow Support, we abandoned GitLab. We are now using GitHub. However, we are still experiencing intermittent issues. Sometimes it works and sometimes it does not work (without us making configuration changes). Do you think it might be something specific to our various applications? We've raised multiple cases with ServiceNow.
The current state of the issue for Github:
We have validated that the credentials are correct, and we have no issue logging into GitHub directly. Once logged into GitHub, we have both read and write access.
Example of Error:
com.glide.sourcecontrol.worker.git.GitWorkerHelper.initRepo(GitWorkerHelper.java:86) com.glide.sourcecontrol.worker.git.GitRefreshRepositoryWorker.refreshRepo(GitRefreshRepositoryWorker.java:84) com.glide.sourcecontrol.worker.RefreshRepositoryWorker.execute(RefreshRepositoryWorker.java:67) com.glide.sourcecontrol.SourceControlWorker.startWork(SourceControlWorker.java:41) com.glide.worker.AbstractProgressWorker.startAndWait(AbstractProgressWorker.java:126) com.glide.worker.HierarchicalProgressWorker.startAndWait(HierarchicalProgressWorker.java:35) com.glide.worker.BackgroundProgressJob.execute(BackgroundProgressJob.java:59) com.glide.schedule.JobExecutor.lambda$executeJob$0(JobExecutor.java:115) com.glide.schedule.JobExecutor.executeJob(JobExecutor.java:118) com.glide.schedule.JobExecutor.execute(JobExecutor.java:102) com.glide.schedule_v2.SchedulerWorkerThread.executeJob(SchedulerWorkerThread.java:300) com.glide.schedule_v2.SchedulerWorkerThread.lambda$process$0(SchedulerWorkerThread.java:188) com.glide.worker.TransactionalWorkerThread.executeInTransaction(TransactionalWorkerThread.java:35) com.glide.schedule_v2.SchedulerWorkerThread.process(SchedulerWorkerThread.java:188) com.glide.schedule_v2.SchedulerWorkerThread.run(SchedulerWorkerThread.java:102) |
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā08-19-2021 05:26 AM
GitHub recently made a change that requires you to use an access token instead of your password when authenticating through an API. Here is some information on how to create a personal access token. Once you have the token, you will use the token in place of your GitHub password in ServiceNow.
I hope this helps.
Ben
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā04-29-2024 04:46 PM
Thanks! Using an access token with my personal account in an Oauth Basic authentication solved that problem for me!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā09-21-2021 08:55 AM