-
Anton Shestakov <av6@dwimlabs.net>, Thu, 11 Aug 2016 18:59:21 +0800
pipelines: yaml was getting confused by a ':' in the two messages, drop it
-
Anton Shestakov <av6@dwimlabs.net>, Thu, 11 Aug 2016 18:48:44 +0800
pipelines: parsing the last task was getting weird, let's make it simple first
-
Anton Shestakov <av6@dwimlabs.net>, Thu, 11 Aug 2016 18:31:20 +0800
pipelines: use a folded scalar (whatever that means)
-
Anton Shestakov <av6@dwimlabs.net>, Thu, 11 Aug 2016 18:21:31 +0800
pipelines: make the second run quiet and check that nothing's changed
Using exit within current shell (i.e. `{}` instead of `()`) is an experiment.
-
Anton Shestakov <av6@dwimlabs.net>, Thu, 11 Aug 2016 18:19:01 +0800
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).
-
Anton Shestakov <av6@dwimlabs.net>, Thu, 11 Aug 2016 18:17:43 +0800
pipelines: provide inventory when checking syntax to silence warnings
-
Anton Shestakov <av6@dwimlabs.net>, Thu, 11 Aug 2016 14:14:37 +0800
pipelines: plan b: install supervisor early and restart it before ansible
-
Anton Shestakov <av6@dwimlabs.net>, Thu, 11 Aug 2016 14:06:59 +0800
pipelines: also install pip
-
Anton Shestakov <av6@dwimlabs.net>, Thu, 11 Aug 2016 14:00:28 +0800
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)
-
Anton Shestakov <av6@dwimlabs.net>, Thu, 11 Aug 2016 13:34:31 +0800
pipelines: fetch package lists first, obviously