604123 - Store crontabs in git

Status: RESOLVED WONTFIX

(Input :: General, defect, P2)

Comment 1

[Dave Dash [:davedash, :dd] (assign all bugs to mbrandt)]

oremj,

Can you list the crontabs we have in prod and staging for Input here?

I want to store them in our git repo, like we do with AMO.

Comment 2

[Fred Wenzel [:wenzel]]

The crons we currently have are:

----

MAILTO="[e-mail]"
# cron for input, Bug 572502
*/5 * * * * root (cd /data/www/input.stage.mozilla.com/reporter/; ./bin/update_staging.sh) > /dev/null
#*/5 * * * * root /usr/local/bin/django_updater.sh --vendor /data/www/input.stage.mozilla.com/reporter > /dev/null
#*/10 * * * * root cd /data/www/input.stage.mozilla.com/reporter && ( /data/virtualenvs/input/bin/schematic migrations > /dev/null ) && ( /data/virtualenvs/input/bin/schematic migrations/sites > /dev/null )
*/30 * * * * apache /data/virtualenvs/input/bin/python26 /data/www/input.stage.mozilla.com/reporter/manage.py update_product_details &> /dev/null
# cron cluster needs to run once an hour because the database can potentially be updated
# from production at :30 on any given hour (depending when backups finish) and it needs to
# be run immediately after a database import.
35 * * * * apache /data/virtualenvs/input/bin/python26 /data/www/input.stage.mozilla.com/reporter/manage.py cron cluster &> /dev/null
# removing as per fwenzel's advice. Not needed for stage.
#*/20 * * * * apache /data/virtualenvs/input/bin/python26 /data/www/input.stage.mozilla.com/reporter/manage.py update_index

----

People receiving the cron-input list are currently davedash, ryansnyder, and I.

Comment 3

[Dave Dash [:davedash, :dd] (assign all bugs to mbrandt)]

Moving to Future, but many of these will land in 4.x

Comment 4

[Will Kahn-Greene [:willkg] ET needinfo? me]

This isn't relevant to the new Input. Marking WONTFIX.