Changeset View
Changeset View
Standalone View
Standalone View
docs/index.rst
Show First 20 Lines • Show All 138 Lines • ▼ Show 20 Lines | Task 169800445 | ||||
Policy: recurring | Policy: recurring | ||||
Status: next_run_not_scheduled | Status: next_run_not_scheduled | ||||
Priority: | Priority: | ||||
Args: | Args: | ||||
'https://bitbucket.org/lunixbochs/pypy-1' | 'https://bitbucket.org/lunixbochs/pypy-1' | ||||
Keyword args: | Keyword args: | ||||
Writing a new worker for a new swh-task-type | |||||
-------------------------------------------- | |||||
When you want to add a new swh-task-type, you need a celery worker backend | |||||
capable of executing this new task-type instances. | |||||
Celery workers for swh-scheduler based tasks should be started using the Celery | |||||
app in `swh.scheduler.celery_config`. This later, among other things, provides | |||||
a loading mechanism for task types based on pkg_resources declared plugins under | |||||
the `[swh.workers]` entry point. | |||||
TODO: add a fully working example of a dumb task. | |||||
Reference Documentation | Reference Documentation | ||||
----------------------- | ----------------------- | ||||
.. toctree:: | .. toctree:: | ||||
:maxdepth: 2 | :maxdepth: 2 | ||||
/apidoc/swh.scheduler | /apidoc/swh.scheduler |