Dear Open Hub Users,
We’re excited to announce that we will be moving the Open Hub Forum to
https://community.synopsys.com/s/black-duck-open-hub.
Beginning immediately, users can head over,
register,
get technical help and discuss issue pertinent to the Open Hub. Registered users can also subscribe to Open Hub announcements here.
On May 1, 2020, we will be freezing https://www.openhub.net/forums and users will not be able to create new discussions. If you have any questions and concerns, please email us at
[email protected]
Can you restart it?
Is it possible to allow users to manually restart a failed repository scan after a certain period of time? This way when a repository screws you won't have to intervene?
Hi zippy,
If a project fails, we usually automatically retry the job several times. If it requires manual intervention, it is often because of a fatal error for which a retry will not help.
In this case, we are seeing a fatal Subversion error:
$ svn checkout -r 3481 'svn://sharpdevelop.net/sharpdevelop/trunk/SharpDevelop@3481' --ignore-externals
svn: Can't open 'C:\WINDOWS\TEMP\report.tmp': Access is denied.
Any idea what this might be? Has it been fixed?
Robin,
Its been restarted. The temp file issue
seems to occur with other svn repos besides sharpdevelop, but I found no resolution from google.
I have two suggestions for these sorts of situations. The first is can you more verbosely report fatal enlistment errors on the site. The second is can you enable email or rss alerts for enlistment failures? It would reduce the need for your manual investigation, and be a good monitoring service for the projects on the site.
Regards,
Justin Dearing
Yeah, agreed, it would be great if the managers for a project could see these errors.