Remove deprecations doc CI job
What does this MR do and why?
- Related to #340985 (moved)
- Related to !70655 (closed) (that tries to get the job to pass by generating the doc, but fails linting because the YAML files use absolute links)
Removes the CI job added in !69358 (merged), and set to allow_failure: true
in !70465 (merged).
We had problems with conflicts and people struggling to run the rake task, so I set it to allow_failure: true
as a temporary fix so people could skip it. I ran it myself after people were able to get 5 deprecation YAML files merged, and generated the doc.
The problem now is that the YAML files need absolute links so they work when imported into the release post, but they need relative links when used in the GitLab docs. The rake task does not do any conversion (yet).
As a result, we've got a job that is going to be failing continuously until the relative link issue is resolved, so we should just remove the CI job while we work on it, and add it back when we're happy that it's all working as expected.
Screenshots or screen recordings
These are strongly recommended to assist reviewers and reduce the time to merge your change.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.