New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 738173 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner: ----
Closed: Aug 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: ----



Sign in to add a comment

Make local Sheriff-o-Matic easier to get up and running

Project Member Reported by zhangtiff@chromium.org, Jun 29 2017

Issue description

Bev's been trying to do a few small changes to Sheriff-o-Matic and found it a bit confusing to get the app going. 

Between things like having to get service account credentials, having to add trees to your local instance, and having to figure out how to populate the server with alerts, it's rather confusing to get a local version of Sheriff-o-Matic set up. 

Maybe we should store some sort of local JSON dump of sample Sheriff-o-Matic data and add a make populate command or something of the like to handle things like adding trees, bug queue labels, etc. The cron analyzers are an improvement over what we used to do to locally populate alerts though the /cron tab in the App Engine local console doesn't see to actually be able to find the crons + you need service account credentials to run the cron. (I feel like, ideally, you should be able to get a basic local copy of Sheriff-o-Matic running without service account credentials.)

It would also help to make sure the README is up to date. 
 
The devserver admin page is pretty sad. AFAICT it pretty much only knows about the default module (nee service).

To deal with cron analyzers, we could make a dev-mode-only page that has buttons to run each.
Mergedinto: 755886
Status: Duplicate (was: Untriaged)

Sign in to add a comment