Hi Felix, I've noticed that a while ago as well, but I was certain it wasn't caused by the recent changes cause we had extensively test them.
Today I found some time to track down the issue and looks like its a regression on gitlab itself, probably on the latest update. The issue is that the template now uses the default .pre and .post stages to avoid over witting/forcing projects on a specific stages schema. This seems to have been working fine, till roughly 2 weeks ago. [1] Some projects that define more jobs and naturally their custom stages, such as epiphany, had pipelines working the whole time. Briefly looking at gitlab, I've found this [2] bug report, but there's probably an older one I suspect. I think we can try to workaround this in our template, and I will try rolling something out tomorrow. Will most likely move back the current jobs back to [build, deploy] stages which hopefully every project has already. This does have the potential to break some CI configurations and if so please do ping me on irc (or rocket chat) or reply to this email. I am sorry for the unfortunate timing and for not looking at it sooner. Hopefully this will be resolved soon™️ Cheers, Jordan [1] https://gitlab.gnome.org/GNOME/gnome-builder/pipelines/154333 [2] https://gitlab.com/gitlab-org/gitlab/-/issues/209102 ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Sunday, March 8, 2020 4:30 PM, Felix Riemann <friem...@gnome.org> wrote: > Am Mittwoch, den 19.02.2020, 14:50 +0100 schrieb Bartłomiej Piotrowski: > > > Hello, > > Hi! > > > For past few days I've been working to ensure that Flatpak builds are > > still functional without additional privileges. If your project is > > using > > citemplates[1], the configuration change should be invisible to your > > pipelines and you can keep on doing awesome GNOME work. > > Is is there something necessary to change on the project level? The > reason I am asking is that I noticed my project (eog) no longer > triggering CI pipelines at all since roughly the time this change was > implemented. > > Updating the configuration to the latest template didn't change > anything. Trying to trigger the pipeline manually from Gitlab doesn't > work either. > > I also looked around and found the gedit and gnome-builder repositories > showing the same behaviour. > > Regards, > > Felix > > desktop-devel-list mailing list > desktop-devel-list@gnome.org > https://mail.gnome.org/mailman/listinfo/desktop-devel-list
publickey - jordan@alatiera.com - 0x0BDAD30B.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
_______________________________________________ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
