xethorn / garcon

95%

master: 95%

LAST BUILD ON BRANCH add-version

branch: add-version

CHANGE BRANCH

x

Reset

• add-version
• 0.0.1
• 0.0.2a1
• 0.0.2a10
• 0.0.2a2
• 0.0.2a4
• 0.0.2a5
• 0.0.2a6
• 0.0.2a7
• 0.0.2a8
• 0.0.2a9
• 0.0.4
• 0.0.5
• 0.0.6
• 0.0.7
• 0.1.0
• 0.2.0
• 0.2.1
• 0.2.2
• 0.2.3
• 0.3.0
• 0.3.1
• 0.3.2
• 0.4.0
• 0.4.1
• add-context
• add-error-handler
• add-param
• boto2
• branch-1.0
• master
• mo-14-dec-add-tests
• mo-14-jan-add-input-as-part-of-context
• mo-15-add-context
• mo-15-april-add-task-runner
• mo-15-feb-add-contextify
• mo-15-feb-add-instance-and-generator
• mo-15-feb-add-run
• mo-15-feb-add-task-runner
• mo-15-feb-fix-yield
• mo-15-jan-add-timeouts
• mo-15-june-add-state
• mo-15-march-add-workflow
• mo-15-march-remove-activity
• mo-15-may-add-support-for-external
• mo-16-april-add
• mo-17-august-add-example-of-full-decider
• mo-apply-pep8
• xethorn-handle-activity-failures
• xethorn-patch-1
• xethorn/20-june-1.0.1
• xethorn/20-june-add-support-for-running-tests-on-pull-requests
• xethorn/20-june-bump-version
• xethorn/20-june-bump-version-1
• xethorn/20-may-add-github-workflows
• xethorn/20-may-add-workflow-to-publish-to-github
• xethorn/20-may-create-alpha-release
• xethorn/20-may-issue-0.4.1
• xethorn/20-may-issue-1.0.0a2
• xethorn/20-may-remove-python27
• xethorn/2021/may/add-codeql
• xethorn/21-may-update-readme

Build # 297

Build Type

push

travis-ci

Committed by xethorn

Commit Message

Add support for manual deciders.

Some flows are more complex than others. For instance: some activities can
be scheduled based on a condition in the context. Being able to (easily)
write the decider has a lot of advantages.

For this: in your flow, you need to define a decider method that takes a
`schedule` param. To call an activity, all you have to do is to call
`schedule`, provide an immutable id, the activity and a list (if necessary)
of requirements. Example:

```python
def decider(schedule):
    activity_1 = schedule(
        'activity_1', test_activity_1)
    activity_2 = schedule(
        'activity_2', test_activity_2, requires=[activity_1])

    for i in range(3):
        activity_3 = schedule(
            'activity-3.{}'.format(i), test_activity_3, requires=[activity_2])

        if activity_3.ready and activity_2.result.get('4') == 4:
            last_activity = schedule(
                'last_activity.{}'.format(i), test_activity_last,
                input=dict(the='end'))
```

Remember: the decider is called anytime you have an event has occurred. So this
method should only be focused on scheduling (and nothing else).

@rantonmattei

Run Details

534 of 562 relevant lines covered (95.02%)

1.9 hits per line