Bug 1272481 - [RFE]Allow passing of parameters via Generic Webhooks
[RFE]Allow passing of parameters via Generic Webhooks
Product: OpenShift Origin
Classification: Red Hat
Component: Build (Show other bugs)
All All
unspecified Severity high
: ---
: ---
Assigned To: Cesar Wong
Wenjing Zheng
: UpcomingRelease
Depends On:
  Show dependency treegraph
Reported: 2015-10-16 09:48 EDT by Dave McCormick
Modified: 2015-10-26 15:29 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-10-26 15:29:05 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Dave McCormick 2015-10-16 09:48:59 EDT
Description of problem:

We wish to use an STI or custom builder to assemble images for Java applications that have already been built and their artefacts uploaded to a repository, such as Nexus.  I don't want to use openshift to perform the whole build from source, where we have an existing CI platform doing this work well. I want the openshift build to be triggered by a generic webhook from our CI server and do job of packaging the built artefacts into a docker container.

When triggering the build, we would like to pass the build version as a parameter (perhaps on the call URL or in the json of the payload) so that the assemble script can use this to locate the application in the repository, e.g.: -


If I could pass a parameter 'version' with the value '2.0.19' to my assemble script then I have all the information I need to download the artefacts into our customised tomcat container.

Version-Release number of selected component (if applicable): Openshift Enterprise

How reproducible:
Feature does not exist.

Actual results:
Feature does not exist.

Expected results:
Allow something like this: -
http://<openshift_api_host:port>/osapi/v1/namespaces/<namespace>/buildconfigs/<name>/webhooks/<secret>/generic?param1=value1&param2=value2 etc..

Or allow parameters to be defined in the webhook payload
  "type": "Generic",
  "generic": {
    "secret": "secret101"
  "parameters":  [
   { "name": "param1", "value": "value1"},
   { "name": "param2", "value": "value2"}

Each parameter is added as environment variable when starting the builder container. e.g.


Additional info:
Comment 1 Ben Parees 2015-10-26 15:29:05 EDT
converted this to a trello card on our backlog:

Note You need to log in before you can comment on or make changes to this bug.