Re: more meaningful description of a step

On Monday, July 17, 2017 at 2:15:59 PM UTC-4, Samuel Van Oort wrote: > > A better approach would be to select from a list of credential ids. > Specifically you can either keep credentials associated with the build; or request user-scoped credentials as a build parameter. Failing that, you coul

Re: more meaningful description of a step

Torsten, > how do I hide sensitive information that *DO NOT* come from credential binding in the shell script header? First, I would strongly discourage this approach in general. Credentials and credentials-binding exist specifically to provide a secure mechanism for build secrets (with seve

Re: more meaningful description of a step

Hello, I am a bit confused how to handle sensitive information when using a shell script: In https://issues.jenkins-ci.org/browse/JENKINS-37324 Sam Van Oort wrote (2017-01-11 23:37): "Lots of discussion about how to separate sensitive and nonsensitive environment variable content (markers f

Re: more meaningful description of a step

Hi Jakub, Custom captions (or more accurately, custom step argument descriptions) are supported on a per-Step type basis, so if your plugin is defining a new Step type, you can define how to display its inputs. There isn't anything coming immediately to allow you to customize captions individua

more meaningful description of a step

Hi, Recently https://issues.jenkins-ci.org/browse/JENKINS-37324 was solved. In sprint review Sam Van Oort demonstrated the foundation for this https://www.youtube.com/watch?v=HhiUY70RVJY&t=510 He mentions there possibili