blocks|key|3235416|text|您正在讨论的内容更类似于像a+git+describe+would+generate这样的technical+revision+number。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3235417|这与真正的应用程序版本不同，因为它是depends+on+a+versioning+policy的，所以您仍然应该独立于Hudson进行管理。|3235418|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/1238992/branch-master-tag-revision-increments-using-git|1|https://stackoverflow.com/questions/677436/how-to-get-the-git-commit-count/677510#677510|2|https://stackoverflow.com/questions/3377655/code-version-change-rules/3377717#3377717^0|F|C|D|T|0|19|P|1|0|I|U|2|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@$9|W|A|X|1|Y]|$9|Z|A|10|1|11]]|E|$]]|$1|F|3|G|5|6|7|12|8|@]|D|@$9|13|A|14|1|15]]|E|$]]|$1|H|3|-4|5|6|7|16|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]|P|$5|K|L|M|E|$N|Q]]|R|$5|K|L|M|E|$N|S]]]]

What you are talking about is more akin to a <a href="https://stackoverflow.com/questions/677436/how-to-get-the-git-commit-count/677510#677510">technical revision number</a> like the one <a href="https://stackoverflow.com/questions/1238992/branch-master-tag-revision-increments-using-git">a <code>git describe</code> would generate</a>.

That is different from a true application version, which you should still manage independently from Hudson since it <a href="https://stackoverflow.com/questions/3377655/code-version-change-rules/3377717#3377717">depends on a versioning policy</a>.

blocks|key|3021004|text|如果你使用git插件，让Hudson提取代码，Hudson会自动标记构建。我不确定这是否会自动推送；在我们的设置中，我们做了额外的标记，并在构建脚本中包含了'git+push+--+tags‘，所以我们肯定会在中央存储库中看到Hudson标记。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3021005|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Hudson automatically tags the build, if you use the git plugin and let Hudson extract the code. I'm not sure if this gets pushed automatically; in our set up we do extra tagging and include a 'git push --tags' in our build script, so we definitely see the Hudson tags in our central repository.

blocks|key|296477|text|我写这篇文章是为了帮助增量更新标签，比如从1.0.1到1.0.2等等。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|296478|2020更新：我已经在/here下面发布了一个改进的版本。(也值得看看下面@Geoffrey的答案，关于分支的一些评论)。|offset|length|style|BOLD|296479|#!/bin/bash

#get+highest+tag+number
VERSION=`git+describe+--abbrev=0+--tags`

#replace+.+with+space+so+can+split+into+an+array
VERSION_BITS=(${VERSION//./+})

#get+number+parts+and+increase+last+one+by+1
VNUM1=${VERSION_BITS[0]}
VNUM2=${VERSION_BITS[1]}
VNUM3=${VERSION_BITS[2]}
VNUM3=$((VNUM3%2B1))

#create+new+tag
NEW_TAG="$VNUM1.$VNUM2.$VNUM3"

echo+"Updating+$VERSION+to+$NEW_TAG"

#get+current+hash+and+see+if+it+already+has+a+tag
GIT_COMMIT=`git+rev-parse+HEAD`
NEEDS_TAG=`git+describe+--contains+$GIT_COMMIT+2>/dev/null`

#only+tag+if+no+tag+already
if+[+-z+"$NEEDS_TAG"+];+then
++++git+tag+$NEW_TAG
++++echo+"Tagged+with+$NEW_TAG"
++++git+push+--tags
else
++++echo+"Already+a+tag+on+this+commit"
fi|code-block|syntax|javascript|296480|296481|6年后，我再次访问它，需要编写一个类似的脚本来上传到npm。下面的代码或here，欢迎您的评论和建议：|296482|#!/bin/bash

#+https://github.com/unegma/bash-functions/blob/main/update.sh

VERSION=""

#get+parameters
while+getopts+v:+flag
do
++case+"${flag}"+in
++++v)+VERSION=${OPTARG};;
++esac
done

#get+highest+tag+number,+and+add+1.0.0+if+doesn't+exist
CURRENT_VERSION=`git+describe+--abbrev=0+--tags+2>/dev/null`

if+[[+$CURRENT_VERSION+==+''+]]
then
++CURRENT_VERSION='1.0.0'
fi
echo+"Current+Version:+$CURRENT_VERSION"


#replace+.+with+space+so+can+split+into+an+array
CURRENT_VERSION_PARTS=(${CURRENT_VERSION//./+})

#get+number+parts
VNUM1=${CURRENT_VERSION_PARTS[0]}
VNUM2=${CURRENT_VERSION_PARTS[1]}
VNUM3=${CURRENT_VERSION_PARTS[2]}

if+[[+$VERSION+==+'major'+]]
then
++VNUM1=$((VNUM1%2B1))
elif+[[+$VERSION+==+'minor'+]]
then
++VNUM2=$((VNUM2%2B1))
elif+[[+$VERSION+==+'patch'+]]
then
++VNUM3=$((VNUM3%2B1))
else
++echo+"No+version+type+(https://semver.org/)+or+incorrect+type+specified,+try:+-v+[major,+minor,+patch]"
++exit+1
fi


#create+new+tag
NEW_TAG="$VNUM1.$VNUM2.$VNUM3"
echo+"($VERSION)+updating+$CURRENT_VERSION+to+$NEW_TAG"

#get+current+hash+and+see+if+it+already+has+a+tag
GIT_COMMIT=`git+rev-parse+HEAD`
NEEDS_TAG=`git+describe+--contains+$GIT_COMMIT+2>/dev/null`

#only+tag+if+no+tag+already
#to+publish,+need+to+be+logged+in+to+npm,+and+with+clean+working+directory:+`npm+login;+git+stash`
if+[+-z+"$NEEDS_TAG"+];+then
++npm+version+$NEW_TAG
++npm+publish+--access+public
++echo+"Tagged+with+$NEW_TAG"
++git+push+--tags
++git+push
else
++echo+"Already+a+tag+on+this+commit"
fi

exit+0|296483|备注:这不适用于zsh，因为(首先)，zsh不使用0索引数组。|296484|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/unegma/bash-functions/blob/main/update.sh|1^0|0|0|6|C|4|0|0|0|0|10|4|1|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@$D|14|E|15|F|G]]|9|@$D|16|E|17|1|18]]|A|$]]|$1|H|3|I|5|J|7|19|8|@]|9|@]|A|$K|L]]|$1|M|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1B|8|@]|9|@$D|1C|E|1D|1|1E]]|A|$]]|$1|P|3|Q|5|J|7|1F|8|@]|9|@]|A|$K|L]]|$1|R|3|S|5|6|7|1G|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]]|U|$V|$5|W|X|Y|A|$Z|10]]|11|$5|W|X|Y|A|$Z|10]]]]

I wrote this to help with updating tags incrementally e.g. 1.0.1 to 1.0.2 etc.
2020 update: I have posted an improved version beneath/<a href="https://github.com/unegma/bash-functions/blob/main/update.sh" rel="noreferrer">here</a>. (Also worth seeing @Geoffrey's answer below for some comments on branching).
<pre><code>#!/bin/bash

#get highest tag number
VERSION=`git describe --abbrev=0 --tags`

#replace . with space so can split into an array
VERSION_BITS=(${VERSION//./ })

#get number parts and increase last one by 1
VNUM1=${VERSION_BITS[0]}
VNUM2=${VERSION_BITS[1]}
VNUM3=${VERSION_BITS[2]}
VNUM3=$((VNUM3+1))

#create new tag
NEW_TAG=&quot;$VNUM1.$VNUM2.$VNUM3&quot;

echo &quot;Updating $VERSION to $NEW_TAG&quot;

#get current hash and see if it already has a tag
GIT_COMMIT=`git rev-parse HEAD`
NEEDS_TAG=`git describe --contains $GIT_COMMIT 2&gt;/dev/null`

#only tag if no tag already
if [ -z &quot;$NEEDS_TAG&quot; ]; then
 git tag $NEW_TAG
 echo &quot;Tagged with $NEW_TAG&quot;
 git push --tags
else
 echo &quot;Already a tag on this commit&quot;
fi
</code></pre>
<hr />
I revisit this 6 years later needing to write a similar script for uploading to npm. Code below or <a href="https://github.com/unegma/bash-functions/blob/main/update.sh" rel="noreferrer">here</a>, comments and suggestions appreciated and welcome:
<pre><code>#!/bin/bash

# https://github.com/unegma/bash-functions/blob/main/update.sh

VERSION=&quot;&quot;

#get parameters
while getopts v: flag
do
 case &quot;${flag}&quot; in
 v) VERSION=${OPTARG};;
 esac
done

#get highest tag number, and add 1.0.0 if doesn't exist
CURRENT_VERSION=`git describe --abbrev=0 --tags 2&gt;/dev/null`

if [[ $CURRENT_VERSION == '' ]]
then
 CURRENT_VERSION='1.0.0'
fi
echo &quot;Current Version: $CURRENT_VERSION&quot;


#replace . with space so can split into an array
CURRENT_VERSION_PARTS=(${CURRENT_VERSION//./ })

#get number parts
VNUM1=${CURRENT_VERSION_PARTS[0]}
VNUM2=${CURRENT_VERSION_PARTS[1]}
VNUM3=${CURRENT_VERSION_PARTS[2]}

if [[ $VERSION == 'major' ]]
then
 VNUM1=$((VNUM1+1))
elif [[ $VERSION == 'minor' ]]
then
 VNUM2=$((VNUM2+1))
elif [[ $VERSION == 'patch' ]]
then
 VNUM3=$((VNUM3+1))
else
 echo &quot;No version type (https://semver.org/) or incorrect type specified, try: -v [major, minor, patch]&quot;
 exit 1
fi


#create new tag
NEW_TAG=&quot;$VNUM1.$VNUM2.$VNUM3&quot;
echo &quot;($VERSION) updating $CURRENT_VERSION to $NEW_TAG&quot;

#get current hash and see if it already has a tag
GIT_COMMIT=`git rev-parse HEAD`
NEEDS_TAG=`git describe --contains $GIT_COMMIT 2&gt;/dev/null`

#only tag if no tag already
#to publish, need to be logged in to npm, and with clean working directory: `npm login; git stash`
if [ -z &quot;$NEEDS_TAG&quot; ]; then
 npm version $NEW_TAG
 npm publish --access public
 echo &quot;Tagged with $NEW_TAG&quot;
 git push --tags
 git push
else
 echo &quot;Already a tag on this commit&quot;
fi

exit 0

</code></pre>
Subnote: this won't work with zsh as (for one), zsh doesn't use 0 indexed arrays.

blocks|key|293978|text|非常好的解决方案timhc22唯一的一件事是它需要最后一个标签(无论分支是什么)，如果你在一个有多个分支的项目上工作，你可能会有问题。我只是提议改进一下你的基地。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|293979|#!/bin/sh

#+retrieve+branch+name
BRANCH_NAME=$(git+branch+%7C+sed+-n+'/\*+/s///p')

#+remove+prefix+release
REGEXP_RELEASE="release\/"
VERSION_BRANCH=$(echo+"$BRANCH_NAME"+%7C+sed+"s/$REGEXP_RELEASE//")+

echo+"Current+version+branch+is+$VERSION_BRANCH"

#+retrieve+the+last+commit+on+the+branch
VERSION=$(git+describe+--tags+--match=$VERSION_BRANCH*+--abbrev=0)

#+split+into+array
VERSION_BITS=(${VERSION//./+})

#get+number+parts+and+increase+last+one+by+1
VNUM1=${VERSION_BITS[0]}
VNUM2=${VERSION_BITS[1]}
VNUM3=${VERSION_BITS[2]}
VNUM3=$((VNUM3%2B1))

#create+new+tag
NEW_TAG="$VNUM1.$VNUM2.$VNUM3"

echo+"Updating+$VERSION+to+$NEW_TAG"

#get+current+hash+and+see+if+it+already+has+a+tag
GIT_COMMIT=`git+rev-parse+HEAD`
NEEDS_TAG=`git+describe+--contains+$GIT_COMMIT`

#only+tag+if+no+tag+already+(would+be+better+if+the+git+describe+command+above+could+have+a+silent+option)
if+[+-z+"$NEEDS_TAG"+];+then
++++echo+"Tagged+with+$NEW_TAG+(Ignoring+fatal:cannot+describe+-+this+means+commit+is+untagged)+"
++++git+tag+$NEW_TAG
++++git+push+--tags
else
++++echo+"Already+a+tag+on+this+commit"
fi|code-block|syntax|javascript|293980|例如，如果您有以下条件，则可以执行此操作：|293981|创建主分支:将创建|293982|-X.Y.Z|unordered-list-item|293983|a版本/X.Y:将创建X.Y.Z|293984|293985|无论如何，非常感谢它给了我很大的帮助。|293986|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|X|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|Y|8|@]|9|@]|A|$]]|$1|N|3|O|5|M|7|Z|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|11|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

Really good solution timhc22
The only thing is that it takes the last tag (whatever the branch)
If you work on a project with multiple branches you could have an issue.
I proposed just an improvement with your base.

<pre><code>#!/bin/sh

# retrieve branch name
BRANCH_NAME=$(git branch | sed -n '/\* /s///p')

# remove prefix release
REGEXP_RELEASE="release\/"
VERSION_BRANCH=$(echo "$BRANCH_NAME" | sed "s/$REGEXP_RELEASE//") 

echo "Current version branch is $VERSION_BRANCH"

# retrieve the last commit on the branch
VERSION=$(git describe --tags --match=$VERSION_BRANCH* --abbrev=0)

# split into array
VERSION_BITS=(${VERSION//./ })

#get number parts and increase last one by 1
VNUM1=${VERSION_BITS[0]}
VNUM2=${VERSION_BITS[1]}
VNUM3=${VERSION_BITS[2]}
VNUM3=$((VNUM3+1))

#create new tag
NEW_TAG="$VNUM1.$VNUM2.$VNUM3"

echo "Updating $VERSION to $NEW_TAG"

#get current hash and see if it already has a tag
GIT_COMMIT=`git rev-parse HEAD`
NEEDS_TAG=`git describe --contains $GIT_COMMIT`

#only tag if no tag already (would be better if the git describe command above could have a silent option)
if [ -z "$NEEDS_TAG" ]; then
 echo "Tagged with $NEW_TAG (Ignoring fatal:cannot describe - this means commit is untagged) "
 git tag $NEW_TAG
 git push --tags
else
 echo "Already a tag on this commit"
fi
</code></pre>

This works for example if you have:

<ul>
<li>a master branch: will create master-X.Y.Z</li>
<li>a release/X.Y: will create X.Y.Z</li>
</ul>

In any case thanks a lot it helped me a lot.

blocks|key|297039|text|我的用法如下。它可以很好地与分支一起工作。下面的代码片段来自上面的评论和gitversion+/+semver.org。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|297040|#!/bin/sh

#+This+script+will+be+executed+after+commit+in+placed+in+.git/hooks/post-commit

#+Semantic+Versioning+2.0.0+guideline
#+
#+Given+a+version+number+MAJOR.MINOR.PATCH,+increment+the:
#+MAJOR+version+when+you+make+incompatible+API+changes,
#+MINOR+version+when+you+add+functionality+in+a+backwards-compatible+manner,+and
#+PATCH+version+when+you+make+backwards-compatible+bug+fixes.

echo+"Starting+the+taging+process+based+on+commit+message+%2Bsemver:+xxxxx"

#get+highest+tags+across+all+branches,+not+just+the+current+branch
VERSION=`git+describe+--tags+$(git+rev-list+--tags+--max-count=1)`

#+split+into+array
VERSION_BITS=(${VERSION//./+})

echo+"Latest+version+tag:+$VERSION"

#get+number+parts+and+increase+last+one+by+1
VNUM1=${VERSION_BITS[0]}
VNUM2=${VERSION_BITS[1]}
VNUM3=${VERSION_BITS[2]}
#+VNUM3=$((VNUM3%2B1))

#+Taken+from+gitversion
#+major-version-bump-message:+'\%2Bsemver:\s?(breaking%7Cmajor)'
#+minor-version-bump-message:+'\%2Bsemver:\s?(feature%7Cminor)'
#+patch-version-bump-message:+'\%2Bsemver:\s?(fix%7Cpatch)'
#+get+last+commit+message+and+extract+the+count+for+"semver:+(major%7Cminor%7Cpatch)"
COUNT_OF_COMMIT_MSG_HAVE_SEMVER_MAJOR=`git+log+-1+--pretty=%25B+%7C+egrep+-c+'\%2Bsemver:\s?(breaking%7Cmajor)'`
COUNT_OF_COMMIT_MSG_HAVE_SEMVER_MINOR=`git+log+-1+--pretty=%25B+%7C+egrep+-c+'\%2Bsemver:\s?(feature%7Cminor)'`
COUNT_OF_COMMIT_MSG_HAVE_SEMVER_PATCH=`git+log+-1+--pretty=%25B+%7C+egrep+-c+'\%2Bsemver:\s?(fix%7Cpatch)'`

if+[+$COUNT_OF_COMMIT_MSG_HAVE_SEMVER_MAJOR+-gt+0+];+then
++++VNUM1=$((VNUM1%2B1))+
fi
if+[+$COUNT_OF_COMMIT_MSG_HAVE_SEMVER_MINOR+-gt+0+];+then
++++VNUM2=$((VNUM2%2B1))+
fi
if+[+$COUNT_OF_COMMIT_MSG_HAVE_SEMVER_PATCH+-gt+0+];+then
++++VNUM3=$((VNUM3%2B1))+
fi

#+count+all+commits+for+a+branch
GIT_COMMIT_COUNT=`git+rev-list+--count+HEAD`
echo+"Commit+count:+$GIT_COMMIT_COUNT"+
export+BUILD_NUMBER=$GIT_COMMIT_COUNT

#create+new+tag
NEW_TAG="$VNUM1.$VNUM2.$VNUM3"

echo+"Updating+$VERSION+to+$NEW_TAG"

#only+tag+if+commit+message+have+version-bump-message+as+mentioned+above
if+[+$COUNT_OF_COMMIT_MSG_HAVE_SEMVER_MAJOR+-gt+0+]+%7C%7C++[+$COUNT_OF_COMMIT_MSG_HAVE_SEMVER_MINOR+-gt+0+]+%7C%7C+[+$COUNT_OF_COMMIT_MSG_HAVE_SEMVER_PATCH+-gt+0+];+then
++++echo+"Tagged+with+$NEW_TAG+(Ignoring+fatal:cannot+describe+-+this+means+commit+is+untagged)+"
++++git+tag+"$NEW_TAG"
else
++++echo+"Already+a+tag+on+this+commit"
fi|code-block|syntax|javascript|297041|entityMap|0|LINK|mutability|MUTABLE|url|http://gitversion.readthedocs.io/|1|http://semver.org/^0|10|A|0|1D|A|1|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]|$A|W|B|X|1|Y]]|C|$]]|$1|D|3|E|5|F|7|Z|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|10|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]|Q|$5|L|M|N|C|$O|R]]]]

I am using as below. It is working perfectly with branches. Below snippets inspired from above comments and the <a href="http://gitversion.readthedocs.io/" rel="nofollow noreferrer">gitversion</a> / <a href="http://semver.org/" rel="nofollow noreferrer">semver.org</a>.

<pre><code>#!/bin/sh

# This script will be executed after commit in placed in .git/hooks/post-commit

# Semantic Versioning 2.0.0 guideline
# 
# Given a version number MAJOR.MINOR.PATCH, increment the:
# MAJOR version when you make incompatible API changes,
# MINOR version when you add functionality in a backwards-compatible manner, and
# PATCH version when you make backwards-compatible bug fixes.

echo "Starting the taging process based on commit message +semver: xxxxx"

#get highest tags across all branches, not just the current branch
VERSION=`git describe --tags $(git rev-list --tags --max-count=1)`

# split into array
VERSION_BITS=(${VERSION//./ })

echo "Latest version tag: $VERSION"

#get number parts and increase last one by 1
VNUM1=${VERSION_BITS[0]}
VNUM2=${VERSION_BITS[1]}
VNUM3=${VERSION_BITS[2]}
# VNUM3=$((VNUM3+1))

# Taken from gitversion
# major-version-bump-message: '\+semver:\s?(breaking|major)'
# minor-version-bump-message: '\+semver:\s?(feature|minor)'
# patch-version-bump-message: '\+semver:\s?(fix|patch)'
# get last commit message and extract the count for "semver: (major|minor|patch)"
COUNT_OF_COMMIT_MSG_HAVE_SEMVER_MAJOR=`git log -1 --pretty=%B | egrep -c '\+semver:\s?(breaking|major)'`
COUNT_OF_COMMIT_MSG_HAVE_SEMVER_MINOR=`git log -1 --pretty=%B | egrep -c '\+semver:\s?(feature|minor)'`
COUNT_OF_COMMIT_MSG_HAVE_SEMVER_PATCH=`git log -1 --pretty=%B | egrep -c '\+semver:\s?(fix|patch)'`

if [ $COUNT_OF_COMMIT_MSG_HAVE_SEMVER_MAJOR -gt 0 ]; then
 VNUM1=$((VNUM1+1)) 
fi
if [ $COUNT_OF_COMMIT_MSG_HAVE_SEMVER_MINOR -gt 0 ]; then
 VNUM2=$((VNUM2+1)) 
fi
if [ $COUNT_OF_COMMIT_MSG_HAVE_SEMVER_PATCH -gt 0 ]; then
 VNUM3=$((VNUM3+1)) 
fi

# count all commits for a branch
GIT_COMMIT_COUNT=`git rev-list --count HEAD`
echo "Commit count: $GIT_COMMIT_COUNT" 
export BUILD_NUMBER=$GIT_COMMIT_COUNT

#create new tag
NEW_TAG="$VNUM1.$VNUM2.$VNUM3"

echo "Updating $VERSION to $NEW_TAG"

#only tag if commit message have version-bump-message as mentioned above
if [ $COUNT_OF_COMMIT_MSG_HAVE_SEMVER_MAJOR -gt 0 ] || [ $COUNT_OF_COMMIT_MSG_HAVE_SEMVER_MINOR -gt 0 ] || [ $COUNT_OF_COMMIT_MSG_HAVE_SEMVER_PATCH -gt 0 ]; then
 echo "Tagged with $NEW_TAG (Ignoring fatal:cannot describe - this means commit is untagged) "
 git tag "$NEW_TAG"
else
 echo "Already a tag on this commit"
fi
</code></pre>

blocks|key|3021145|text|如果您需要Posix版本，则回答几乎与上面相同|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3021146|#!/bin/sh

#Get+the+highest+tag+number
VERSION=`git+describe+--abbrev=0+--tags`
VERSION=${VERSION:-'0.0.0'}

#Get+number+parts
MAJOR="${VERSION%25%25.*}";+VERSION="${VERSION#*.}"
MINOR="${VERSION%25%25.*}";+VERSION="${VERSION#*.}"
PATCH="${VERSION%25%25.*}";+VERSION="${VERSION#*.}"

#Increase+version
PATCH=$((PATCH%2B1))

#Get+current+hash+and+see+if+it+already+has+a+tag
GIT_COMMIT=`git+rev-parse+HEAD`
NEEDS_TAG=`git+describe+--contains+$GIT_COMMIT`

#Create+new+tag
NEW_TAG="$MAJOR.$MINOR.$PATCH"
echo+"Updating+to+$NEW_TAG"

#Only+tag+if+no+tag+already+(would+be+better+if+the+git+describe+command+above+could+have+a+silent+option)
if+[+-z+"$NEEDS_TAG"+];+then
++++echo+"Tagged+with+$NEW_TAG+(Ignoring+fatal:cannot+describe+-+this+means+commit+is+untagged)+"
++++git+tag+$NEW_TAG
else
++++echo+"Already+a+tag+on+this+commit"
fi|code-block|syntax|javascript|3021147|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

In case if you will need Posix version, almost the same as above answer

<pre><code>#!/bin/sh

#Get the highest tag number
VERSION=`git describe --abbrev=0 --tags`
VERSION=${VERSION:-'0.0.0'}

#Get number parts
MAJOR="${VERSION%%.*}"; VERSION="${VERSION#*.}"
MINOR="${VERSION%%.*}"; VERSION="${VERSION#*.}"
PATCH="${VERSION%%.*}"; VERSION="${VERSION#*.}"

#Increase version
PATCH=$((PATCH+1))

#Get current hash and see if it already has a tag
GIT_COMMIT=`git rev-parse HEAD`
NEEDS_TAG=`git describe --contains $GIT_COMMIT`

#Create new tag
NEW_TAG="$MAJOR.$MINOR.$PATCH"
echo "Updating to $NEW_TAG"

#Only tag if no tag already (would be better if the git describe command above could have a silent option)
if [ -z "$NEEDS_TAG" ]; then
 echo "Tagged with $NEW_TAG (Ignoring fatal:cannot describe - this means commit is untagged) "
 git tag $NEW_TAG
else
 echo "Already a tag on this commit"
fi
</code></pre>

blocks|key|299087|text|很好的解决方案。我可以建议使用带注释的标签来表示版本吗？像这样：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|299088|git+tag+-a+"$NEW_TAG"++-m+"autogenerated"|code-block|syntax|javascript|299089|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

good solution. my i suggest using annotated tags to represent a release? like:

<pre><code>git tag -a "$NEW_TAG" -m "autogenerated"
</code></pre>

blocks|key|3021190|text|基于timhc22应答，但稍作修改以处理初始标记，并在提交时不存在标记的情况下静默输出错误|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3021191|#!/bin/bash

#get+highest+tag+number
VERSION=`git+describe+--abbrev=0+--tags+2>/dev/null`

if+[+-z+$VERSION+];then
++++NEW_TAG="1.0.0"
++++echo+"No+tag+present."
++++echo+"Creating+tag:+$NEW_TAG"
++++git+tag+$NEW_TAG
++++git+push+--tags
++++echo+"Tag+created+and+pushed:+$NEW_TAG"
++++exit+0;
fi

#replace+.+with+space+so+can+split+into+an+array
VERSION_BITS=(${VERSION//./+})

#get+number+parts+and+increase+last+one+by+1
VNUM1=${VERSION_BITS[0]}
VNUM2=${VERSION_BITS[1]}
VNUM3=${VERSION_BITS[2]}
VNUM3=$((VNUM3%2B1))

#create+new+tag
NEW_TAG="${VNUM1}.${VNUM2}.${VNUM3}"

#get+current+hash+and+see+if+it+already+has+a+tag
GIT_COMMIT=`git+rev-parse+HEAD`
CURRENT_COMMIT_TAG=`git+describe+--contains+$GIT_COMMIT+2>/dev/null`

#only+tag+if+no+tag+already+(would+be+better+if+the+git+describe+command+above+could+have+a+silent+option)
if+[+-z+"$CURRENT_COMMIT_TAG"+];+then
++++echo+"Updating+$VERSION+to+$NEW_TAG"
++++git+tag+$NEW_TAG
++++git+push+--tags
++++echo+"Tag+created+and+pushed:+$NEW_TAG"
else
++++echo+"This+commit+is+already+tagged+as:+$CURRENT_COMMIT_TAG"
fi|code-block|syntax|javascript|3021192|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

based on timhc22 answer, but slightly modified to handle initial tagging, and silence output errors in case of no tag is present on commit

<pre><code>#!/bin/bash

#get highest tag number
VERSION=`git describe --abbrev=0 --tags 2&gt;/dev/null`

if [ -z $VERSION ];then
 NEW_TAG="1.0.0"
 echo "No tag present."
 echo "Creating tag: $NEW_TAG"
 git tag $NEW_TAG
 git push --tags
 echo "Tag created and pushed: $NEW_TAG"
 exit 0;
fi

#replace . with space so can split into an array
VERSION_BITS=(${VERSION//./ })

#get number parts and increase last one by 1
VNUM1=${VERSION_BITS[0]}
VNUM2=${VERSION_BITS[1]}
VNUM3=${VERSION_BITS[2]}
VNUM3=$((VNUM3+1))

#create new tag
NEW_TAG="${VNUM1}.${VNUM2}.${VNUM3}"

#get current hash and see if it already has a tag
GIT_COMMIT=`git rev-parse HEAD`
CURRENT_COMMIT_TAG=`git describe --contains $GIT_COMMIT 2&gt;/dev/null`

#only tag if no tag already (would be better if the git describe command above could have a silent option)
if [ -z "$CURRENT_COMMIT_TAG" ]; then
 echo "Updating $VERSION to $NEW_TAG"
 git tag $NEW_TAG
 git push --tags
 echo "Tag created and pushed: $NEW_TAG"
else
 echo "This commit is already tagged as: $CURRENT_COMMIT_TAG"
fi
</code></pre>

blocks|key|3021207|text|希望这能有所帮助|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3021208|#!/bin/bash

RES=$(git+show-ref+--tags)
if+[+-z+"$RES"+];+then
++++NEW_TAG="v1.0.0"
else
++++LATEST_TAG=$(git+describe+--tags+--abbrev=0)
++++IFS='.'+read+-r+-a+array+<<<+${LATEST_TAG:1}
++++one=${array[0]}
++++two=${array[1]}
++++three=${array[2]}

++++if+[+"$three"+==+"999"+];+then
++++++++if+[+"$two"+==+"999"+];+then
++++++++++++three=0
++++++++++++two=0
++++++++++++((one%2B%2B))
++++++++else
++++++++++++((two%2B%2B))
++++++++++++three=0
++++++++fi
++++elif+[+"$two"+==+"999"+]+&&+[+"$three"+==+"999"+];+then
++++++++((one%2B%2B))
++++++++two=0
++++else
++++++++((three%2B%2B))
++++fi

++++NEW_TAG="v${one}.${two}.${three}"
fi

git+tag+$NEW_TAG+-a+"autogenerated+tag"
git+push+origin+$NEW_TAG|code-block|syntax|javascript|3021209|或者，如果您只想递增标记的最后一部分，请使用以下命令|3021210|#!/bin/bash

RES=$(git+show-ref+--tags)
if+[+-z+"$RES"+];+then
++++NEW_TAG=v1.0.0
else
++++NEW_TAG=$(git+describe+--tags+--abbrev=0+%7C+awk+-F.+'{OFS=".";+$NF%2B=1;+print+$0}')
fi

git+tag+$NEW_TAG+-a+"autogenerated+tag"
git+push+origin+$NEW_TAG|3021211|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Hope this will help
<pre><code>#!/bin/bash

RES=$(git show-ref --tags)
if [ -z &quot;$RES&quot; ]; then
 NEW_TAG=&quot;v1.0.0&quot;
else
 LATEST_TAG=$(git describe --tags --abbrev=0)
 IFS='.' read -r -a array &lt;&lt;&lt; ${LATEST_TAG:1}
 one=${array[0]}
 two=${array[1]}
 three=${array[2]}

 if [ &quot;$three&quot; == &quot;999&quot; ]; then
 if [ &quot;$two&quot; == &quot;999&quot; ]; then
 three=0
 two=0
 ((one++))
 else
 ((two++))
 three=0
 fi
 elif [ &quot;$two&quot; == &quot;999&quot; ] &amp;&amp; [ &quot;$three&quot; == &quot;999&quot; ]; then
 ((one++))
 two=0
 else
 ((three++))
 fi

 NEW_TAG=&quot;v${one}.${two}.${three}&quot;
fi

git tag $NEW_TAG -a &quot;autogenerated tag&quot;
git push origin $NEW_TAG
</code></pre>
or else if you want to increment only last part of the tag, use this
<pre><code>#!/bin/bash

RES=$(git show-ref --tags)
if [ -z &quot;$RES&quot; ]; then
 NEW_TAG=v1.0.0
else
 NEW_TAG=$(git describe --tags --abbrev=0 | awk -F. '{OFS=&quot;.&quot;; $NF+=1; print $0}')
fi

git tag $NEW_TAG -a &quot;autogenerated tag&quot;
git push origin $NEW_TAG
</code></pre>

How do you tag your release versions in git?

Now I have each release identified by build number, but they increment even if there are no changes in the repo. My idea is to have it generated automatically on successful deployment on staging server. E.g.

<ul>
<li>run Hudson build</li>
<li>when successful, add new tag, i.e. 1.0-1</li>
<li>on next successful build add next tag, 1.0-2</li>
<li>version tag is displayed then in site footer</li>
</ul>

This would require:

<ul>
<li>Hudson to manage next version numbers</li>
<li>or script to store last tag in some file</li>
<li>or parse git tags to determine last</li>
</ul>

Any tips?

Automatic tagging of releases

服务器

如何在git中标记您的发布版本？现在，我已经通过内部版本号标识了每个版本，但即使在repo中没有任何更改，它们也会增加。我的想法是在登台服务器上成功部署时自动生成它。例如。运行Hudson build 成功后，添加新标记，即1.0-1on next成功构建添加下一个标记，1.0-2version标记显示，然后显示在站点...

问版本的自动标记
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问版本的自动标记EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问版本的自动标记
EN