[JENKINS-53026] Snippitizer should use double quotes around strings containing variables

In the example below, the user would expect ${WORKSPACE} to be substitutes for the workspace path. The snippitzer returns the parameter surrounded in single quotes so the replace does not happen. In this scenario, the snippitezer should return the parameter in double quotes and either convert the exiting double quotes to single, or properly escape them.

---
Originally reported by mdkf, imported from: Snippitizer should use double quotes around strings containing variables

• status: Open
  
• priority: Minor
  
• component(s): workflow-cps-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 2
  
• imported: 2025-12-07
  

In the example below, the user would expect ${WORKSPACE} to be substitutes for the workspace path. The snippitzer returns the parameter surrounded in single quotes so the replace does not happen. In this scenario, the snippitezer should return the parameter in double quotes and either convert the exiting double quotes to single, or properly escape them.

1 attachment

- [image-2018-08-13-21-02-59-197.png](https://issues.jenkins.io/secure/attachment/43731/image-2018-08-13-21-02-59-197.png)
> 

Start by locating the Snippitizer entry point in workflow-cps-plugin and reproduce the ${WORKSPACE} example described in the issue. Trace how strings containing variables are quoted, then add or update focused coverage for the expected output and handling of existing double quotes; done means the generated snippet allows the variable substitution.

Written by the indexing model from the issue text.