Notifies on slack when update feature categories automation fails to create issue
Due to an expired access token, the pipeline failed silently to create the issue to update feature categories.
Notification should be sent to slack for awareness and to react to a broken pipeline.
Example of a broken pipeline: https://gitlab.com/gitlab-com/gl-infra/scalability/-/pipelines/1021947043
Running with gitlab-runner 16.3.0~beta.108.g2b6048b4 (2b6048b4)
on green-5.saas-linux-small-amd64.runners-manager.gitlab.com/default xS6Vzpvo, system ID: s_6b1e4f06fcfd
feature flags: FF_USE_IMPROVED_URL_MASKING:true, FF_RESOLVE_FULL_TLS_CHAIN:false
...
$ scripts/fetch-feature-categories
$ scripts/check-feature-categories
config/feature_categories.yml is outdated!
Categories missing: ["cloud_connector"]
Outdated categories: ["application_performance", "billing_and_payments"]
Please run scripts/update-feature-categories in the gitlab-org/gitlab repository and submit an MR
Cleaning up project directory and file based variables
ERROR: Job failed: exit code 1
The failure above triggers another CI pipeline on failure to create the issue of outdated feature categories. However, when the action is triggered, the job succeeds even though the HTTP call returns an unauthorized response:
...
$ scripts/create-feature-category-issue
{"message":"401 Unauthorized"}
Cleaning up project directory and file based variables
Job succeeded
Edited by Hercules Merscher