pipelines: make the second run quiet and check that nothing's changed Using exit within current shell (i.e. `{}` instead of `()`) is an experiment.

pipelines: no need to be extra verbose on the initial run If it fails, it will print enough debug info with just one -v. Also, verbosity level 4 prints debug messages for connection, which is unlikely to be useful (it's local).

pipelines: provide inventory when checking syntax to silence warnings

pipelines: plan b: install supervisor early and restart it before ansible

pipelines: also install pip

pipelines: hitting a supervisor bug, let's see if this helps It looks like an image problem, let's try another distro. (https://github.com/Supervisor/supervisor/issues/121)

pipelines: fetch package lists first, obviously

pipelines: install sudo (for become)

pipelines: apparently multiple steps means just do the first and then fail

pipelines: write valid yaml Pipelines don't yet support multiple steps, but let's see what happens.