Skip to content

Guard Build job JSON parsing#2260

Open
kiwigitops wants to merge 1 commit into
microsoft:mainfrom
kiwigitops:fix-empty-build-order-condition
Open

Guard Build job JSON parsing#2260
kiwigitops wants to merge 1 commit into
microsoft:mainfrom
kiwigitops:fix-empty-build-order-condition

Conversation

@kiwigitops
Copy link
Copy Markdown

Summary

  • guard Build job conditions before parsing needs.Initialization.outputs.buildOrderJson
  • apply the same guard in generated multi-depth Build jobs
  • update both template CICD workflows

Closes #2258.

Testing

  • git diff --check

Copilot AI review requested due to automatic review settings May 20, 2026 19:11
@kiwigitops kiwigitops requested a review from a team as a code owner May 20, 2026 19:11
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR addresses a GitHub Actions workflow failure where the Build job’s if: condition attempted to fromJson() an empty needs.Initialization.outputs.buildOrderJson, causing CI/CD to error and skip Build.

Changes:

  • Guarded the Build job if: condition in both template CI/CD workflows to ensure buildOrderJson is non-empty before calling fromJson(...).
  • Applied the same guard to the if: conditions generated for multi-depth Build jobs in ModifyBuildWorkflows.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File Description
Templates/Per Tenant Extension/.github/workflows/CICD.yaml Adds a non-empty buildOrderJson guard before fromJson(...) in the Build job condition.
Templates/AppSource App/.github/workflows/CICD.yaml Adds the same non-empty buildOrderJson guard before fromJson(...) in the Build job condition.
Actions/CheckForUpdates/CheckForUpdates.HelperFunctions.ps1 Updates multi-depth Build job condition generation to include the same guard.

if: (!failure()) && (!cancelled()) && needs.Initialization.outputs.buildOrderJson != '' && fromJson(needs.Initialization.outputs.buildOrderJson)[0].projectsCount > 0
strategy:
matrix:
include: ${{ fromJson(needs.Initialization.outputs.buildOrderJson)[0].buildDimensions }}
if: (!failure()) && (!cancelled()) && needs.Initialization.outputs.buildOrderJson != '' && fromJson(needs.Initialization.outputs.buildOrderJson)[0].projectsCount > 0
strategy:
matrix:
include: ${{ fromJson(needs.Initialization.outputs.buildOrderJson)[0].buildDimensions }}
Comment on lines +189 to +201
# Example (depth 1):
# needs: [ Initialization ]
# if: (!failure()) && (!cancelled()) && fromJson(needs.Initialization.outputs.buildOrderJson)[0].projectsCount > 0
$if = "if: (!failure()) && (!cancelled()) && fromJson(needs.Initialization.outputs.buildOrderJson)[$index].projectsCount > 0"
# if: (!failure()) && (!cancelled()) && needs.Initialization.outputs.buildOrderJson != '' && fromJson(needs.Initialization.outputs.buildOrderJson)[0].projectsCount > 0
$if = "if: (!failure()) && (!cancelled()) && needs.Initialization.outputs.buildOrderJson != '' && fromJson(needs.Initialization.outputs.buildOrderJson)[$index].projectsCount > 0"
}
else {
# Subsequent build jobs needs to have a dependency on all previous build jobs
# Example (depth 2):
# needs: [ Initialization, Build1 ]
# if: (!failure()) && (!cancelled()) && (needs.Build1.result == 'success' || needs.Build1.result == 'skipped') && fromJson(needs.Initialization.outputs.buildOrderJson)[0].projectsCount > 0
# if: (!failure()) && (!cancelled()) && (needs.Build1.result == 'success' || needs.Build1.result == 'skipped') && needs.Initialization.outputs.buildOrderJson != '' && fromJson(needs.Initialization.outputs.buildOrderJson)[0].projectsCount > 0
# Another example (depth 3):
# needs: [ Initialization, Build2, Build1 ]
# if: (!failure()) && (!cancelled()) && (needs.Build2.result == 'success' || needs.Build2.result == 'skipped') && (needs.Build1.result == 'success' || needs.Build1.result == 'skipped') && fromJson(needs.Initialization.outputs.buildOrderJson)[0].projectsCount > 0
# if: (!failure()) && (!cancelled()) && (needs.Build2.result == 'success' || needs.Build2.result == 'skipped') && (needs.Build1.result == 'success' || needs.Build1.result == 'skipped') && needs.Initialization.outputs.buildOrderJson != '' && fromJson(needs.Initialization.outputs.buildOrderJson)[0].projectsCount > 0
@kiwigitops kiwigitops force-pushed the fix-empty-build-order-condition branch from 3972fd2 to 1283d72 Compare May 21, 2026 01:44
@kiwigitops
Copy link
Copy Markdown
Author

Updated the other template Build conditions with the same guard and fixed the generated workflow examples to use the matching build-order index.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: Build in CICD is skipped because of the json error parsing

2 participants