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 schedule for a release
  • Steps to create a schedule for a pipeline
  1. Documentation
  2. CI/CD
  3. Triggers

Scheduling a pipeline and/or a release run

PreviousTriggersNextTriggering a pipeline and/or a release run

Last updated 9 months ago

Imagine you want to trigger a release or a pipeline in frequent intervals say every hour, every day at a particular hour, or at a particular day in a week, Instead of going and doing it manually, users can create a Schedule for the particular use case they want according to their requirements for a release or a pipeline.

Steps to create a schedule for a release

Pre-requisites:

  • An Active cluster

  • A Release created from Release Templates

Steps:

  1. Once you log in to Ozone, select Triggers on the left-side bar.

  2. After clicking on triggers a modal appears to select between Schedules and Webhooks Click on Schedules to get the schedules page

  3. After this users can click on the Create Schedule button to open the modal window for schedule creation

  4. This will open the modal window for schedule creation

  5. Users are provided options to select the frequency, Hourly - The release/pipeline will be triggered every hour, you need to enter the minutes on when to trigger the release/pipeline

    Daily - Release/Pipeline will be triggered daily, you just need to enter the hours and minutes when they want to trigger the Release and Pipeline

    Weekly - You can select the day of the week and the time on that particular day when they want to trigger the Release or Pipeline. You need to select the day and enter the hours and minutes

    Open image-20240416-090835.png

  6. Once the frequency is selected you can select the Resource type as Release

    Open image-20240416-091042.png

  7. After selecting the Resource type as Release, an option will be provided to select the release template to choose the release template as desired. After all the details are entered and the release is selected, users can click on map parameters to move to the second step of schedule creation

    Open image-20240416-091435.png

  8. Once all the details are entered, users can click on Save to create the schedule.

    Open image-20240416-091532.png

  9. Once the Schedule has been successfully created it will be shown in the form of a tabular list, in the below way. In the table list view, you can see that the next run is visible and when next will the release will be triggered.

    Open image-20240416-091616.png

    Users can click on the edit button, to edit the schedules Users can click on the toggle button, to enable/disable schedules Users can click on the delete button, to delete the schedules.

Steps to create a schedule for a pipeline

Pre-requisites:

  • An Active cluster

  • Microservice

  • Select the same environment in which the cluster has been created

Steps:

  1. Follow the same steps as schedule creation for release, i.e. from step 1 - to step 6

  2. Once this is done, select the resource type as pipeline

  3. Now select the details for the following- - Select the pipeline name, i.e. the pipeline that needs to be triggered - Next, select the environment, the environment should be the same in which the cluster has been created - Select the microservice - Select the cluster Once all these details are entered click on the map parameters to move to the next step

  4. The next step is to map parameters for the particular pipeline and enter the details as requested in the input run parameters. Once all the details have been entered, click on Save to create the schedule. The schedule created will be shown in the table list view as it was shown above while creating a release schedule.

Open image-20240416-091715.png

Open image-20240416-091808.png

Open image-20240416-091842.png