> On 28 Aug 2020, at 23:45, Jonathan van Alteren <jvalte...@objectguild.com> 
> wrote:
> 
> Ah yes, sorry, you're right. You do have to commit/push for that to work.
> 
> I'm interested to hear what your experience is with using #record.

My experience is that there is nothing better than what you propose. 

> 
> Kind regards,
> 
> Jonathan van Alteren
> 
> Founding Member | Object Guild B.V.
> Sustainable Software for Purpose-Driven Organizations
> 
> jvalte...@objectguild.com
> On 28 Aug 2020, 20:00 +0200, Esteban Maringolo <emaring...@gmail.com>, wrote:
>> Hi Jonathan,
>> 
>> I never thought of SmalltalkCI for that (I use Gitlab) but in essence
>> it still requires a trial and error approach (of committing the
>> Baseline and loading it afterwards to see if it works).
>> 
>> Metacello has a "record" operation that basically does a dry run of
>> the load, but I don't know if there is a way to do it using the
>> Baseline in the image instead of one in a repository.
>> 
>> Regards!
>> 
>> Esteban A. Maringolo
>> 
>> On Fri, Aug 28, 2020 at 10:10 AM Jonathan van Alteren
>> <jvalte...@objectguild.com> wrote:
>>> 
>>> Hi Esteban,
>>> 
>>> You might want to give smalltalkCI a try: 
>>> https://github.com/hpi-swa/smalltalkCI
>>> 
>>> I've recently started using it myself, with GitLab CI and GitHub Actions, 
>>> but one of the cool things is that you can use it to test your build 
>>> locally.
>>> 
>>> For example, create a .smalltalk.ston file for your project which loads the 
>>> baseline that you want to test, like this:
>>> 
>>> SmalltalkCISpec {
>>> #loading : [
>>> SCIMetacelloLoadSpec {
>>> #baseline : 'MyProject',
>>> #directory : 'source',
>>> #load : [ 'default' ],
>>> #onWarningLog : true,
>>> #platforms : [ #pharo ]
>>> }
>>> ],
>>> #testing : {
>>> #categories : [ 'MyProject-Tests' ]
>>> }
>>> }
>>> 
>>> Then clone the smalltalkCI repo locally and open a terminal on its 
>>> location, for example /Users/johndoe/git/smalltalkCI. You can then simply 
>>> use smalltalkCI to build a Pharo image of your baseline, which effectively 
>>> tests the correct working of your baseline:
>>> 
>>> bin/smalltalkci -s "Pharo64-8.0" 
>>> /Users/johndoe/git/MyProject/.smalltalk.ston
>>> 
>>> By default, it will run all tests in the image, but you can change the list 
>>> of tests being run by modifying the .smalltalk.ston file accordingly (see 
>>> https://github.com/hpi-swa/smalltalkCI#testcase-selection).
>>> 
>>> Hope this helps!
>>> 
>>> Kind regards,
>>> 
>>> Jonathan van Alteren
>>> 
>>> Founding Member | Object Guild B.V.
>>> Sustainable Software for Purpose-Driven Organizations
>>> 
>>> jvalte...@objectguild.com
>>> On 27 Aug 2020, 04:12 +0200, Esteban Maringolo <emaring...@gmail.com>, 
>>> wrote:
>>> 
>>> Hi,
>>> 
>>> How can I check that my baseline works without having to publish
>>> everything, check that it fails and then going to the origin, fixing,
>>> etc?
>>> 
>>> I might be particularly idiot to always miss something, I usually have
>>> to try at least four times (in a blank image) that my Baseline,
>>> dependencies, etc. works as expected.
>>> 
>>> There must be some other way.
>>> 
>>> Esteban A. Maringolo
>>> 
>> 

--------------------------------------------
Stéphane Ducasse
http://stephane.ducasse.free.fr / http://www.pharo.org 
03 59 35 87 52
Assistant: Aurore Dalle 
FAX 03 59 57 78 50
TEL 03 59 35 86 16
S. Ducasse - Inria
40, avenue Halley, 
Parc Scientifique de la Haute Borne, Bât.A, Park Plaza
Villeneuve d'Ascq 59650
France

Reply via email to