Skip to content

Commit

Permalink
🤦‍♀️ Dot between build ID and commit on Azure Pipelines (#113)
Browse files Browse the repository at this point in the history
#### Summary:
Need a "." between build number and commit, not a plus

#### Motivation:
Use non-tagged templates built by Azure

##### References (optional):
purduesigbots/pros-cli#66
purduesigbots/pros-cli#64

#### Test Plan:
- [x] Can fetch/use template built locally
- [x] Can fetch/use template built on Azure


#### Commits:
* dot between build number and commit

* Dots are better in general
  • Loading branch information
edjubuh authored Feb 17, 2019
1 parent 728dcb1 commit 47b06f0
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions version.py
Original file line number Diff line number Diff line change
Expand Up @@ -16,8 +16,8 @@
# pippre = 'alpha' if v.endswith('-dirty') else 'pre'
build = subprocess.check_output(['git', 'rev-parse', '--short', 'HEAD']).decode().strip()
number_since = subprocess.check_output(['git', 'rev-list', v[:v.index('-')] + '..HEAD', '--count']).decode().strip()
build = "{}+{}".format(number_since, build)
semver = bv + '-' + sempre + '+' + build
build = "{}.{}".format(number_since, build)
semver = bv + '-' + sempre + '.' + build
else:
semver = v

Expand Down

0 comments on commit 47b06f0

Please sign in to comment.