Add support for Triggering a build Pipeline in GitLab from spinnaker
Problem to solve
Some of our customers use Spinnaker for their CD solution, we can integrate with Spinnaker and make their life easier.
This process is already documented in * https://blog.opsmx.com/triggering-build-pipeline-in-gitlab-from-spinnaker/
Use case is users who used GitLab CI but Spinnaker CD.
Add documentation for Triggering a build Pipeline in GitLab from spinnaker. But also create a webhook based on the instructions from the blog:
** Configure a GitLab Custom Webhook Stage**
Custom Webhook Stages provide a simple, yet powerful, way of adding custom stages to Spinnaker. These stages are typically used to make quick API calls to an external system as part of a pipeline. Instead of extending the various components through code, users can simply add configuration to Orca for these stages. They appear in the UI as if they were a native stage.
3.1. Creating a Custom Webhook Stage
To create a custom webhook stage, we need to add configuration for the stage in ‘orca-local.yml’ available at ‘/opt/orca/config/’. The ‘webhook.preconfigured’ property supports configuring multiple webhook stages.
3.2. Configuring parameters for Custom Webhook Stage
We can also configure parameters for Custom Webhook Stages. These Custom webhook parameters allow variables to be used within the custom stages. These parameters are rendered in the UI and let users of your stage set them as necessary. When the stage executes, the values of these parameters are evaluated using SpEL which means that they can be dynamic in nature. Add the following configuration in ‘orca-local.yml’ to create a custom webhook stage with parameters: Given name for the stage: GitLab – GitLab Custom Webhook Parameters used in Webhook URL are: Project ID and GL Webhook Token for my GitLab project-id and token resp.
Permissions and Security
What does success look like, and how can we measure that?
Number of people using the new webhook
Sales able to demonstrate this cabability