Difference between revisions of "Running hound on Infra"
m |
|||
Line 7: | Line 7: | ||
EXTRA_SKILLS=Go| | EXTRA_SKILLS=Go| | ||
MENTORS=Elizabeth K. Joseph (pleia2), Jeremy Stanley (fungi), Jonathan Harker (jesusaurus)| | MENTORS=Elizabeth K. Joseph (pleia2), Jeremy Stanley (fungi), Jonathan Harker (jesusaurus)| | ||
− | STATUS= | + | STATUS=Completed by Taron(Emma) for Outreachy May 2015| |
PROGRAM=Outreach May-Aug 2015 | PROGRAM=Outreach May-Aug 2015 | ||
}} | }} |
Latest revision as of 18:32, 9 December 2015
Implement livegrep service for Infra
Running a livegrep service to search for code across OpenStack git repositories
Difficulty | Low |
Topics | Infra |
Required skills | Puppet, Ruby |
Extra skills | Go |
Mentor | Elizabeth K. Joseph (pleia2), Jeremy Stanley (fungi), Jonathan Harker (jesusaurus) |
Status | Completed by Taron(Emma) for Outreachy May 2015 |
Program | Outreach May-Aug 2015 |
Run livegrep in infra: https://review.openstack.org/#/c/96877/ https://review.openstack.org/#/c/129726/ (actually Monty had suggested to me to run Hound instead, as it is able to update the index for the git repos which livegrep doesnt': https://github.com/etsy/hound) but either way a grep service (yah - hound is like a 5 minute task - would be a great first task for someone) setting up hound is a 5 minute task, writing the parser to parse the yaml files so it knows which repos to index might take longer than 5 minutes