Why it's not directly possible
CI pipelines are designed with a strong emphasis on dependency management. When a job in a pipeline fails, subsequent jobs are marked as skipped because they may rely on the output or success of the failed job. (Forcing execution could lead to unexpected errors.)
Workaround using allow_failure
You can mark a job as "allowed to fail" in your config. This way, subsequent jobs are not influenced by the status of this job.
allow_failure: true
Important: Subsequent jobs should obviously not strictly depend on the job's successful completion and/or have built-in error handling.
https://docs.gitlab.com/ee/ci/yaml/#allow_failure
allow_failure: true
on this job and it will not impact next jobs – Aquila