Tim Mackinnon wrote > the use of Iceberg and projects using github:// (which needs them by > default) causes quite a lot of pain (even if they aren’t private repos). > … > Iceberg > enableMetacelloIntegration: true; > remoteTypeSelector: #httpsUrl.
This is part of my standard workflow and I didn't experience it as a pain point. It seems I uploaded my public GH key, but after that it "just worked". IIRC it seemed to automatically fallback to https when ssh failed, but it's been a while and I'm not in front of a pipeline. The first message is needed, especially to use `gitlab://` URLs, but I never used the second. Tim Mackinnon wrote > the reality is all you are really plugging into Gitlab is: > …loadProject.st… testProject.st I guess you could say that, except smalltalkCI also handles any needed setup, like Linux 32-bit libs (which I handle with Docker instead). Also, it saves you from having to construct the .st files in your example because: - there is a configuration model that allows you to specify the baseline name, target platforms, etc instead of manually writing load scripts - smalltalkCI remembers which tests it loaded and runs those automatically, so by default no extra work is needed to enable testing Tim Mackinnon wrote > by no means is this a citicism… All good :) ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
