I have found that once I'm using Specs to manage a build or deployment plan, I can no longer edit any of the contents of that build plan or deployment plan.
However, one thing you could try is, knowing that variables in a Deployment plan inherit the variables in the Build plan that it's based on. If that build plan isn't managed by specs, you can create another variable in that build plan. If your Build Plan is also managed by specs, the Build Project that contains the Build Plan can also have "Project Variables" that are ultimately inherited by the Build Plan, and thus the Deployment Project. The downside is that you can't (without some kludge) have a Deployment Environment specific changeable variable in the Build Project variables. For example, if there is a "deployment_target_host" variable that you define differently for each environment you deploy to, you'll have to do something like define the Build Project variable as "deployment_target_host_ENV1", "deployment_target_host_ENV2", etc, and then have some logic in the deployment environments that choose the "deployment_target_host" based on the names of the keys. It's kind of kludgy, which means it's kind of fragile, but I guess it works.
EDIT: The only way to change any spec-managed build or deployment plan is to update the specs files in the relevant git repo. It doesn't make it all that easy to "test a quick change" as a one-shot, but for better or worse, it forces you to use the pipeline process to, well, update the pipeline, too.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.