I imagine a lot of the Gooey triggered functionality in Jenkins will run entirely inside Jenkins (creating jobs etc) with the job doing it just triggered by Gooey via REST API or something similar.
Need to prepare for this so Gooey can be configured to hit an arbitrary spot in Jenkins and pass parameters.
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/2583329-allow-gooey-to-interact-with-jenkins-to-create-a-new-module-job?utm_campaign=plugin&utm_content=tracker%2F983091&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F983091&utm_medium=issues&utm_source=github).
I imagine a lot of the Gooey triggered functionality in Jenkins will run entirely inside Jenkins (creating jobs etc) with the job doing it just triggered by Gooey via REST API or something similar.
Need to prepare for this so Gooey can be configured to hit an arbitrary spot in Jenkins and pass parameters.
Some inspiration: https://wiki.jenkins-ci.org/display/JENKINS/Remote+access+API https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Remote+Trigger+Plugin
Related: #5 and others