Skip to main content

Continuous Integration Events

CodeNOW processes events from CI pipelines to track build progress and results. Events are sent to the CodeNOW webhook endpoint and allow CodeNOW to display build status, logs, and artifacts in the Build History. Events are divided into three types:

#Event TypeDescription
1Start EventIndicates the start of a pipeline execution
2Result EventReports results of individual pipeline steps
3End EventReports the final outcome of the pipeline

Event Flow​

Events must be sent in the following order:

  1. Start Event — informs CodeNOW which pipeline was executed on which resource
  2. Result Event — reports the outcomes of individual steps (can be sent multiple times)
  3. End Event — reports the final result of the entire pipeline
info

For first-class CI providers (such as CodeNOW CI and GitHub Actions), the start event is triggered automatically by CodeNOW. You only need to implement events manually when using Custom CI.

Authentication​

All events are sent to the CodeNOW Webhook Receiver and must be authenticated using a CI Key passed in the X-Codenow-Api-Key header. You can generate a CI Key in Continuous Integration Keys.

caution

Each CI Key is bound to a single resource (component or library). It cannot be reused across multiple resources.

Webhook Endpoint​

All events are sent as POST requests to:

https://api.cloud.codenow.com/ci/webhook

With the following headers:

Accept: application/vnd.codenow.v1+json
Content-Type: application/vnd.codenow.v1+json
X-Codenow-Api-Key: {YOUR_CI_KEY}