DeveloperPlaybook/best-practices/howto_readme.md needs how-to for gemnasium, coveralls etc.?
Closed this issue · 8 comments
I'm looking for additional information on how to enable gemnasium and coveralls for any DLSS project. Because these are additional online services, it's not obvious to me how we add a DLSS project to these services. For example, what 'user' account is used for these services? (If it's a developer's own account, how are they added to a DLSS 'group' (if it exists), and what, if anything, happens during staff turnover etc.) Would someone qualified like to add this information to the playbook or point me in the right direction if it's already available?
BTW, I know we're trying to prefer PRs over issues, but this can't be a PR and this seems like the best venue for the issue (as opposed to dlss dev list) because it's specifically about the playbook info.
I think that you need to have @sul-devops-team register your app with Gemnasium
https://consul.stanford.edu/display/dlssdevops/How+to+track+and+manage+application+dependencies
For Coveralls, I have followed this guide to adding them into the apps I work on:
https://coveralls.zendesk.com/hc/en-us/articles/201769485-Ruby-Rails
Also, you'll probably want to add a Service to your repository so that it informs Gemnasium when you've updated so it will re-evaluate your Gemfile.lock.
This is particularly useful when you're using the Gemnasium badge on your README otherwise it will be stale.
Service Setup Example: https://github.com/sul-dlss/sul-requests/settings/hooks
Meta: 👍 to raising issues for shared requirements that aren't in the playbook!
See PR #44 as a first attempt to include the core of these comments in the how-to.
Closing.