You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using GitVersion to generate a FullSemVer version to be used with our builds and Docker image tag, using the YML configuration and Azure DevOps tasks in pipelines to generate the version. So far the build numbers have been generated like this: 2.3.0-123-test.1 with the last part being an increment after every commit. The mode was ContinuousDeployment. This worked fine until we switched to GitFlow as branching strategy.
I started looking into it and changed the configuration to use GitFlow, which requires ContinuousDelivery mode.
The new build numbers being generated report FullSemVer version like this on a feature branch: 2.3.0-123-test.1+0
At the end, you can see after the patch version, there is the number of commits done of the branch in respect to the parent branch.
This 1+0 part though clashes with Docker, which doesn't accept strings with the + plus sign in the tag.
How is GitVersion used in conjuction with GitFlow supposed to be used when we need to generate a Docker image tag?
Do we need to use something that is not FullSemVer?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We are using GitVersion to generate a
FullSemVer
version to be used with our builds and Docker image tag, using the YML configuration and Azure DevOps tasks in pipelines to generate the version. So far the build numbers have been generated like this:2.3.0-123-test.1
with the last part being an increment after every commit. The mode wasContinuousDeployment
. This worked fine until we switched to GitFlow as branching strategy.I started looking into it and changed the configuration to use GitFlow, which requires
ContinuousDelivery
mode.The new build numbers being generated report
FullSemVer
version like this on a feature branch:2.3.0-123-test.1+0
At the end, you can see after the patch version, there is the number of commits done of the branch in respect to the parent branch.
This
1+0
part though clashes with Docker, which doesn't accept strings with the+
plus sign in the tag.How is GitVersion used in conjuction with GitFlow supposed to be used when we need to generate a Docker image tag?
Do we need to use something that is not
FullSemVer
?GitVersion.yml:
Output of gitversion command:
Beta Was this translation helpful? Give feedback.
All reactions