On Wed, May 16, 2018 at 3:34 AM Sean P. DeNigris <sean@clipperadams.com> wrote:
fniephaus wrote
As a bonus, it does all
the necessary in-container work to setup SSH for private Gitlab projects, so you'd just have to create/enable the deploy key in the Gitlab web UI.
This is only needed for private repos on GitLab, right?
Correct.
fniephaus wrote
This library needs to be used manually, right? Or is this somehow part of the build process?
The library is used to generate the artifacts (e.g. config files), which are then committed to be picked up by the CI. I assume that's what you meant by "manually"?
Yes, that's what I meant. Up until now, templates have worked quite well, but I can also see why a library would be helpful at some point.
fniephaus wrote
I think it'd be great if we could somehow merge your additions back into smalltalkCI's repo.
Definitely open to that. I got it "working" for my use cases and then paused. IIRC I did open a few issues in smalltalkCI related to this and Docker.
Yes, you did. And I hope I have more time to work on smalltalkCI features soon...the list is getting longer and longer.
fniephaus wrote
I'd love to hear your feedback on the solution I suggested in my previous email. Any ideas how to make it better?
Which one?
This one: https://gist.github.com/fniephaus/b95c4ed15abd8c4305277f51fbe21fee
fniephaus wrote
Have a look at the launcher script for smalltalkCI [1] used in the Docker image.
I will.
----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html