Catlee suggested that we should get a development instance of AUS3 going such that folks with build network access can point their Firefoxes at it. The AUS code itself is pretty much ready for this. Here's a rough list of what I think we need to do to make this happen: - Get a VM for it - Figure out how to get snippets onto the machine (A few possible option: have pushsnip & the nightly snippet cronjob push them there; mount the snippet partition read-only on the AUS3 VM; push snippets to it from Buildbot) - Teach the snippet importer how to create -Nightly release blobs - Possibly teach the snippet importer how to update rules. Or we could update rules manually (since they only need updating for release/beta channel changes, generally). Most of this work will be tracked in dependent bugs.

(In reply to Ben Hearsum [:bhearsum] from comment #0) > - Teach the snippet importer how to create -Nightly release blobs And by this, I mean that we need something that knows how to insert the blobs that generate-json.py generates into an existing databases, both updating a -Nightly or -Latest row, and creating a new one for the dated version.

This is a modified version of the one I've been using on dev-master01 that allows for site-specific things to be passed in. It also doesn't do an rsync, because when the dev environment is fully up, we'll have the snippets available on a read-only mount. I purposely left PRODUCT/VERSION/BRANCH hardcoded so that we've got the ability to update them without IT intervention. We could also expand the script to multiple products/branches if needed.

I'm declaring this done. The environment is up, automatically pulling new versions of the code. The cronjob is in place and importing snippets every day. There's improvements to be made later, namely: running the admin.wsgi app and having the build machines submit information directly to it -- but that will be tracked elsewhere, when it's ready.