| 2014-04-07 21:49:35 |
David Britton |
description |
If you run tarmac like this:
tarmac -v -d lp:~user/project/branch
But tarmac thinks the branch is "lp:project" (the bzr_identity), you get confusing results. Branches get landed without any settings applied to them. Like the 'verify_command', bugresolver, commit message plugins, all don't load and pass happily appear to succeed (without doing anything).
It's even worse if the 'BRANCH_URL' is unspecified on the command line and multiple branches are used in the config, since then you can get the case where you think your config is correct (tarmac is attempting to land that branch), but it can't read any of the config settings. |
If you run tarmac like this:
tarmac -v -d lp:~user/project/branch
But tarmac thinks the branch is "lp:project" (the bzr_identity), you get confusing results. Branches get landed without any settings applied to them. Like the 'verify_command', bugresolver, commit message plugins, all don't load and happily appear to succeed (without doing anything).
It's even worse if the 'BRANCH_URL' is unspecified on the command line and multiple branches are used in the config, since then you can get the case where you think your config is correct (tarmac is attempting to land that branch), but it can't read any of the config settings. |
|
