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? However peeking at what Sean pointed at - it seemed like he expected you to intermingle your project with the SmalltalkCI one - so Iâm not really clear on how he uses it. It sounds like all the right pieces are there - just not quite sure what the concept is - particularly given that Gitlab Pipelines already is a CI with the concept of jobs - just not Smalltalk ones. At its best - how does SmalltalkCI function - I never quite understood the pipeline when checked years ago. Tim
On 15 May 2018, at 09:09, Fabio Niephaus <lists@fniephaus.com> wrote:
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.0` in your project's root directory to test against Pharo-6.0.
Hope this helps. And if you work out a simple and generic way of using smalltalkCI on Gitlab, please feel free to open a PR against smalltalkCI and contribute a template :)
Best, Fabio
[1] https://github.com/travis-ci/travis-build/blob/51ebd738f537a82874b03cb964eca... <https://github.com/travis-ci/travis-build/blob/51ebd738f537a82874b03cb964eca...>
On Tue, May 15, 2018 at 12:40 AM Tim Mackinnon <tim@testit.works> wrote: 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 your url - how is that running a project that you have in a different repo? Is there some web hook that causes it to then trigger a build cycle? I can see you edited a BaselineOfGitLabCI and added a BabyPhexample <https://gitlab.com/SeanDeNigris/gitlab-smalltalk-ci/commit/d59ba3788aa86bde3...> - which seems a bit inside out to me - but Iâm hanging in there (so do you add other projects in this same file?).
I also donât understand the pipeline model - there seems to be just one pipeline (and gitlab has great pipeline support)?
And then - when it all builds successfully - how does it deploy (hence my pipeline question).
Iâm lost - but curious, as maybe I can save time on what Iâm doing (writing more apps vs pissing around with missing infrastructure).
Tim
On 14 May 2018, at 22:38, Sean P. DeNigris <sean@clipperadams.com <mailto:sean@clipperadams.com>> wrote:
Tim Mackinnon wrote
may take another look at SmalltalkCI - the trouble is, I really donât like Travis⦠I quite like the model of Gitlabâs one stop shop
I use SmalltalkCI on Gitlab (https://gitlab.com/SeanDeNigris/gitlab-smalltalk-ci <https://gitlab.com/SeanDeNigris/gitlab-smalltalk-ci>)
----- Cheers, Sean
-- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html>