Skip to content
This repository has been archived by the owner on Aug 13, 2024. It is now read-only.

Add webhook support #59

Closed
alexanderdean opened this issue Aug 22, 2016 · 0 comments
Closed

Add webhook support #59

alexanderdean opened this issue Aug 22, 2016 · 0 comments
Assignees
Milestone

Comments

@alexanderdean
Copy link
Contributor

alexanderdean commented Aug 22, 2016

Emit following webhooks as self-describing JSONs:

  1. Task complete, for every task finishing, whether successful or failed (or no-op)
  2. DAG complete, whether successful or failed
@alexanderdean alexanderdean added this to the Version 0.3.0 milestone Aug 22, 2016
@alexanderdean alexanderdean changed the title Placeholder for webhook support Add webhook support Sep 23, 2016
ninjabear added a commit that referenced this issue Sep 29, 2016
This also does a lot of refactoring, primarily around decoupling
execution strategies from actual execution. This includes adding
a layer over a dag to model which tasks can be run together,
and keep a log of which tasks have been run. This puts the foundation
down for #59 and #61.
ninjabear added a commit that referenced this issue Sep 30, 2016
This also does a lot of refactoring, primarily around decoupling
execution strategies from actual execution. This includes adding
a layer over a dag to model which tasks can be run together,
and keep a log of which tasks have been run. This puts the foundation
down for #59 and #61.
ninjabear added a commit that referenced this issue Oct 10, 2016
Using the option --webhook <url> Factotum will post status updates
to the given url. These include the current run-state of the job,
failures, skipped tasks etc.
ninjabear added a commit that referenced this issue Oct 10, 2016
ninjabear added a commit that referenced this issue Oct 10, 2016
ninjabear added a commit that referenced this issue Oct 10, 2016
ninjabear added a commit that referenced this issue Oct 10, 2016
ninjabear added a commit that referenced this issue Oct 10, 2016
ninjabear added a commit that referenced this issue Oct 10, 2016
ninjabear added a commit that referenced this issue Oct 10, 2016
ninjabear added a commit that referenced this issue Oct 10, 2016
Using the option --webhook <url> Factotum will post status updates
to the given url. These include the current run-state of the job,
failures, skipped tasks etc.
ninjabear added a commit that referenced this issue Oct 10, 2016
Using the option --webhook <url> Factotum will post status updates
to the given url. These include the current run-state of the job,
failures, skipped tasks etc.
ninjabear added a commit that referenced this issue Oct 10, 2016
Using the option --webhook <url> Factotum will post status updates
to the given url. These include the current run-state of the job,
failures, skipped tasks etc.
ninjabear added a commit that referenced this issue Oct 10, 2016
Using the option --webhook <url> Factotum will post status updates
to the given url. These include the current run-state of the job,
failures, skipped tasks etc.
ninjabear added a commit that referenced this issue Oct 11, 2016
Using the option --webhook <url> Factotum will post status updates
to the given url. These include the current run-state of the job,
failures, skipped tasks etc.
ninjabear added a commit that referenced this issue Oct 11, 2016
Using the option --webhook <url> Factotum will post status updates
to the given url. These include the current run-state of the job,
failures, skipped tasks etc.
@ninjabear ninjabear removed their assignment Oct 21, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants