Dear Open Hub Users,
We’re excited to announce that we will be moving the Open Hub Forum to
https://community.blackduck.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]
Hi,
could you please have a look while code locations listed at https://www.ohloh.net/p/magnolia/enlistments aren't checked for updates? It seems like last fetch happened 7 months ago and it's not been checked ever since.
Thanks,
Jan
Jan,
Needed to re-evaluate two enlistments which finished OK (12415 and 416 total commits) about 8 hours ago.
Also noted that one enlistment modules/workflow
has gone missing since the last update. Deleted that enlistment. A full update started immediately and also finished OK (415 and 1 or no added commits respectively). Analysis is now at July 25, 2013 on code collected on July 25, 2013 and last commit is at July 24, 2013 - about 18 hours ago.
Please be sure you remind me here if the project stalls again.
Thanks!
Superb, thanks a lot for fixing the problem. And yeah, the workflow is gone now. Does it mean I need to watch enlistments closely and make sure I fix them asap when some location changes or it would stop again updating stats on whole project?
Additionally, is there a way to set somewhere in configuration of a project to get notified in case of some analysis issues?
Thanks again,
Jan
Jan,
Yes, you'll need to revisit enlistments as regularly as you can to keep the data updated. Unfortunately, there's no way. currently, to notify managers if there's a hiccup in processing (you probably wouldn't want to know every time because we take care of a number of issues automatically - the less distractions the better.) But once the update date Analyzed blah ago based on code collected blah ago
gets too out-of-date then it's time to call for help. No analysis will be done if any enlistment is in failure. The problem is it's currently impossible for a manager to determine the type of failure that's present. You could fix some of them like the missing repository issue if you only knew about it more specifically. We are exploring this without giving you a lot of unneeded useless detail. It will take a while to implement and since it is an enhancement, it takes a back seat to bug fixes, as it should.
Thanks!
All right, that's fine.
Thanks for explanation. I'll try to keep an eye on those enlistments (just realized there's number of them missing anyway) and will check analysis & collection dates regularly.
Cheers,
Jan