Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make Citadel to use custom ciconfig to exclude gz-sim/gz-launch #1097

Merged
merged 2 commits into from
Dec 15, 2023

Conversation

j-rivero
Copy link
Contributor

Need to exclude gz-sim and gz-launch from Citadel. To avoid adding harcoded values in the DSL, the declarative approach is to create a new ciconfig for Citadel, just by duplicating the win configuration and make the exclusions for the libraries.

@@ -96,7 +96,7 @@ collections:
configs:
- focal
- brew
- win
Copy link
Contributor

Choose a reason for hiding this comment

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

IIUC this PR this line has to be kept(? Then you would have focal, brew, win and win_citadel configs

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Note that this config section is defining the configurations for Citadel so win is replaced by win_citadel.

You are right about that now we have 4 configurations available, with winstill defined generally in the ci_configs section and used for Fortress, Garden, Harmonic, Ionic and upcoming.

Copy link
Contributor

Choose a reason for hiding this comment

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

Oh, I see, thanks for the explanation

Copy link
Contributor

@Blast545 Blast545 left a comment

Choose a reason for hiding this comment

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

Small question jic, otherwise LGTM

@j-rivero j-rivero merged commit 939913e into master Dec 15, 2023
@j-rivero j-rivero deleted the jrivero/win_citadel_ciconfig branch December 15, 2023 17:18
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.

2 participants