service/ci.md

@@ -105,26 +105,16 @@ See [Runner disk fills up](#runner-disk-fills-up).
 
 ## Running a job locally
 
-If you are having trouble reproducing a problem or just want to run a
-job in your local, trusted environment, know that you can [install
-your own GitLab runner](https://docs.gitlab.com/runner/install/index.html) and actually use it to run jobs locally,
-without registering it with the central server. The magic command is
-[`gitlab-runner exec`](https://docs.gitlab.com/runner/commands/#gitlab-runner-exec). For example, this will run a job named
-`tests` with a `shell` executor:
+It used to be possible to run pipelines locally using `gitlab-runner exec` but
+this was deprecated a while ago and the feature is now removed from latest
+versions of the runner.
 
-    gitlab-runner exec shell tests
+According to the GitLab issue tracker the feature is currently
+[redesigned](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/2797) to be
+more complete, as the above method had important limitations.
 
-To see a list of available executors, run:
-
-    gitlab-runner exec
-
-To see a list of all available options for the shell executor, run:
-
-    gitlab-runner exec shell
-
-Note that this feature was deprecated for a while but re-enabled. It
-is being [redesigned](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/2797) to be more complete, as the above has
-important limitations.
+An alternative that's reported to be working reasonably well is the 3rd-party
+[gitlab-ci-local](https://github.com/firecow/gitlab-ci-local) project.
 
 ## Build Docker images with kaniko