Skip to content

Make fallback_run_target mandatory - #656

Merged
MaciejKaszynski merged 2 commits into
eclipse-score:mainfrom
etas-contrib:fallback_run_target_mandatory
Sep 21, 2026
Merged

MaciejKaszynski merged 2 commits into
eclipse-score:mainfrom
etas-contrib:fallback_run_target_mandatory

Conversation

@NicolasFussberger

Copy link
Copy Markdown
Contributor

Behaviour before:

fallback_run_target was optional in the json schema.
However, the python script was validating that it exists and aborts if not present.
So it was actually mandatory already. This was confusing to the user.

Behaviour now:

fallback_run_target is marked required in the json schema.
No custom validation required to make sure its configured - already handled via schema validation.

Resolves: #655

@MaciejKaszynski
MaciejKaszynski merged commit 1622364 into eclipse-score:main Sep 21, 2026
12 of 14 checks passed
@github-project-automation github-project-automation Bot moved this from Backlog to Done in LCM - Lifecycle & Health FT Sep 21, 2026

This branch is waiting to be deployed

1 waiting deployment
workflow-approval — 0f804d35 Waiting Sep 21, 2026 by MaciejKaszynski via Build and test unit-tests-x86_64-qnx / approval #918
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

Improvement: Make fallback_run_target mandatory in json schema

3 participants