GitLab on postmarketOS Status

[Resolved] GitLab is down

Fri, 16 Jan 2026 16:49:00 +0000

gitlab.postmarketos.org is currently down while our host (OSUOSL) performs a datacenter migration. ETA is currently unknown.

[Resolved] GitLab data loss

Thu, 04 Dec 2025 19:00:00 +0000

Due to some problem with the database at the host of our GitLab instance we experience some data loss of gitlab-related information: MRs, comments, and issues. Anything done in GitLab during that period of time might have been lost and have to be recreated. Repository information was not lost.

[Resolved] Connectivity issues to GitLab

Mon, 20 Oct 2025 12:39:00 +0000

We are detecting network connectivity issues from multiple places to gitlab.postmarketos.org, likely caused by intermediate network errors unrelated to our infrastructure. GitLab is managed by OSUOSL in their own hardware, and the service is otherwise up and healthy. We are seeking clarification on possible reasons for the outages.

[Resolved] GitLab is down

Fri, 18 Jul 2025 06:51:00 +0000

gitlab.postmarketos.org is currently down due to unknown reasons. We have contacted OSUOSL who are hosting our GitLab instance.

[Resolved] Scheduled downtime for GitLab instance

Mon, 19 May 2025 17:00:00 +0000

The postmarketOS GitLab instance has an upgrade scheduled for Monday, May 19 @ 17:00 UTC. At least 1 hour of downtime can be expected while this is taking place. Thanks for your patience and happy hacking!

[Resolved] gitlab is down

Thu, 12 Dec 2024 06:22:00 +0000

Unfortunately gitlab.postmarketos.org is currently down. We have notified OSUOSL. It is the middle of the night for them currently, so it will probably take a bit until it comes back online. We are working hard with them to prevent such outages in the future.

UPDATE: an automatic update went wrong, it is up again.

[Resolved] GitLab reboot to increase RAM and CPU

Sun, 08 Dec 2024 17:30:00 +0000

OSUOSL is rebooting gitlab.postmarketos.org to increase RAM and CPU, this should help with making it more reliable.

[Resolved] GitLab doesn't trigger on git pushes

Fri, 06 Dec 2024 08:35:00 +0000

GitLab doesn’t trigger on git pushes currently, which means MRs do not get updated after pushing to a git repository. We have contacted OSUOSL about it.

[Resolved] Our GitLab is down

Mon, 02 Dec 2024 10:00:00 +0000

GitLab is stuck in “Waiting for GitLab to boot”. OSUOSL maintains the instance for us (see blog post), and we have contacted them.

More information: https://gitlab.postmarketos.org/postmarketOS/postmarketos/-/issues/87

[Resolved] HTTP 502: Waiting for GitLab to boot

Thu, 28 Nov 2024 08:00:00 +0000

GitLab is stuck in “Waiting for GitLab to boot”. OSUOSL maintains the instance for us (see blog post), and we have contacted them. Unfortunately it is a public holiday in the US, so it looks like this won’t be resolved today.

UPDATE: OSUOSL resolved it and added additional monitoring, so this should not go unnoticed for so long in the future, if it happens again.

[Resolved] Migration to gitlab.postmarketos.org

Sat, 05 Oct 2024 22:00:00 +0000

(Find updates at the bottom)

On Sunday, 2024-10-06 00:00 CEST, we are migrating from gitlab.com to our self-hosted instance at gitlab.postmarketos.org. It is expected to take the whole day (a test import took 18 hours).

Projects (pmbootstrap, pmaports, etc.) will be read-only during the migration, meaning that you can’t create issues, merge requests or comment on these.
Accounts in gitlab.postmarketos.org will be approved after the migration is done.
Read postmarketos#77 for more information on the migration plan, why we migrate to a self-hosted gitlab instance in the first place and why to that instead of Forgejo, SourceHut, etc.

Update 18:15 CEST:

Transfer is still ongoing for pmaports.git, but has completed for all other repositories.
Mirroring of git repositories to gitlab.com has been set up here.

After the transfer of all repositories has completed, the next steps are as follows.

Set up permissions for Core Contributors, Trusted Contributors, Active Contributors (see team).
Unarchive all imported repositories at gitlab.postmarketos.org. (The repositories at gitlab.com will stay archived.)
Approval of accounts, so https://gitlab.postmarketos.org can be used. It will probably take a few more hours until we reach this point, please be patient.
Various clean up tasks (e.g. recreating epics as milestones, ensuring/fixing push hooks to various sites like postmarketos.org, adjust all repos where we have gitlab.com/postmarketos hardcoded)

Update 23:00 CEST:

Repositories are transferred. The transfer ran into a timeout for 125 merge requests in pmaports.git, those were not transferred. For all old merge requests, we just recommend looking at the archived ones at gitlab.com (we won’t delete them). These also have the proper users associated to comments, which was not possible with the import.
It seems that all issues were imported successfully.
All imported merge requests have been closed (as they are now owned by the “Administrator” user who was used during import). If you had an open merge request that is still relevant, please re-submit it at gitlab.postmarketos.org. We realize that this is inconvenient, but it was not possible to do this differently as users from gitlab.com could not be mapped to users on gitlab.postmarketos.org (even if they already existed and were approved at time of transfer).
Accounts are being approved now. If you just registered, give us some time to review new account requests. We should be able to do it within a day usually.
If you run into any issues, please write in the postmarketos-devel IRC/matrix channel.
Some of the mentioned clean up tasks still need to be done, this will be tracked in postmarketos#77 (now on gitlab.postmarketos.org).