Hi Sean - I stand corrected, #remoteTypeSelector: doesn’t seem to be needed (a
case of getting all the other stuff right - and Docker is such a huge help for
this).
For SmalltalkCI the automatic Test side might win me over. Does it also spot
load load failures (like Undeclared class) and do a n
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
Hi Sean/Fabio - I’m still mulling over which direction to jump. When
experimenting with PharoLambda and a minimal image it was all very custom and
so I just used GitLab “natively” - and as you have noted - Gitlab has got a lot
of built in CI stuff.
Now my need has expanded to something a bit m
On Wed, May 16, 2018 at 3:34 AM Sean P. DeNigris
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
Tim Mackinnon wrote
> Have you written anything else up about it - or is this the “user manual”
> for now?
The latter :) It was an itch I scratched because GL offers unlimited private
projects and significant CI build time for free and then shared just in case
others were struggling with the same
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 libra
Hi Sean,
Sorry, I just saw your response. Questions/comments are inline...
On Tue, May 15, 2018 at 3:26 PM Sean P. DeNigris
wrote:
> Tim Mackinnon wrote
> > But I don’t understand how it works on Gitlab
>
> The gitlab-smalltalk-ci project performs three roles:
> 1. The glue which connects Gitla
Hi Tim,
On Tue, May 15, 2018 at 11:56 AM Tim Mackinnon wrote:
> Thanks Fabio - it sounds like Sean already has figured something out - but
> I haven’t fully grok’d how it hangs together. From your description, it
> sounds like you expect SmalltalkCI to be like a submodule of your project -
> and
Hi Sean - it certainly sounds like its worth a poke. Have you written anything
else up about it - or is this the “user manual” for now? Presumable a lot of
the below could go in the readme.md for the project itself.
So to get started with it - is the intent that you fork it so you can customise
Tim Mackinnon wrote
> But I don’t understand how it works on Gitlab
The gitlab-smalltalk-ci project performs three roles:
1. The glue which connects Gitlab and smalltalkCI. As a bonus, it does all
the necessary in-container work to setup SSH for private Gitlab projects, so
you'd just have to creat
Thanks Fabio - it sounds like Sean already has figured something out - but I
haven’t fully grok’d how it hangs together. From your description, it sounds
like you expect SmalltalkCI to be like a submodule of your project - and you
can then invoke it from your normal projects build script? Howeve
Hi Tim,
It should be relatively straightforward to use smalltalkCI on Gitlab CI.
All you have to take care of is to ensure the Linux container has all Pharo
dependencies [1] installed correctly. If you append smalltalkCI's `bin`
directory to your $PATH, you can simply call `smalltalkci -s Pharo-6.
Hi Sean - thanks for mentioning that - I tried it ages ago and didn’t get on
well with it on Travs. But I don’t understand how it works on Gitlab - and the
project readme.md seems to assume you understand how its approaching the
problem (which possibly has changed over the years).
Looking at yo
13 matches
Mail list logo
