Hello, I hope that I’m posting to good enough category, didn’t find anything Framagit service related. And I don’t speak french, so sorry..
I’m using Framagit for some time and I’ve noticed recently few things.
First one is non-configurable pull image policy, currently it is set to download always. As I’m using my own image, sometimes it is preferable to set it to “if not present“ to avoid redownloading it over and over, unfortunately this option is disabled in Framagit. Is there somone here who could enable other options (like Framagit admins)? Right now setting image ‘pull_policy‘ to anything other than ‘always’ ends with pipeline error.
Second thing, package registry looks like it is disabled in Framagit(or I don’t know how to configure/set it up correctly). It would be great to have possibility to upload own packages and refer them in releases.
Unfortunately option isn’t present in general project feature list(Settings/General, “Visibility, project features, permissions“). There’s no “Packages” option there and under ‘Deploy‘ menu, as far I know it should be enabled by default (feature is now part of GitLab free tier), but for some reason it isn’t. Is there possibility to enable it? Regards, Pawel
First one is non-configurable pull image policy
We added if-not-present to allowed_pull_policies on the configuration of the runner, which will be restarted this night. You will be able to choose the policy you want.
Second thing, package registry looks like it is disabled in Framagit
Sorry, but it will stay disabled: we don’t want to store an infinite amount of packages. We know we would end with too much disk space needed for that. So no package registry, no Docker image registry either.
Regards,
@Framasky Thank you for quick reply and enabling more pull policies. For packages there are quota limits for each project, package has currently 5GiB quota set. But I understand. I’m not much interested in docker image registry, packages were meant to upload software builds for distribution.
Same can be done with artifacts (disabling their expiry date and linking them to Release), but they can be deleted by accident (eg. from GUI frontend).
It would be great to put what some information what isn’t enabled and why on front page or somewhere. I was convinced that this feature could be used until I’ve started to dig more into documentation (official Gitlab / Framagit one and YT tutorials) and only after that figured out that something is missing there.
Regards,
Pawel