• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

blue-yonder / pyscaffold / 390 / 1
94%
master: 98%

Build:
Build:
LAST BUILD BRANCH: dev
DEFAULT BRANCH: master
Ran 14 Apr 2015 12:20PM UTC
Files 8
Run time 1s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

14 Apr 2015 12:11PM UTC coverage: 94.346%. Remained the same
DISTRIB="ubuntu" PYTHON_VERSION="2.7" COVERAGE="true"

push

travis-ci

xhochy
Handle an empty GIT repository for versioning

In the case where a pyscaffold project is moved into a new, yet empty
GIT repository, git describe fails with exit 128 due to not having any
revision, i.e. there is also no HEAD.

As we cannot distinguish `git describe` failing between an empty
repository and being outside of a directory, we also execute
`git show-refs --tags` as this will succeed in a git repository with
commits and exit with exit code 1 if inside a repository with no
commits. (In case of other errors, `git show-refs --tags` will exit with
an exit code no in 0, 1 (mostly 128) so that we can distinguish the
problem here by using the exit code of the command.)

Only in this case handle the error and do the same actions as if an
invalid tag (format) was given.

534 of 566 relevant lines covered (94.35%)

0.94 hits per line

Source Files on job 390.1 (DISTRIB="ubuntu" PYTHON_VERSION="2.7" COVERAGE="true")
  • Tree
  • List 0
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 390
  • Travis Job 390.1
  • 9cd2c73e on github
  • Prev Job for DISTRIB="ubuntu" PYTHON_VERSION="2.7" COVERAGE="true" on fix-version-on-empty-repo (#375.1)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc