Skip to main content

Custom CI

Custom CI allows you to integrate any external CI system (e.g. Jenkins, GitLab CI, Azure DevOps) with CodeNOW.

How It Works​

Unlike the first-class providers (CodeNOW CI and GitHub Actions), custom CI integration is event-based. Your external CI system sends CI events to CodeNOW's webhook endpoint to report build progress and results. The event flow consists of three steps:

  1. Start Event — signal that a pipeline has started
  2. Result Events — report individual step outcomes (container image, Helm chart, code quality, etc.)
  3. End Event — report the final pipeline result (successful, failed, or canceled)

CodeNOW receives these events and displays the build progress and results in the Build History alongside builds from other providers.

Getting Started​

  1. Switch the resource to Custom CI via CI Provider & Global Configuration
  2. Generate a CI key to authenticate event requests
  3. Configure your external CI pipeline to send events to the CodeNOW webhook endpoint

Use Cases​

  • You already have an established CI/CD infrastructure and want to keep using it
  • Your build process requires specialized tooling not available in CodeNOW CI or GitHub Actions
  • You need to integrate with an on-premises CI system