Incomplete Build

A build is marked as Incomplete in the Build History when the CI pipeline finished but CodeNOW could not fully process the build. There are two possible causes:

1. Missing Required Results

The CI pipeline did not produce all result events required by the resource type. Each resource type defines its own set of required results — for example:

• Runtime components (application components) require container, helm, and git-tag
• Containers require container and git-tag
• Libraries require git-tag and a package registry result (maven, npm, or nuget depending on the technology)

info

The exact required results for each resource type are documented on the respective resource documentation page.

How to Resolve

1. Open the Build Detail to see which results were registered and which are missing
2. Fix the pipeline to ensure all required results are sent
3. Trigger a new build

tip

For CodeNOW CI (Tekton), the default pipelines handle all required results automatically. Missing results are most common when using Custom CI or customized pipelines.

2. Failed Default Configuration Processing

For runtime components, CodeNOW processes the default deployment configuration after a successful build. If this processing fails, the build is marked as Incomplete.

How to Resolve

When this happens, a Retry action appears next to the incomplete build in the Build History. Click Retry to re-attempt processing the default configuration — there is no need to re-run the entire pipeline.