[GH-ISSUE #5785] gitlab-ci: The repository is not being mirrored from GitHub to GitLab #3092

New issue

gitea-mirror · 2026-05-05T09:43:58-06:00

gitea-mirror commented

2026-05-05 09:43:58 -06:00

Originally created by @kmk3 on GitHub (Apr 13, 2023).
Original GitHub issue: https://github.com/netblue30/firejail/issues/5785

Background

Before this week (2023-04-10), master was last updated on GitLab on 2022-12-12,
by @Fred-Barclay:

f99a29634 ("clipit hardening (#5521)", 2022-12-12)
https://gitlab.com/Firejail/firejail_ci/activity

And indeed the last pipeline that was executed before this week was triggered
by that same commit:

f99a29634 ("clipit hardening (#5521)", 2022-12-12)
https://gitlab.com/Firejail/firejail_ci/-/pipelines/719948535
https://gitlab.com/Firejail/firejail_ci/-/pipelines

But there was no pipeline executed for the next commit on master onwards:

365ac8544 ("Fix whitelisting for wusc (#5526)", 2022-12-14)

That is, GitLab CI is not running every time master is updated on GitHub
anymore; it hasn't been running for about 4 months.

Though it still runs normally on push if I manually push to master on GitLab:

99a1006cf ("RELNOTES: bump release date to fix gitlab ci", 2023-04-10)
https://gitlab.com/Firejail/firejail_ci/-/pipelines/832926480

Questions

How was the repository being mirrored?

Any idea why it stopped?

I assume that it could be related to the following:

https://github.com/netblue30/firejail/issues/5146

Cc: @Fred-Barclay @reinerh

Originally created by @kmk3 on GitHub (Apr 13, 2023). Original GitHub issue: https://github.com/netblue30/firejail/issues/5785 ### Background Before this week (2023-04-10), master was last updated on GitLab on 2022-12-12, by @Fred-Barclay: * f99a29634 ("clipit hardening (#5521)", 2022-12-12) * <https://gitlab.com/Firejail/firejail_ci/activity> And indeed the last pipeline that was executed before this week was triggered by that same commit: * f99a29634 ("clipit hardening (#5521)", 2022-12-12) * <https://gitlab.com/Firejail/firejail_ci/-/pipelines/719948535> * <https://gitlab.com/Firejail/firejail_ci/-/pipelines> But there was no pipeline executed for the next commit on master onwards: * 365ac8544 ("Fix whitelisting for wusc (#5526)", 2022-12-14) That is, GitLab CI is not running every time master is updated on GitHub anymore; it hasn't been running for about 4 months. Though it still runs normally on push if I manually push to master on GitLab: * 99a1006cf ("RELNOTES: bump release date to fix gitlab ci", 2023-04-10) * <https://gitlab.com/Firejail/firejail_ci/-/pipelines/832926480> ### Questions How was the repository being mirrored? Any idea why it stopped? I assume that it could be related to the following: * <https://github.com/netblue30/firejail/issues/5146> Cc: @Fred-Barclay @reinerh

gitea-mirror commented

2026-05-05 09:44:00 -06:00

@kmk3 commented on GitHub (Apr 13, 2023):

Also, going to the clipit commit on the GitHub log:

f99a29634 ("clipit hardening (#5521)", 2022-12-12)
https://github.com/netblue30/firejail/commits/master?after=0554f6d7697389a2837a5ab47545d7a63900f8ab+454&branch=master&qualified_name=refs%2Fheads%2Fmaster

The checkmark shows this:

(icon) ci/gitlab/master - Pipeline passed on GitLab Details

And the icon on hover shows this:

GitLab.com (@gitlabhq) generated this status.

This GitLab CI entry is missing for newer commits in the GitHub log since then,
even on commits that were manually pushed to GitLab's master:

0554f6d76 ("Merge pull request #5777 from hotcapy/patch-1", 2023-04-11)

@kmk3 commented on GitHub (Apr 13, 2023): Also, going to the clipit commit on the GitHub log: * [`f99a29634`][1] ("clipit hardening (#5521)", 2022-12-12) * <https://github.com/netblue30/firejail/commits/master?after=0554f6d7697389a2837a5ab47545d7a63900f8ab+454&branch=master&qualified_name=refs%2Fheads%2Fmaster> The checkmark shows this: > [(icon)][] **ci/gitlab/master** - Pipeline passed on GitLab [Details][] [(icon)]: https://about.gitlab.com/gitlab-com/ [details]: https://gitlab.com/Firejail/firejail_ci/-/pipelines/719948535 And the icon on hover shows this: > GitLab.com (@gitlabhq) generated this status. This GitLab CI entry is missing for newer commits in the GitHub log since then, even on commits that were manually pushed to GitLab's master: * [`0554f6d76`][2] ("Merge pull request #5777 from hotcapy/patch-1", 2023-04-11) [1]: https://github.com/netblue30/firejail/commit/f99a296347a3a70fe898915746306dfe78bcdeae [2]: https://github.com/netblue30/firejail/commit/0554f6d7697389a2837a5ab47545d7a63900f8ab

Sign in to join this conversation.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#3092

Rows
Columns