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
Currently environments can be used to pass variables to jobs, but all variables must be secret. This makes the user experience very poor for settings I want to pass to jobs that are no secrets. For example, download URLs or number of threads.
Sometimes the value is so short, making it a secret hurts usability. For example, if I wanted to pass the value 1 into my job, then everything that is 1 in the build output gets masked out, which is quite bad.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Currently environments can be used to pass variables to jobs, but all variables must be secret. This makes the user experience very poor for settings I want to pass to jobs that are no secrets. For example, download URLs or number of threads.
Sometimes the value is so short, making it a secret hurts usability. For example, if I wanted to pass the value
1into my job, then everything that is1in the build output gets masked out, which is quite bad.Beta Was this translation helpful? Give feedback.
All reactions