How do I customize the structure of response?

[Bpazy]

Similar to #113 .

My purpose is to return the following payload (docker hub webhook expected response):

{
  "state": "success",
  "description": "387 tests PASSED",
  "context": "Continuous integration by Acme CI",
  "target_url": "http://ci.acme.com/results/afd339c1c3d27"
}

But the response structure of this plugin does not seem to be customizable. Are there any related tutorials or development plans?

[tomasbjerre]

So not a static custom response but something that is dynamic. Something that can be sent after the build is completed.

No such feature is implemented. PR:s are welcome but I think this would be hard to do, if possible.

[caquino]

Regarding the response payload, I see it contains an url field pointing to the /queue/item/<id>. Is it possible if quiet-period is set to 0 that, instead of returning the queue URL to respond with the url for the job like /job/<job_name>/<id>?

This would allow me to log the job URL on the system triggering the webhook to simplify troubleshooting.

[tomasbjerre]

Dont you have all the things you need to construct the URL yourself?

{"jobs":{"refjob":{"regexpFilterExpression":"","triggered":true,"resolvedVariables":{"ref":""},"regexpFilterText":"","id":1,"url":"queue/item/1/"}},"message":"Triggered jobs."}

[caquino]

First of all, thanks for such a quick response!

Maybe I'm missing something here, so feel free to correct me if my understanding is incorrect, but to be able to map from /queue/item/1/ to a JOB URL, it would require the webhook originator system to issue another request to Jenkins to query the/queue/item/1/api/{xml,json} endpoint and retrieve the job information.

This is not a problem, but still, it would require extra logic on the webhook source system, another request to Jenkins, and also credentials for that system to access the /queue/item/1/api/{xml,json}, which sadly is not viable for us.