timetobail
My stack

Playbook for makers · Forced move · free while in beta

Act

GitLab 20.0 removes old retry:when failure reasons (May 20, 2027)

Readers can stay on GitLab: they change a setting or plan. Help the ones who would rather leave.

214 days left · May 20, 2027 · Public page

Low switching pressure28/100

An estimate from the deadline, cost, discussion and need to move. It is not a product rating.

What goes into it

Confidence: medium.

deadline8/30
money14/25
attention0/25
audience0/12
force6/8
  • Hard deadline in 214 days.
  • The change is forced: it reaches users even if they wait.

  1. 1 Related discussions

    Only threads tied to this event that talk about leaving, moving or prices. Saved, not live. Check the date and read the thread before replying.

    No live threads yet.

  2. 2 What people ask

    No common questions yet.

  3. 3 Reply templates

    Answer the question first. Link only if it helps. Always keep the disclosure line. Never post the same text twice.

    Helpful first
    Sorry you have to deal with this. You can stay on GitLab. Here is what to change before May 20, 2027:

1. Search your CI files. Look for the two old names in .gitlab-ci.yml and in files it includes.
2. Use the new reasons. List the new names you need, like no_updates_running or server_timeout_running.
3. Run CI lint. Open the pipeline editor. The warning should be gone.

If they would rather leave, describe a verified way <your product> can help: <your link>
[Disclosure: I build <your product>.]
    Short answer
    You have until May 20, 2027. You can stay on GitLab. First: search your CI files. Then use the new reasons.
Happy to help if you get stuck.
[Disclosure: I build <your product>.]

  4. 4 Switch-page builder

    Create a draft “Switch from GitLab” page. Add your product, review every claim, then copy HTML or Markdown. Your product claims need your own evidence.

    • Add your product name to replace “Your product”.
    Preview

    Switch from GitLab to Your product

    GitLab CI jobs that retry on the old timeout reasons: a change is due by May 20. You can stay on GitLab. If you would rather leave, here is how to move to Your product.

    What changes at GitLab

    GitLab 19.0 split two failure reasons into more exact ones. The old names are stuck_or_timeout_failure and job_execution_timeout. You can still use them in retry:when, but you get a warning. GitLab plans to remove them in GitLab 20.0, on May 20, 2027.

    • GitLab 20.0 release (planned): May 20, 2027 (GitLab)
    • Removed in: GitLab 20.0 (GitLab)
    • Deprecated values: stuck_or_timeout_failure and job_execution_timeout (GitLab)
    • Split into new reasons in: GitLab 19.0 (GitLab)
    • Until then: They work as aliases for the new reasons, and CI lint shows a warning (GitLab)
    • Replace stuck_or_timeout_failure with: The ones you need of stuck_pending_with_matching_runners, stuck_pending_no_matching_runners, no_updates_running and no_updates_canceling (GitLab)
    • Replace job_execution_timeout with: server_timeout_running and/or server_timeout_canceling (GitLab)
    • GitLab.com: Deprecated features can be removed at any time in the month before the release (GitLab)
    • Pipelines that list the old values: Must use the new values before GitLab 20.0 (GitLab)

    You can stay on GitLab if you make the change. This page is for people who would rather leave.

    What Your product gives you

    Write two or three short lines here. Say what Your product does, who it is for, and what it costs. Use only facts you can show.

    How to move from GitLab to Your product

    1. Save what you need from GitLab. Keep a copy before you cancel anything.
    2. Import into Your product. Say which files you accept and how long an import takes.

    Tell readers the key date: May 20, 2027.

    Questions people ask

    If Your product has a direct answer to one of these, add it here. Keep it short and true.

    How to help new users settle in

    Send one short email. Say what changed, where to find you now, and what they need to do. Put the most important line first.

    If there is a date, send a short reminder a few days before it. Keep a copy of the list you sent it to.

    Sources

  5. 5 Search ideas to validate

    suggested, not measured Phrases people may search when a tool changes like this. We have no search volume data for them.

    • gitlab ci jobs that retry on the old timeout reasons
    • gitlab alternative
    • gitlab alternatives
    • gitlab export
    • how to leave gitlab
    • switch from gitlab
    • gitlab migration
    • gitlab migration 2027