Variable Substitution Issue in Repository URL field with Git Repository as Script Source in Run a Script Step

[RobMcCarther]

Severity

Low

Version

2024.1 Build 3998-hotfix.4353

Latest Version

I could reproduce the problem in the latest build

What happened?

Encountering a bug where variable substitution is not functioning as expected in the Repository URL field when using a Git repository as the script source in a Run a Script step. Despite attempting to substitute variables like #{Project.AdoRepositoryUrl}, the system generates an error insisting on a valid repository URL, hindering the intended flexibility in configuration.

A valid repository URL must be specified when using a Git repository source, e.g. https://github.com/OctopusDeploy/OctopusClients.git

The Script File Path accepts variable substitution without issue

Reproduction

• Configure a Run a Script step using a Git repository as the script source.
• Define project variable for a valid git repo URL (https://github.com/OctopusDeploy/OctopusClients.git)
• Attempt to substitute variables like in the Repository URL field and save
• Encounter an error demanding a valid repository URL, despite the presence of the variable.

Error and Stacktrace

_A valid repository URL must be specified when using a Git repository source, e.g. https://github.com/OctopusDeploy/OctopusClients.git_

More Information

No response

Workaround

To enter in the Repository URL manually

[rain-on]

Release Note: Fixed issue whereby when using git-sourced scripts, an Octopus variable was considered invalid content for the repository URL; Octopus Variables can now be used for git repository urls.

[Octobob]

🎉 The fix for this issue has been released in:

Release stream	Release
2024.2	2024.2.6781
2024.3+	all releases