Skip to content
This repository was archived by the owner on Feb 19, 2020. It is now read-only.

Add --directory override to specify top level git directory.#22

Merged
machadoit merged 1 commit intoarchived-codacy:masterfrom
jkrukoff:master
Apr 22, 2016
Merged

Add --directory override to specify top level git directory.#22
machadoit merged 1 commit intoarchived-codacy:masterfrom
jkrukoff:master

Conversation

@jkrukoff
Copy link
Copy Markdown

Currently, the coverage reporter invokes git to determine the base
directory of the git repository. If CI is being run inside a docker
container, best practices include not copying the VCS information into
the container to reduce the size. However, if that advice is followed,
the coverage reporter is then unable to invoke git successfully for this
use case.

To support running without git, this adds a command line flag to
manually specify the base directory without invoking git. This has the
side benefit of allowing the coverage reporter to be useful for other
VCS systems as well.

Currently, the coverage reporter invokes git to determine the base
directory of the git repository. If CI is being run inside a docker
container, best practices include not copying the VCS information into
the container to reduce the size. However, if that advice is followed,
the coverage reporter is then unable to invoke git successfully for this
use case.

To support running without git, this adds a command line flag to
manually specify the base directory without invoking git. This has the
side benefit of allowing the coverage reporter to be useful for other
VCS systems as well.
@rtfpessoa
Copy link
Copy Markdown

LGTM 👍

@PCManticore
Copy link
Copy Markdown

Looks good to me as well.

@machadoit machadoit merged commit 18c505e into archived-codacy:master Apr 22, 2016
@machadoit
Copy link
Copy Markdown

@jkrukoff we're having some issues regarding the publish process of this new version in our build server to PyPi, will let you know when the version with your PR goes live =)

@jkrukoff
Copy link
Copy Markdown
Author

Thanks, looking forward to removing some hackery from my Dockerfile!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants