Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
bundletester not calling dependent make targets for make lint #15
Comments
|
A work-around is to change the dependent make target to just ".venv" (i.e., remove slashes and dashes) but that still doesn't explain why it works when manually running |
added a commit
to chuckbutler/bundletester
that referenced
this issue
Apr 2, 2015
chuckbutler
referenced this issue
Apr 2, 2015
Merged
Change the default venv behavior to false as we are using a docker image #16
|
The problem is that bundletester makes its own venv by default, which happens to be named '.venv', so from make's perspective, that target is already satisfied, and it doesn't install your deps. The way forward is to include a tests/tests.yaml containing We should probably change this default (see #16). |
tvansteenburgh
closed this
Apr 2, 2015
added a commit
to chuckbutler/flannel-docker-charm
that referenced
this issue
Apr 2, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
chuckbutler commentedApr 1, 2015
In the flannel docker charm - there is a dependent make target which installs the VENV and sets up ansible playbook linting.
The format of the Makefile is as follows:
When executing via bundletester, it does not actually fire off the dependent job of :.venv/bin/python with the output:
When executing /usr/bin/make -s lint - it does call the dependent job, and can be verified with no .venv directory present in the charm.