CI script

[robertodr]

The CI script is very simple-minded. Things to improve:

1. The report dumps all info to screen. Should we agree on a less cluttered output format? EDIT I have also noticed that non-STATUS messages from CMake are printed elsewhere from where you'd expect (separate from the CMake configuration output stream) I suspect CMake might use the stderr instead of stdout for these.
2. Some of the failing builds, fail the whole CI. But maybe we want to show that some stuff doesn't work. How can we implement an "expected failure" behavior?
3. It would be good to move the environment variables inside the various subdirectories. I think this will contribute to have cleaner build matrices on the CI services. I have played around with direnv to no avail. Maybe I can get you up to speed with what I've done, before we decide the next steps.

[bast]

All 3 suggestions sound good. Indeed I need to get a bit up to speed first. I will look around in the scripts to get a grasp and then return to this discussion.

[robertodr]

It works for now, but it could be better. I opened the issue as a reminder to self 😉 A couple more ideas:

• direnv is great, but it won't work on CI services, or it's too much effort to make it work.
• I think the easy way out is to have a YAML file in each directory that lists stuff like environment variables. Then in the inner loop of the script, the YAML is parsed and its contentes passed on to subprocess.Popen

[bast]

I like the yaml idea :-) I start working on the recipes/book this weekend.

[robertodr]

I think it is necessary to do this to get meaningful recipes. For example, I can't modify the compiler for just one recipe with -DCMAKE_<LANG>_COMPILER=blabla without doing so for all recipes. If you can do a first pass, I would be grateful (time will be a bit tight for me in the next couple of weeks)

[bast]

I will implement this. Now it's my turn to also do something.

[bast]

1. done (PR not submitted yet but soon)
2. split out to own issue: Implement expected failure functionality in CI #33
3. to be done (once it is done will file a PR)