You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 10, 2024. It is now read-only.
I know something similar has been rasied previoulsy but the scenario here is slightly different. I'm already dynamically creating a VSTS variable that is then used by the Replace Tokens task but it has now reached the upper size limits for variables:
##[warning]Environment variable 'XXXX' exceeds the maximum supported length. Environment variable length: 41681 , Maximum supported length: 32766
If the task supported reading a parameters (token/value pairing) file as well as using the environment variables then instead of dynamically creating a variable I'd generate the parameters file.
The file format could be a simple text TOKEN = VALUE per line or more complex as JSON or XML format.
Thanks,
The text was updated successfully, but these errors were encountered:
Hi
I know something similar has been rasied previoulsy but the scenario here is slightly different. I'm already dynamically creating a VSTS variable that is then used by the Replace Tokens task but it has now reached the upper size limits for variables:
##[warning]Environment variable 'XXXX' exceeds the maximum supported length. Environment variable length: 41681 , Maximum supported length: 32766
If the task supported reading a parameters (token/value pairing) file as well as using the environment variables then instead of dynamically creating a variable I'd generate the parameters file.
The file format could be a simple text TOKEN = VALUE per line or more complex as JSON or XML format.
Thanks,
The text was updated successfully, but these errors were encountered: