[Feature Request]: Custom Versioning Strategy #1596
AlexanderRichter
started this conversation in
Ideas
Replies: 1 comment
-
|
The VersioningStrategy is mostly determining the Build and Revision part of the build number, currently supporting 2 modes: 1: RUN_NUMBER.RUN_ATTEMPT In IncrementVersionNumber it is only used to determine whether you want to use the same version number for all projects. Not sure there are enough different versioningstrategies to justify making it overridable - but maybe you can describe how you would like versioning to work? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
The VersioningStrategy allows do choose between different Versioning strategies.
It would be great to have the chance to also use a custom Versioning Strategy as another option.
My idea is to define a path and in the al-go settings to the custom powershell which would then basically override the logic from
IncrementVersionNumber
Beta Was this translation helpful? Give feedback.
All reactions