OctoLintProjectReleaseTemplate

OctoLintProjectReleaseTemplate returns a warning if any project has a release versioning template set incorrectly, according to a specified regular expression.

Recommendation

We recommend using SemVer as the versioning scheme for releases in Octopus.

You can use variables from the project (un-scoped or scoped only to a channel). In addition, some special variables are provided. For example:

1.2.#{Octopus.Version.NextPatch}-pre

These special variables take the form:

Octopus.Version.(Last|Next)(Major|Minor|Patch|Build|Revision|Suffix)

If you are using channels, channel-specific special variables are also available:

Octopus.Version.Channel.(Last|Next)(Major|Minor|Patch|Build|Revision|Suffix)

Version components from other channels in the project can be referenced using the channel name as the index:

Octopus.Version.Channel[ChannelName].(Last|Next)(Major|Minor|Patch|Build|Revision|Suffix)

The channel name can also be used (generally as part of the suffix):

Octopus.Release.Channel.Name

The version can also include Octopus semantic version mask characters i and c referring to the incremented and current values of the version, respectively. For example:

2.1.c.i

Finally, date fields can be also be used, for example:

#{Octopus.Date.Year}.#{Octopus.Date.Month}.#{Octopus.Date.Day}

These take the form:

Octopus.Date.(Day|Month|Year|DayOfYear)
Octopus.Time.(Hour|Minute|Second)

Remediation

Consider changing the project's release versioning strategy template to a valid one according to your convention.