This repository has been archived by the owner on Aug 13, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 12
Add webhook support #59
Comments
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 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.
This was referenced Oct 20, 2016
This was referenced Oct 25, 2016
This was referenced Nov 18, 2016
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Emit following webhooks as self-describing JSONs:
The text was updated successfully, but these errors were encountered: