Skip to content

CreateOctopusRelease@6 has url encoding bug in link to created release #323

@ArturDorochowicz

Description

@ArturDorochowicz

When using CreateOctopusRelease@6 the link to the created release is incorrectly url encoded.

I have an Azure DevOps pipeline where I use CreateOctopusRelease@6 task to create a release in Octopus. When the task runs, it adds a link to the created release in the Extensions tab. If I use the task to create a release with number using SemVer with build metadata scheme, e.g. 1.2.3+test, the generated link to release in Octopus is invalid, because the + sign is incorrectly encoded in the url.

The generated, incorrect link looks like this:

<a href="[...]/deployments/releases/1.2.3 test" [...]>Release 1.2.3+test created for 'My Project'</a>

When you follow it, Octopus shows a page saying Release '1.2.3 test' for project 'My Project' was not found.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions