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
  • Steps to create a Github Webhook for release
  • Steps to create webhook for pipeline
  1. Documentation
  2. CI/CD
  3. Triggers
  4. Triggering a pipeline and/or a release run

From Github events

PreviousTriggering a pipeline and/or a release runNextFrom GitLab events

Last updated 9 months ago

Suppose you want to trigger a pipeline or release on a successful PR merge on GitHub or when a code is pushed to a particular branch, they can create a webhook using the webhook type as GitHub.

Steps to create a Github Webhook for release

Pre-requisites:

  • An active GitHub account with repositories needs to have the PAT(Personal Access Token) which can be entered while creating GitHub integrations

  • 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 you can enter the details for webhook creation

  1. Now we need to select the Webhook Type as Github from the Webhook Type dropdown

  1. After selecting the webhook type as Github, a dropdown will be shown to select the repository for which the webhook needs to be created

  1. Once the repository has been selected, users have the option to select the event for which they want the pipeline or release to be triggered Ozone offers 2 events for which webhooks can be created: - Push branch - whenever code is pushed to the specified branch the webhook is triggered - Pull request - whenever a pull request is merged at that point the webhook will be triggered

  1. After selecting the event, users are provided an option to select the branch for the repository for which they want the webhook to be triggered

  1. Once the branch has been selected, the next option is provided for the users to select as to whether they want to trigger a release or a pipeline on the successful happening of the event that they had selected

Here we will select the option of Release

  1. After this users can select the release which they want to be triggered

  1. Once every option has been selected the map parameters option will be enabled and users can click on it to move to the next step

9. After going to the second step users can choose the input run parameters, once all these options have been selected, users can click on the save button to create the webhook

  1. Once the webhook has been created, it will be shown in the tabular list view

Here you can see it shows when was the webhook last triggered, as well as we can enable/disable the webhook from the tabular list, and we can click on the edit icon to edit the webhook.

Steps to create webhook for pipeline

Pre-requisites:

  • An Active cluster

  • A microservice

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

Steps:

  1. Once the repository name and the branches have been selected select the trigger type as Pipeline

  1. Once the Trigger type has been selected, now select the pipeline that needs to be triggered

  1. 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

  1. After selecting the environment, users will be shown an option to select the cluster

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

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

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

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

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

Users can click on the edit icon to edit the webhook, and click on the toggle button to enable/disable the webhook.

Hurray 🥳This is how you can create the webhooks for GitHub to trigger a release or a pipeline.