ScriptRepository Script execution doesn't seem to respect defaults

[Damian Reeves]

When I execute a script I have stored in the Script Repository, if I set defaults for its parameters (either using constants or BuildMaster variables), it does not seem to pass those values through to the script and I am forced to specify values even if all I want are the default values.

This seems like it is a bug.

Product: BuildMaster
Version: 4.2.7

[Tod]

Thanks for the report - I was able to reproduce the issue, and have logged the issue as BM-1501.

[Dave Genthe]

Is there a date when this will be resolved?
Even if I wanted to use the script repository as a template I can't change the script text after selecting one of the actions from the repository.
I have a Linux script using three different Build Master variable scopes. None of the variables are used.

Script parameter: DeploymentPath
Script parameter: DeploymentMainFile
Server variable: DeploymentScripts
BuildMaster functions: ApplicationName, ReleaseNumber, BuildNumber

Script text:

#!/bin/bash
. $$HOME/.bash_profile
$$HOME/prepare_sql_files.sh ${DeploymentScripts}/${ApplicationName}/${ReleaseNumber}/${BuildNumber}/${DeploymentPath}/${DeploymentMainFile}

[Tod]

As far as I'm aware, this particular issue has already been resolved. Can you post a new question with the same details? For some quick suggestions though, does echo $ApplicationName work as expected? Is the application configuration to use new variable support (Settings -> Application Settings)?