mozilla
/
treeherder
зеркало из https://github.com/mozilla/treeherder.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
treeherder/Procfile

11 строки
1.4 KiB
Plaintext
Исходник Обычный вид История

Bug 1197186 - Move wsgi.py to a generic config/ directory Since it's not specific to the Django app 'webapp'.
2015-10-08 16:21:17 +03:00
web: newrelic-admin run-program gunicorn treeherder.config.wsgi:application --log-file - --timeout 29 --max-requests 2000
Bug 1145606 - Setup treeherder to deploy on heroku I added a Procfile listing all the different python services treeherder needs. Heroku provides deployment-specific settings via environment variables, so I had to modify the settings file to listen to them where that wasn't the case. I created an enviroment variable IS_HEROKU which allows to have a heroku-only configuration where needed. The db service is provided by Amazon RDS, which requires a ssl connection. To enable ssl in the MySQLdb python client I had to modify Datasource (and bump up the version used). The cache service is provided by the memcachier heroku addon. Heroku recommends to use pylibmc, so I set it up according to the docs here https://devcenter.heroku.com/articles/memcachier#python. The amqp service is provided by the CloudAMQP addon. I added a post_compile script that runs every time we deploy. We should run every build step we require in there, like static asset minification, collection, etc. To share the oauth credentials among the various services I used an environment variable. I also added an option to export_project_credentials so that the credentials can be printed to stdout. This should come handy when we will need to update the environment-stored credentials with the ones in the db.
2015-05-01 13:01:11 +03:00
worker_beat: newrelic-admin run-program celery -A treeherder beat
worker_pushlog: newrelic-admin run-program celery -A treeherder worker -Q pushlog,fetch_missing_push_logs --maxtasksperchild=500 --concurrency=5
Bug 1164868 - Split the buildapi tasks into {pending,running,4hr} queues Previously all three of the buildapi ETL ingestion tasks (pending, running, 4hr) were run under one queue. In order to be able to tell issues (such as backlogs or leaks) apart, these have now been split onto their own queues. On Heroku, these queues now also have a dyno each - which should mean we can easily tell which is leaking and possibly also downgrade from the expensive performance dyno even before the leak is fixed.
2015-05-21 17:44:58 +03:00
worker_buildapi_pending: newrelic-admin run-program celery -A treeherder worker -Q buildapi_pending --maxtasksperchild=20 --concurrency=5
worker_buildapi_running: newrelic-admin run-program celery -A treeherder worker -Q buildapi_running --maxtasksperchild=20 --concurrency=5
Bug 1164888 - Tune Heroku build4hr handling By taking the concurrency down to 1, we can control how much memory is used and increase throughput by assigning more dynos. This prevents us overflowing the memory allocations on each dyno due to the growth of the build4hr process.
2015-06-17 21:19:51 +03:00
worker_buildapi_4hr: newrelic-admin run-program celery -A treeherder worker -Q buildapi_4hr --maxtasksperchild=20 --concurrency=1
Bug 1228154 - Generate new performance alerts as data is ingested
2015-12-02 21:00:45 +03:00
worker_default: newrelic-admin run-program celery -A treeherder worker -Q default,cycle_data,calculate_durations,fetch_bugs,fetch_allthethings,generate_perf_alerts --maxtasksperchild=50 --concurrency=3
Bug 1145606 - Setup treeherder to deploy on heroku I added a Procfile listing all the different python services treeherder needs. Heroku provides deployment-specific settings via environment variables, so I had to modify the settings file to listen to them where that wasn't the case. I created an enviroment variable IS_HEROKU which allows to have a heroku-only configuration where needed. The db service is provided by Amazon RDS, which requires a ssl connection. To enable ssl in the MySQLdb python client I had to modify Datasource (and bump up the version used). The cache service is provided by the memcachier heroku addon. Heroku recommends to use pylibmc, so I set it up according to the docs here https://devcenter.heroku.com/articles/memcachier#python. The amqp service is provided by the CloudAMQP addon. I added a post_compile script that runs every time we deploy. We should run every build step we require in there, like static asset minification, collection, etc. To share the oauth credentials among the various services I used an environment variable. I also added an option to export_project_credentials so that the credentials can be printed to stdout. This should come handy when we will need to update the environment-stored credentials with the ones in the db.
2015-05-01 13:01:11 +03:00
worker_hp: newrelic-admin run-program celery -A treeherder worker -Q classification_mirroring,publish_to_pulse --maxtasksperchild=50 --concurrency=1
Bug 1237474 - add error_summary and store_error_summary tasks to Heroku procfile
2016-01-07 04:26:59 +03:00
worker_log_parser: newrelic-admin run-program celery -A treeherder worker -Q log_parser_fail,log_parser,log_parser_hp,log_parser_json,error_summary,store_error_summary --maxtasksperchild=50 --concurrency=5
Bug 1245472 - Heroku: Update to the new release-phase implementation The beta release-phase feature is making a backwards incompatible change today - moving from an app.json (and corresponding buildpack) approach to specifying a `release` Procfile entry that blocks the app deploy. For more info, see: https://devcenter.heroku.com/articles/release-phase?preview=1
2016-02-03 15:33:54 +03:00
release: ./manage.py migrate --noinput && ./manage.py load_initial_data && ./manage.py init_datasources