Hi Harald,
On 8/12/22 18:26, Harald Welte wrote:
On Fri, Aug 12, 2022 at 04:38:42PM +0700, Vadim Yanitskiy wrote:
Cloning via https:// works, but doesn't via git://
some people would consider that a feature... In fact we've even had a bug report years ago considering clone possibility via git:// a bug.
I think a good first step would be to not enable it for new projects, to avoid people from creating clones that would break if we eventually disable it.
this way we need to invest some additional time into git-to-https migration, because, as I mentioned earlier, both Coverity [1] and Jenkins [2] are still using git://. And currently both are failing when trying to clone libosmo-gprs.git, see:
[1] https://jenkins.osmocom.org/jenkins/job/osmocom-coverity/1698/ [2] https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-pcu/2430/
The main problem with using Gitea is that all projects are grouped: we have 'osmocom', 'cellular-infrastructure', 'phone-side', and more. This is why we cannot simply do s#git://git#https://gitea#.
To overcome this problem, we could clone/pull from Gerrit instead. But this is not going to work for projects not present in Gerrit... :/
Best regards, Vadim.