On Wed, 24 Jul 2013 14:52:40 +0100 James Tunnicliffe <james.tunnicli...@linaro.org> wrote:
> I am trying to get a couple of new device types into LAVA. I have a > new config file in a checkout of lava-dispatcher, which is linked in > <instance>/code/current. > > Path to code I want to run: > /srv/lava/instances/lab/code/current/local/lava-dispatcher/lava_dispatcher/default-config/lava-dispatcher/device-types/ > /srv/lava/instances/multinode/etc/lava-dispatcher/device-types/ The code expresses the range of possibilities - /etc/ dictates what you can address in the database and the database dictates what can actually be scheduled. > Running bin/buildout in /srv/lava/instances/lab/code/current/ > > The new code isn't ending up in > /srv/lava/.cache/branch-cache/lava-dispatcher/checkouts. That would be correct because the cache for lava-dispatcher would now no longer be in use. The buildout happens from your own checkout elsewhere and it is that code which executes. In my case, on multinode, I've built out lava-dispatcher for the multinode shared branch: /home/codehelp/lava-dispatcher Code changes in that directory immediately affect the next run of lava-dispatch with no other changes. Configuration changes need to happen in etc/ (and the db). -- Neil Williams ============= http://www.linux.codehelp.co.uk/
signature.asc
Description: PGP signature
_______________________________________________ linaro-validation mailing list linaro-validation@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-validation
