From: Iñaki Malerba on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1326#note_660019560
LGTM, regarding your "too many anchors" comment, maybe something that would
make it simpler to read would be:
- `realtime_check_c9s` and `realtime_check_rhel9` are only used once, could be
merged into the job definition?
```yaml
c9s_realtime_check_merge_request:
extends: [.trusted, .merge_request,
.9-common,
.realtime_check_common,
.trigger_c9s_pipeline]
trigger:
branch: c9s-rt
variables:
merge_branch: main-rt
name: kernel-rt-c9s
```
- move anchors next to the place they're used so it's simpler to follow?
```yaml
# c9s realtime branch CI
.realtime_full_c9s:
variables:
name: kernel-rt-c9s
kpet_tree_family: c9s-rt
RUN_ONLY_FOR_RT: 'true'
c9s_realtime_merge_request:
extends: [.trusted, .merge_request,
.9-common,
.realtime_pipeline_common,
.trigger_c9s_pipeline, .realtime_full_c9s]
c9s_realtime_baseline:
extends: [.trusted, .baseline,
.9-common,
.realtime_pipeline_common,
.trigger_c9s_pipeline, .realtime_full_c9s]
```
Not sure this is better, YMMV :thumbsup:
_______________________________________________
kernel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
