search

RiotGamesMinions / thor-scmversion

Thor tasks to manage a VERSION file based on SCM tags
MIT License
58 stars 22 forks source link

Properly handle blank slate case for 0.0.1 #3

Open ivey opened 12 years ago

Fapiko commented 11 years ago

Is this issue when using 'auto'? I just ran into an issue with this today with my jenkins job - if there are no existing tags and you're using version:bump auto it fails. Manually running a 'patch' bump on my local machine resolved the issue. If this is not the case this ticket is describing I can open a new ticket.

ivey commented 11 years ago

Yeah. The docs say you need to manually make your first tag, either with a patch or with git tag if you have existing versions. Would be nice to remove that step.

iiro commented 9 years ago

Hi,

sorry for commenting an old ticket - but I'm having an issue with Bamboo and auto-bumping. For some reason - when I run version:current it always returns 0.0.1 - although there are existing tags. The "git ls-remote" works perfectly as well.

As your readme says - I can ignore the VERSION file in CI as well - so it would be used internally by Berkshelf only when uploading etc?

iiro commented 9 years ago

Some more information:

I got into Bamboo agent host. This does not look like a permission problem between Bamboo and Stash (repository location) as I can even push things back from Bamboo.

The current version just reports: $ thor version:current 0.0.1

If I retag - things are ok then regarding Bamboo as well - until I do a new commit (SCMversion should auto-bump) and Bamboo does a new checkout with latest tags. I'm a bit puzzled...

Like this (example from you): $ git tag 1.2.3 $ git push --tags

And tags are ok: $ git tag -l 0.1.19 0.1.20 0.1.21 0.1.22 0.1.23 0.1.24 0.1.25

Any ideas are welcomed.