![]() |
4 weeks ago | |
---|---|---|
doc | 3 months ago | |
releasenotes | 2 months ago | |
taskflow | 2 months ago | |
tools | 1 year ago | |
.coveragerc | 8 years ago | |
.gitignore | 3 years ago | |
.gitreview | 4 years ago | |
.mailmap | 10 years ago | |
.pre-commit-config.yaml | 2 years ago | |
.stestr.conf | 5 years ago | |
.zuul.yaml | 1 year ago | |
CONTRIBUTING.rst | 2 years ago | |
LICENSE | 10 years ago | |
README.rst | 4 years ago | |
bindep.txt | 4 years ago | |
pylintrc | 8 years ago | |
requirements.txt | 1 year ago | |
run_tests.sh | 10 years ago | |
setup.cfg | 4 weeks ago | |
setup.py | 6 years ago | |
test-requirements.txt | 2 years ago | |
tox.ini | 1 year ago |
README.rst
Team and repository tags
TaskFlow
A library to do [jobs, tasks, flows] in a highly available, easy to understand and declarative manner (and more!) to be used with OpenStack and other projects.
- Free software: Apache license
- Documentation: https://docs.openstack.org/taskflow/latest/
- Source: https://opendev.org/openstack/taskflow
- Bugs: https://bugs.launchpad.net/taskflow/
- Release notes: https://docs.openstack.org/releasenotes/taskflow/
Join us
Testing and requirements
Requirements
Because this project has many optional (pluggable) parts like persistence backends and engines, we decided to split our requirements into two parts: - things that are absolutely required (you can't use the project without them) are put into requirements.txt
. The requirements that are required by some optional part of this project (you can use the project without them) are put into our test-requirements.txt
file (so that we can still test the optional functionality works as expected). If you want to use the feature in question (eventlet or the worker based engine that uses kombu or the sqlalchemy persistence backend or jobboards which have an implementation built using kazoo ...), you should add that requirement(s) to your project or environment.
Tox.ini
Our tox.ini
file describes several test environments that allow to test TaskFlow with different python versions and sets of requirements installed. Please refer to the tox documentation to understand how to make these test environments work for you.
Developer documentation
We also have sphinx documentation in docs/source
.
To build it, run:
$ python setup.py build_sphinx