Pipelines docs - ensure that where only/except content is provided, rules is also documented
Problem to solve
We updated the docs to indicate that "the rules syntax is now the preferred method of setting job policies. only and except are candidates for deprecation, and may be removed in the future."
It follows that if folk are creating CI from scratch, we want it to be easy for them to use rules from day 1. And when existing configuration is being changed or extended, migrated to rules
Where only/except is documented, we need to provide equivalent documentation for rules as well.
MVP would be to at least mention that rules is supported.
Further details
In flight
- !19098 (closed) should handle limiting job creation using variables
This included mentioning that only/except is deprecated, and in this instance, referring to existing documentation for rules. Whatever approach is agreed in that MR, it should be done consistently in the other places as well.
To do:
- A GitLab Premium customer highlighted (internal) that merge request pipelines omits that
rulescan be used. - Scope other documentation for
only/except
Proposal
Track down only/except references, and add documentation, with comparable examples, for rules.
Who can address the issue
Supplied examples should be tested, so some technical effort is also required.