On Openshift, custom plugin repository builds need to be triggered from Studio at the right moment in order to identify when a Studio change breaks a build.
Ideally, when a build fails on a CI system, the user needs to be able to identify the point at which the build occurred (in the Studio dev flow) and what changes broke the build. The second point will be handled in a second scope.
High Level To Do:
Allow the user to configure a web trigger that is executed when a new save is done on a specific branch. With a properly configured web trigger, it starts automatically a build on Openshift that has dependency on the Studio project.
The user is allowed to set a preference for when the web trigger occurs:
- Commit (excluding wip branches)
Moreover, ensure the trigger identifies as many elements of
- Any other identifier
The user is able to navigate to an history page that lets him identify if the web trigger has been correctly delivered. In case of issue, he is able to identify what happened, and replay the failed event.
For a first iteration; we are going to focus the interaction to Openshift only as target CI environment.