Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version is not always derived from a tag in Travis CI #81

Closed
2m opened this issue Nov 6, 2018 · 0 comments
Closed

Version is not always derived from a tag in Travis CI #81

2m opened this issue Nov 6, 2018 · 0 comments
Assignees

Comments

@2m
Copy link
Member

2m commented Nov 6, 2018

As a default, Travis CI fetches only 50 last commits when it checks out repository before the build.

If the last tag is more than 50 commits old then sbt-dynver falls back to having only the short commit sha as the version name, like 50-aee9ebeb. This is problematic when releasing snapshots from Travis.

Also previousStableVersion becomes None. This, with combination with MiMa, might end up in a situation where no BC checks are being run.

Currently the workaround is to fetch full history in the before_install section of Travis configuration:

before_install:
  - git fetch --unshallow

It would be great to have a setting in sbt-dynver which would prevent versions being derived if no tags are present.

@2m 2m changed the title Settings are not always populated in Travis CI Version is not always derived from a tag in Travis CI Nov 6, 2018
@dwijnand dwijnand self-assigned this Jan 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants