Tutorials
  • Welcome to Ozone
  • Quick Onboarding
    • Creating a New Project
    • Creating Environments
    • Adding a Registry
    • Adding a Repository
    • Attaching Clusters
    • Creating a Microservice
    • Using out-of-the-box Pipeline Templates
    • Creating a new pipeline on the Ozone Pipeline Studio
    • Configuring Triggers for Automated Deployments
    • Adding a CD Provider
      • Jenkins Pipeline
  • Documentation
    • Dashboard
      • Ozone Dashboard
      • Analyze Metrics & Logs for Kubernetes Clusters
    • CI/CD
      • Create Microservice
        • Link a Git Repo
        • Map a Registry
        • Map to Environments
        • Build Config (Specify where the Docker file exists)
      • Link Pipelines to your Microservice
        • Default Pipelines that are linked
        • What are Input Sets?
        • Execute a linked pipeline
      • Catalog
        • External Pipelines
          • Supported Integrations
          • How to Link an External CI Integration
          • Conversion Of external pipelines to Tekton Pipelines
        • Tasks
          • Create a Custom task
        • Releases (Templates and Runs)
          • What are releases composed of (Pipelines & Approvals)
          • Create a Release Template
          • Run a Release Template
        • Running Your First Pipeline
        • Pipelines (Templates & Runs)
          • Adding Nodes to Canvas
          • Configuring Rollbacks at Pipeline Template
          • Secret Injection + Secrets
          • Input-result mapping between tasks
        • Initiating Pipeline run
          • Manually
      • Triggers
        • Scheduling a pipeline and/or a release run
        • Triggering a pipeline and/or a release run
          • From Github events
          • From GitLab events
          • From Jira events
          • Custom Webhook
          • From Harbor events
          • From Azure DevOps events
          • From Bitbucket events
          • From Dockerhub events
      • Observe your Microservice
      • Verify Your Microservice With AI
    • Helm
      • Create a Helm Channel
      • Create a Helm Release
      • Edit a Helm Release
    • DevSecOps
      • Security Dashboard
      • Scans
      • Supported Integrations
      • Run Your First Security Pipeline
      • Shift Left Policy Management
        • Policies
    • Backups
      • Pre-requisites
      • How do I schedule a backup to create snapshots?
      • How to take snapshots and how do I know the status of backups?
      • How do I restore snapshots to clusters?
    • Setup
      • Manage Cluster
        • Public Cluster
        • Reattach Cluster
      • Setting up Environments
      • Manage Secret
      • Manage Repos
      • Manage Registries
      • Integrations
        • Managing Cloud Integrations
          • AWS
          • Azure
          • GCP
        • Managing Source Code Integrations
          • GitHub
          • GitLab
          • Bit bucket
          • Azure DevOps Repos
          • Git Repo
          • Bitbucket Datacenter
        • Managing Container Registry
          • Docker
          • GCR
          • Harbor
          • Quay
          • Azure ACR
          • Adhoc Registry
        • Managing Container Orchestration
          • AWS EKS
          • GKE
          • Azure AKS
        • Managing Issue Trackers
        • Managing Continuous Deployment
          • Argo CD
          • Azure DevOps
          • Ansible Tower
        • Managing SSO
        • Managing Private Catalogs
        • Managing Notifications
        • Managing Security
          • Snyk
          • Prisma Cloud
        • Managing APM
          • NewRelic
        • Managing Cloud Storage
          • Minio
          • AWS S3 Bucket
          • Google Cloud Storage
          • Azure Blob Storage
        • Managing Network Tunnels
        • Manage Testing
          • K6
        • Managing Secret Store
          • Azure Key Vault
          • Google Secret Manager
          • AWS Secrets Manager
          • Hashicorp Vault
    • Settings
      • Role Based Access Control
        • Create a new role
        • Clone an Existing Role
        • Apply a role to a member
      • Ozone Identity Management
      • Audit Trails
      • Private Cluster Management
      • SSO
        • Pre-Requisites
        • Azure AD
      • Projects
        • Create a new Project
        • Archive a Project
        • Import and remove resources into the project
        • Add Members to a Project
      • Setup Alerts and Notifications
  • Release Notes
    • August - 2024
    • July - 2024
    • June - 2024
    • April - 2024
    • February - 2024
    • November - 2023
    • October - 2023
    • September - 2023
    • August - 2023
    • July - 2023
    • June - 2023
    • May - 2023
    • April - 2023
    • September - 2022
    • August - 2022
    • July - 2022
    • May - 2022
    • April - 2022
    • Mar - 2022
    • Jan - 2022
    • Nov - 2021
  • FAQ
    • In House Applications
    • COTS Applications
    • Tasks
    • Pipelines
    • Releases
    • Projects
    • Members
    • Environments
    • Variables
    • Roles
  • Use Cases
    • For Platform Engineers
      • Standardized Application Delivery Workflows
      • Unified Observability and Alerting
      • On Demand Workload Recovery
    • For Software Developers
      • On Demand Delivery
      • Scalable and Re-usable Workflows
Powered by GitBook
On this page
  1. Documentation
  2. CI/CD
  3. Triggers
  4. Triggering a pipeline and/or a release run

Custom Webhook

PreviousFrom Jira eventsNextFrom Harbor events

Last updated 9 months ago

thatthatSuppose users want to create a webhook for custom use cases, like they want a pipeline or release to be triggered based on the options that they desire so what they can do is they can create a Generic webhook. This only requires a POST request to be sent on the URL provided and then the pipeline or release will be triggered. Steps to create a Generic Webhook for release

Pre-requisites:

  • An Active cluster

  • A Release that has been created from the Release Templates section

Steps

  1. On click of the create webhook button, a modal window appears in which we can enter the details for webhook creation

  1. After this select the webhook type as Generic

  1. After this select the release type as the release

4. After the trigger type release has been selected, select the release which needs to be triggered on the success of the POST request

  1. Once all the options are selected, the map parameters button will be enabled users can click on the button to move to the next step

  1. On moving to the next step, users can select the desired options for mapping the parameters. Once all the options are chosen users can click on save to create the Generic webhook.

  1. The webhook once created will be shown in the webhook list view

  1. To get the URL of the generic webhook that is created, click on the edit button of the webhook

Now we can use this URL for sending POST requests, after completion of any action we can send a POST request to this URL and the selected Release will be triggered.

Steps to create Generic Webhook for pipeline

Pre-requisites:

  • An Active cluster

  • A microservice

Follow the same steps until Step 2 of Creating Webhooks for release

Steps:

  1. Select the trigger type as pipeline

  1. Now select the pipeline that needs to be triggered

3. After selecting the pipeline, select the environment in which the webhook needs to be created

Remember to select the environment the same in which the cluster has been created 4. After selecting the environment, users will be shown an option to select the cluster

  1. Once the cluster has been selected, select the microservice

  1. After selecting the microservice, users can move to the Map parameters step, to select the run parameters for the pipeline

  1. In Map parameters, users can select all the options as they desire

  1. Once all this is done, users can click on the Save button to create the webhook for the pipeline

  1. The created webhook will be shown in the webhook list view

  1. To get the URL of the generic webhook that is created, click on the edit button of the webhook

Now we can use this URL for sending POST requests, after completion of any action we can send a POST request to this URL and the selected Release will be triggered.

This is how webhooks are created for Generic use cases, where we can just send a POST request to the URL and the desired pipeline/release will be triggered.