Skip to content

Skip Deliver and Deploy when no app artifacts exist#2129

Draft
Copilot wants to merge 12 commits intomainfrom
copilot/fix-deliver-to-blob-storage
Draft

Skip Deliver and Deploy when no app artifacts exist#2129
Copilot wants to merge 12 commits intomainfrom
copilot/fix-deliver-to-blob-storage

Conversation

Copy link
Contributor

Copilot AI commented Feb 16, 2026

❔What, Why & How

This pull request improves the CI/CD workflow for both AppSource App and Per Tenant Extension templates by ensuring that the Deploy and Deliver actions are only executed when app artifacts are present. This prevents errors that could occur on initial commits or when no artifacts are generated.

Workflow improvements for artifact handling:

  • Added a conditional check (if: hashFiles('.artifacts/**/*.app') != '') to the Deploy step in Templates/AppSource App/.github/workflows/CICD.yaml and Templates/Per Tenant Extension/.github/workflows/CICD.yaml to skip deployment when no .app artifacts are found.
  • Added the same conditional check to the Deliver step in both workflow files to skip delivery when no artifacts are present.
  • Added notice steps that display informative messages when Deploy or Deliver steps are skipped due to no app artifacts:
    • "Deployment to environment [name] was skipped because no app artifacts were found"
    • "Delivery to [target] was skipped because no app artifacts were found"

Documentation update:

  • Updated RELEASENOTES.md to document that Deliver and Deploy actions now skip execution when no app artifacts are found, preventing errors on initial commits.

✅ Checklist

  • Add tests (E2E, unit tests)
  • Update RELEASENOTES.md
  • Update documentation (e.g. for new settings or scenarios)
  • Add telemetry

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Co-authored-by: mazhelez <43066499+mazhelez@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix deliver to blob storage failure on initial commit Fix: Skip delivery when no app artifacts exist Feb 16, 2026
Copilot AI requested a review from mazhelez February 16, 2026 09:34
Copilot AI and others added 2 commits February 16, 2026 13:32
Co-authored-by: mazhelez <43066499+mazhelez@users.noreply.github.com>
Co-authored-by: mazhelez <43066499+mazhelez@users.noreply.github.com>
Copilot AI changed the title Fix: Skip delivery when no app artifacts exist Skip Deliver and Deploy when no app artifacts exist Feb 16, 2026
@mazhelez
Copy link
Collaborator

mazhelez commented Mar 3, 2026

@copilot it seems the solution works. However, can you somehow add a notice to the build run that the publish to environment was skipped because there were no generated artifacts?

Co-authored-by: mazhelez <43066499+mazhelez@users.noreply.github.com>
…rtifacts

Co-authored-by: mazhelez <43066499+mazhelez@users.noreply.github.com>
Copy link
Contributor Author

Copilot AI commented Mar 3, 2026

@copilot it seems the solution works. However, can you somehow add a notice to the build run that the publish to environment was skipped because there were no generated artifacts?

Added notice steps in commit 5542516. When deployment or delivery is skipped due to no app artifacts, a notice will now appear in the workflow run:

  • "Deployment to environment [name] was skipped because no app artifacts were found"
  • "Delivery to [target] was skipped because no app artifacts were found"

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.

3 participants