How can we improve Azure DevOps?

Multiple lines variable in Build and Release

This suggestion is migrated to Developer Community. Please use below link to view the current status.
https://developercommunity.visualstudio.com/content/idea/365667/multiple-lines-variable-in-build-and-release.html
Some tasks have the textboxes that support multiple line content, such as Delete task, but multiple lines variable is not supported, it's better to support it.

56 votes
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Anonymous shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    6 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • NKDavis commented  ·   ·  Flag as inappropriate

        yes I need this for token replacement as well!!
        I have 20 services i need to tokenize and now becouse i can not group related environment controlled variables intend of 6 tokens per file i have 26!!!!
        because i can not put
        10 lines of an entire configuration element IE

        <time>
        <add key="DueTimeSeconds" value="10" />
        <add key="PeriodSeconds" value="600" />
        <add key="PrimaryDaysToRun" value="2,3,4,5,6" />
        <add key="PrimaryHoursToRun" value="0:00-1:00,3:00-23:59:59" />
        <add key="SecondaryDaysToRun" value="7" />
        <add key="SecondaryHoursToRun" value="8:00-17:59" />
        <add key="StopDateTime" value="2000-01-25 18:22" />
        <add key="DetailWaitCount" value="1" />
        <add key="DetailHourTime" value="20" />
        </time>
        is my element
        i want
        <time>
        #{TOKEN_TIMESETTINGS}#
        </time>
        since this change PER ENVIRONMENT and i have 6 test environments with different values..
        now i need ONE for each key....

      • Paul commented  ·   ·  Flag as inappropriate

        It would be nice to have available (in the Release process when run) a drop down field containing a set of values which, when any value is selected becomes that variables value. For example, a list of server names. We find ourselves creating releases for a number of Test servers to deploy to which means setting up a release for each one. If we could give the option of selecting a server to deploy to and have one release using the dropdown variable created, we wouldn't need to create so many releases.. if that makes sense!

      • Anonymous commented  ·   ·  Flag as inappropriate

        Good Lord add multi-line variables. Your own file search patterns require multiple lines to filter file copies, for example:

        **\*
        !$(Build.ProductName).exe

        Those two filters MUST be on two lines, this is Microsoft tech!

      Feedback and Knowledge Base