Add configuration param to define PreReleaseTag separator

[kalmykov-sergey]

I'm trying to use SemVer as a single identifier for all build artifacts. GitVersion Babmoo plugin is a great solution for almost all cases, but unfortunately I have linux RPM+YUM-based distribution.

RPM+YUM versioning technicaly maps to SemVer abstractions (semver pre-release + build metadata = rpm release), but doesn't allow dashes in rpm-release string. Standard GitVersion config for feature branch feature/JIRA-123 generates invalid artifacts like name-1.4.3-JIRA-123.rpm. Moreover, branch feature/JIRA.123 also generates invalid rpm version. They say similar problem appears in other package managers, but i have no details.

Current behavior comes from regex replacement of [^a-zA-Z0-9] symbols with universal separator. Now this separator is hardcoded in core and has dash = - as default value. I just want to add config parameter to specify other separator, i.e. dot = .

[stale]

This issue has been automatically marked as stale because it has not had recent activity. After 30 days from now, it will be closed if no further activity occurs. Thank you for your contributions.

[rkleinman-hpe]

How do we make this unstale?

[asbjornu]

Sorry for allowing this to become stale without responding. I think this is related to what's being discussed in #2065.

[asbjornu]

As code has changed and moved a lot since this was created, the replacement being mentioned is now found here:

GitVersion/src/GitVersion.Core/Configuration/ConfigExtensions.cs

Line 138 in 34b21cb

branchName = branchName?.RegexReplace("[^a-zA-Z0-9-]", "-");

[rkleinman-hpe]

Thanks for re-opening. I have the same use case for RPM versioning for SLES/OpenSUSE-based RPMs.