+1 for Slava Dubrovskiy's question: 'Is it possible to disable this
feature?'
Especially when referencing ENV variables which should be masked, this is
problematic in the UI for exposing the values of those variables.
On Monday, December 4, 2017 at 11:09:34 AM UTC-8, Victor Martinez wrote:
>
Hi
Is it possible to disable this feature?
04.12.2017 21:09, Victor Martinez пишет:
As far as I know you don't need to do anything since the pipeline does
it automatically:
For instance, the below pipeline will be shown as the attached screenshot
|
node('docker') {
sh 'docker
It'll a problem for me in the near future as I'll not work for this
customer in the next few weeks.
Anyhow, next time, when I'll be there, I'll compare the plugins versions.
Before I left, I have updated all the relevant plugins to their latest
versions and also upgraded the Jenkins to its
My current setup is:
- Jenkins core 2.73
- Blueocean 1.3.3
- JDK 1.8.0_131
See the whole plugins setups in this gist:
https://gist.github.com/anonymous/a6785cf2182d4e4b35f0bfb426d0f69b
Can you confirm whether you are using the same or superior versions?
Cheers
--
You received this message
Yes, that is what I meant but I do not see that like that.
On Monday, December 4, 2017 at 9:09:34 PM UTC+2, Victor Martinez wrote:
>
> As far as I know you don't need to do anything since the pipeline does it
> automatically:
>
> For instance, the below pipeline will be shown as the attached
As far as I know you don't need to do anything since the pipeline does it
automatically:
For instance, the below pipeline will be shown as the attached screenshot
node('docker') {
sh 'docker --version'
sh 'docker info'
}
I have seen the following ticket [1] and all of it's duplicate tickets but
haven't found any documentation on how to actually add the description to a
pipeline step so it'll show what really happened and not just "shell
script".
Can someone please assist?
[1]
