- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-13-2022 05:14 AM
Hello Community,
When trying to commit to Git from within Studio, I'm getting this error:
Error occurred while exporting application : com.glide.sourcecontrol.SourceControlException: org.eclipse.jgit.errors.RepositoryNotFoundException: repository not found: /glide/nodes/****_****/webapps/glide/itil/WEB-INF/update/git/*********: com.glide.sourcecontrol.AGitRepository.loadGit(AGitRepository.java:234)
com.glide.sourcecontrol.worker.git.GitWorkerHelper.initRepo(GitWorkerHelper.java:90)
com.glide.sourcecontrol.worker.git.GitExportApplicationWorker.exportApp(GitExportApplicationWorker.java:161)
com.glide.sourcecontrol.worker.ExportApplicationWorker.execute(ExportApplicationWorker.java:132)
com.glide.sourcecontrol.SourceControlWorker.startWork(SourceControlWorker.java:41)
com.glide.worker.AbstractProgressWorker.startAndWait(AbstractProgressWorker.java:126)
com.glide.worker.HierarchicalProgressWorker.startAndWait(HierarchicalProgressWorker.java:26)
com.glide.worker.BackgroundProgressJob.execute(BackgroundProgressJob.java:59)
com.glide.schedule.JobExecutor.lambda$executeJob$0(JobExecutor.java:129)
com.glide.schedule.JobExecutor.executeJob(JobExecutor.java:132)
com.glide.schedule.JobExecutor.execute(JobExecutor.java:116)
com.glide.schedule_v2.SchedulerWorkerThread.executeJob(SchedulerWorkerThread.java:338)
com.glide.schedule_v2.SchedulerWorkerThread.lambda$process$0(SchedulerWorkerThread.java:220)
com.glide.worker.TransactionalWorkerThread.executeInTransaction(TransactionalWorkerThread.java:35)
com.glide.schedule_v2.SchedulerWorkerThread.process(SchedulerWorkerThread.java:220)
com.glide.schedule_v2.SchedulerWorkerThread.run(SchedulerWorkerThread.java:101)
It might be a coincidence, but maybe it's related to a recent upgrade to San Diego. At the time of the upgrade however it didn't come to mind to check Studio. Contacting the repo didn't work either. But I could make it work again by entering the password again. So now it's able to contact the repo. The commit however does not work.
A clue is maybe that I can't publish the application to our repository from within Studio. But it works to open the app's record and use the publish link there. As suggested in another post.
Is there anyone having an idea of what's going on and what I can try to fix this ?
THX !
Solved! Go to Solution.
- Labels:
-
Scoped App Development
-
Studio
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-05-2022 05:48 AM
Apparently is was an issue due to the upgrade to San Diego. Something about empty directories for the Git repositories. Servicenow fixed the issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-05-2022 05:48 AM
Apparently is was an issue due to the upgrade to San Diego. Something about empty directories for the Git repositories. Servicenow fixed the issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-19-2022 07:43 AM
Do you know when / how it was fixed? Getting the same error on SD Patch 4.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-19-2022 11:59 PM
I think they manually fixed it, because we opened a support case to have them look to it. So it's not part of an update of some kind. Which reminds me - that's why yesterday I couldn't commit anymore either ! I thought somebody here messed up.
Anyway, I signaled the issue and they quickly found the issue. Which I will do again.