Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

add a new notification type : URL

#225

Hi,

it would be great to have a new type of notification to do an HTTP POST on one (or more) URL(s) after a job execution success/failure (same as the email notification)
I'm thinking about something similar to what github does with "post-receive hooks" : http://help.github.com/post-receive-hooks/

I've got 2 use-cases for that :

  • kind of a "callback" for external systems that triggers job execution (typically the jenkins plugin, so that I could add the execution status on a jenkins build)

  • integration with an external monitoring system, to graph the success/failure executions

Thanks

Reported by Vincent Behar · March 8th, 2011 @ 05:17 AM

State: new
Milestone: none
Assigned to: nobody

Activity

  1. Greg Schueler
    Greg Schueler
    • Tag set to interop, notification, webhook
    • Milestone set to Rundeck 1.3
    • Assigned user set to Greg Schueler
    • Milestone order changed from 17 to 0

    Some more thoughts:

    The URL should have token expansion, so ${execution.id} will be replaced by execution ID, etc. Other properties: ${job.[name,group,id,project]}, ${execution.[id,status,user]}

    March 9th, 2011 @ 03:26 PM

  2. Deleted User
  3. Greg Schueler
    Greg Schueler
    • State changed from new to open

    March 17th, 2011 @ 02:59 PM

  4. Alex-SF
    Alex-SF

    A webhook executed at job begin would also be useful.

    March 21st, 2011 @ 07:46 AM

  5. Greg Schueler
    Greg Schueler
    • State changed from open to needs_verification
    • Milestone order changed from 2 to 0

    webhook (or other notification) at job begin i guess would be another type of notification...perhaps that should be another ticket

    June 3rd, 2011 @ 04:32 PM

  6. Alex-SF
    Alex-SF

    Verified the functionality but errors in service.log do not include timestamp:

    Unable to POST notification after 1 tries: success for execution 253 (succeeded) to http://localhost:8000/bleeps/bleep?email_from=alex@dtosolutions.com...: Error making request: Connection refused

    See #335 Define log format with timestamp for service.log

    June 8th, 2011 @ 09:24 AM

  7. Alex-SF
    Alex-SF
    • State changed from needs_verification to open

    June 8th, 2011 @ 10:11 AM

  8. Alex-SF
    Alex-SF
    • Tag changed from interop, notification, webhook to feature request, interop, notification, webhook

    June 8th, 2011 @ 11:45 AM

  9. Deleted User
  10. Deleted User
  11. Greg Schueler
    Greg Schueler
    • State changed from needs_verification to resolved

    verified that logging includes timestamp.

    verified that webhook URL can include variable expansion.

    updated ${job.id} to default to use uuid if present.

    July 7th, 2011 @ 07:12 PM

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.