pipeline: multi line string input?
long-term
T
Tawny Aardvark
it's possible to have multi line string for pipeline input?
at the moment, the string input allow input as a giant string... but it's pretty hard to read, would be nice if we could have an option to enter multi line string for scenario where it's easier to enter data as a yaml content or just multi line text?
entering
Log In
Rohan Gupta
Merged in a post:
Add Multi-Line Text Area for Pipeline Inputs
T
Teal blue Mackerel
Summary:
When configuring pipeline variables to accept YAML or other lengthy input, the current single-line input box is impractical and cluttered. Providing a multi-line text area—or an expanded code-like editor—on the “Run Pipeline” window would improve usability and reduce input mistakes.
Problem Statement / Pain Point:
Large YAML or JSON content is difficult to edit and review in a cramped single-line field.
Users are more prone to syntax errors or formatting mistakes due to limited space.
The current flow diminishes productivity by forcing repeated scrolling or external text editors.
Proposed Solution:
Replace the single-line input with a multi-line text area that automatically expands, or add a toggle to switch to a code editor view.
Offer basic formatting or syntax-highlighting to ease reading and editing.
Benefits / Impact:
Improves user experience by making it simpler and quicker to provide or adjust complex inputs.
Decreases errors and rework caused by formatting issues.
Streamlines the pipeline setup process for teams working with large YAML configurations.
Canny AI
Merged in a post:
Multi-Line Entry in Manual Approver, Approver Input
F
Fuchsia Catshark
In our release pipeline we want to add a release note, which could be multiple lines once the user accepts the tests. If there was an option to enter a multi-line text outside of the approval step that could be ok too (i.e. an input step).
As a workaround for now we will likely use the comment field (but that is obviously not optimal).
Sudarshan Purohit
Fuchsia Catshark: Thanks for the request. The comment field is intended for such notes attached to specific executions. Could you elaborate on why it doesn't solve your use case?
F
Fuchsia Catshark
Sudarshan Purohit That is likely what we will use as a work-around. However, it is not optimal given the comment field is currently being used to provide the reason for the approval while I am looking for a mechanism to add a multi-line text after the run has kicked off.
At a higher level it seems restrictive that input variables do not seem to support multiple lines as far as I can tell. So even if I knew at the beginning of the test run (which we don't, because we use a GCR Trigger) what multiple-line release note I wanted to add, it does not seem that is possible either.
Sudarshan Purohit
Fuchsia Catshark: I was referring to the comment field that's attached to the execution. This one is multi-line, and it can be edited multiple times while pipeline is running. Does it serve your purpose?
Prasad Satam
long-term