[FF] ci_create_failed_job_on_rules_parse_error -- create a failed job when rules cannot be evaluated
Summary
Roll out the feature currently behind the ci_create_failed_job_on_rules_parse_error feature flag.
- DRI: @oyakovenko-ext
- Team Slack channel:
#g_pipeline_authoring
Note
Process and guidance live in the docs — this issue is just the commands and a place to track the rollout. "Rolling out" means incrementally enabling the flag on GitLab.com to validate stability — it is not the same as releasing the feature, which happens when the flag is removed. Feature flag controls · Feature flag lifecycle
What could go wrong?
Enabling this creates a job that previously did not exist, so an affected
pipeline gains a visibly failed job and reports warnings. The pipeline status
itself stays success, because failed plus allow_failure resolves to
success.
Scope is narrow by design: only the silent drop changes. A stage that keeps
another job still fails creation with a config_error, and a non-optional
needs: on a broken job still fails creation, so nothing that fails today
starts passing.
Affected projects are identified by the logging from !257559 (merged). Volume is concentrated: in one four-day window a single project produced 81% of events, so per-project rollout is preferable to a percentage before going wide.
Watch json.message: "rule errors dropped with fully excluded stage" in
Kibana. Occurrences should fall to zero for a namespace once the flag is on
there, because the stage is no longer dropped.
Events
- Exceptions with ci_create_failed_job_on_rules_parse_error:1
- Events with ci_create_failed_job_on_rules_parse_error:1
- Error rate and other graphs by modifying the examples in the Visualization Library
Feature Flag events are only logged by default for feature flags marked for the current or future milestones. To enable while the feature flag is active, see https://docs.gitlab.com/development/feature_flags/#logging
Rollout
Run all production /chatops in #production and cross-post the results to #g_pipeline_authoring. Background: incremental rollout process, feature actors.
Non-production
/chatops gitlab run feature set ci_create_failed_job_on_rules_parse_error 50 --actors --dev --pre --staging --staging-ref
/chatops gitlab run feature set ci_create_failed_job_on_rules_parse_error true --dev --pre --staging --staging-refProduction — percentage rollout (wait ≥15 min between steps, watch dashboards):
/chatops gitlab run feature set ci_create_failed_job_on_rules_parse_error <percentage> --actorsOr target specific actors instead:
/chatops gitlab run feature set --project=gitlab-org/gitlab,gitlab-org/gitlab-foss ci_create_failed_job_on_rules_parse_error true
/chatops gitlab run feature set --group=gitlab-org,gitlab-com ci_create_failed_job_on_rules_parse_error true
/chatops gitlab run feature set --user=oyakovenko-ext ci_create_failed_job_on_rules_parse_error trueBefore global rollout
Confirm the relevant gotchas before going to 100% — see enabling a feature for GitLab.com:
- Docs + version history updated
- Breaking changes announced, if any
- Change management issue opened, if required
- External API consumers handled with a fail-open mechanism, if applicable
Cleanup
Remove the flag once deemed stable — see cleaning up. Track it here, or open a follow-up Feature Flag Cleanup issue. Remove the flag and its YAML definition from the codebase, then:
/chatops gitlab run release check <merge-request-url> <milestone>
/chatops gitlab run feature delete ci_create_failed_job_on_rules_parse_error --dev --pre --staging --staging-ref --productionRollback
/chatops gitlab run feature set ci_create_failed_job_on_rules_parse_error false # production
/chatops gitlab run feature set ci_create_failed_job_on_rules_parse_error false --dev --pre --staging --staging-ref # non-production
/chatops gitlab run feature delete ci_create_failed_job_on_rules_parse_error --dev --pre --staging --staging-ref --production # remove entirely