![]() ![]() Pause your runners, or block new jobs from starting by adding the following to your /etc/gitlab/gitlab.rb: To address the above two scenarios, it is advised to do the following prior to upgrading: However, depending on the error, the GitLab Runner either retries, or eventually terminates, job handling.Īs for the artifacts, the GitLab Runner attempts to upload them three times, after which the job eventually fails. When GitLab is back online, the trace updates should self-heal. If you upgrade your GitLab instance while the GitLab Runner is processing jobs, the trace updates fail. Dealing with running CI/CD pipelines and jobs Check for background migrations before upgradingĬertain releases may require different migrations to beįinished before you upgrade to the newer version.įor more information, see background migrations. ![]() See the guide to plan your GitLab upgrade.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |