Password agent parameters?
Answered
We have a number of agent-specific environment variable parameters that we would like to define as password parameters. It is possible to do this when defining parameters on projects via the type spec, but I can't find any way to do the same thing for agent parameters.
Is this possible? If not, is there a workaround that would achieve the same result of making certain values available to builds as environment variables, but without configuring them as project parameters and without having their values show up in the "Actual Parameters" of builds?
Thanks in advance!
Please sign in to leave a comment.
Hi Ali,
environment variables are the most common approach indeed, and yes, all environment variables available for the build agent's process at start should be passed to the build as "env.PARAMETER_NAME". Of course, the usual restrictions to environment variables apply, they will need to be properly set for the build agent's process to pick them up, and setting them will depend on your exact OS.
This said, the parameters will be displayed in Actual Parameters if they are picked up by the agent. Currently, if you want to keep them hidden you should set them on the server as password parameters. Alternatively you can also remove the "View build runtime parameters and data" permission from the role of the users who should not have access to that information.
We have this request in our tracker to implement the feature to mark agent-side parameters as passwords to hide them from sight as well. Please vote for it: https://youtrack.jetbrains.com/issue/TW-36047