Hi! I continue to make updates on RakuDist project aimed to automate a process of testing Raku modules.

Here is a couple of interesting features I have added recently.

Enter Travis CI integration and post deployemt checks.

Travis CI

If one need to run RakuDist through Travis CI it’s as simple as that:

language: minimal script: - curl http://repo.westus.cloudapp.azure.com/rakudist/api/run/$os/$author/$module -s | bash

Where:

$os – tested OS name, for example `debian`

$author – github(*) login

$module – module name

(*) – RakuDist supports GitLab projects as well I just need to write a proper helper for that.

Post deployment scenarios

Quite often Raku modules distributions include scripts that are part of an installation process.

RakuDist allows to test such a scripts at post deployment phase:

nano smokefile:

bash 'your-script', %( user => config()<user>, expect_stdout => 'this string should be in a script output' );

You could see more sophisticated and interesting examples here.

I would like to hear from Raku modules authors if this feature is useful.

—

That’s all for @today, stay tuned!