Skip to content

Conversation

@patersonc
Copy link
Contributor

No description provided.

@patersonc patersonc marked this pull request as draft November 27, 2025 21:34
@patersonc patersonc force-pushed the patersonc/cip-config-update branch 2 times, most recently from d34adf9 to 0b4cadd Compare November 27, 2025 23:44
@patersonc patersonc marked this pull request as ready for review November 27, 2025 23:45
The CIP project only supports specific architectures and build
configurations. Give the project complete control over this by not
scheduling standard jobs.

Signed-off-by: Chris Paterson <chris.paterson2@renesas.com>
The validation tools get confused if we make changes to anchors in
jobs-cip.yaml and not in jobs.yaml if they share the same name.

Avoid the issue by renaming the CIP specific anchors.

Signed-off-by: Chris Paterson <chris.paterson2@renesas.com>
Also make more use of anchors to slim down the job definitions.

Signed-off-by: Chris Paterson <chris.paterson2@renesas.com>
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.

1 participant