[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title boris avney commented on JENKINS-37324 Re: We would like a more meaningful description of a step Hi, Where can I find which BO version has this functionality? (couldn't find the PR in change log: https://wiki.jenkins.io/display/JENKINS/Blue+Ocean+Plugin) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Jesse Glick commented on JENKINS-37324 Re: We would like a more meaningful description of a step if I use any variables (in the stock sh step's command or the labelledShell step's label), then the label is just silently ignored See JENKINS-47101. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Phil McArdle commented on JENKINS-37324 Re: We would like a more meaningful description of a step If you wanted something like that changed, that'd be a separate issue, yep I think that's running at a much lower level than the step labelling. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Dana Goyette commented on JENKINS-37324 Re: We would like a more meaningful description of a step Thanks for the hint about the issue being variables. That seems to be it: if I use any variables (in the stock sh step's command or the labelledShell step's label), then the label is just silently ignored! Should I file a separate ticket for that brokenness? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Phil McArdle commented on JENKINS-37324 Re: We would like a more meaningful description of a step Dana Goyette, I haven't tested this in a while, but I believe your issue there is using variables like the build id, assuming you used the actual number of the current build. In my experience, Jenkins goes to lengths to identify and mask data like that. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title
Dana Goyette edited a comment on JENKINS-37324
Re: We would like a more meaningful description of a step
As it is now, the sh script is quite unreliable about ever saying anything more than just "Shell Script". Shouldn't single-line commands show the command being executed? For me, they almost never do. This step shows These steps show the command: {{sh(script: "/usr/bin/env python ./install_manager.py --jenkins --uninstall-all")}} {{sh(script: "/usr/bin/env python ./install_manager.py --jenkins --fail-if-leftovers --uninstall-all")}} These steps shows show just "Shell Script", rendering the summary useless: {{sh(script: "/usr/bin/env python ./install_manager.py --jenkins -- fail build - if id 123456 - leftovers - -uninstall-all install ")}} {{sh(script: "/usr/bin/env python ./install_manager.py --jenkins --build-id 123456 -- install uninstall ")}} Adding or removing the /usr/bin/env didn't change anything, either.Note that my actual script is actually calling {{sh}} with a Map as a parameter, rather than passing named parameters. If I use the labelledShell step, even _that_ description sometimes gets ignored.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Dana Goyette commented on JENKINS-37324 Re: We would like a more meaningful description of a step As it is now, the sh script is quite unreliable about ever saying anything more than just "Shell Script". Shouldn't single-line commands show the command being executed? For me, they almost never do. This step shows the command: sh(script: "/usr/bin/env python ./install_manager.py --jenkins --uninstall-all") These steps shows just "Shell Script", rendering the summary useless: sh(script: "/usr/bin/env python ./install_manager.py --jenkins --fail-if-leftovers --uninstall-all") sh(script: "/usr/bin/env python ./install_manager.py --jenkins --build-id 123456 --install") Adding or removing the /usr/bin/env didn't change anything, either. Note that my actual script is actually calling sh with a Map as a parameter, rather than passing named parameters. If I use the labelledShell step, even that description sometimes gets ignored. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Veaceslav Gaidarji commented on JENKINS-37324 Re: We would like a more meaningful description of a step Still not sure that wrapping each and every "sh" step into a stage block is a good idea for providing a description for sh step. There should be a possibility to label sh step (and probably other steps) and it was mentioned here. I had a plan to enhance "sh" step API and add "label" parameter (as discussed with Sam Van Oort). Just need to find time for that. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Vicky Chijwani commented on JENKINS-37324 Re: We would like a more meaningful description of a step Jesse Glick - you're right. I loosely said "Jenkins core" as a way to say "officially supported by CloudBees". If nested stages can support the use-case of labelling a group of steps (especially shell steps) without creating a new node in the pipeline visualization, that would also perfectly solve the issue. Come to think of it, there's a very similar proposal at JENKINS-44094, about grouping a set of steps with a custom label. That would solve multiple problems. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Jesse Glick commented on JENKINS-37324 Re: We would like a more meaningful description of a step This is Pipeline, not Jenkins core BTW. I still advocate maintaining a separation of duties, so that stage is used for adding a human-readable label to a step or sequence of steps. If Blue Ocean fails to display nested stages well, then improve Blue Ocean. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title
Vicky Chijwani edited a comment on JENKINS-37324
Re: We would like a more meaningful description of a step
[~thclpr] - I was thinking maybe we could add label support for other common steps as well. That's why I named the plugin {{labelled-steps}} instead of {{labelled-shell-step -plugin }} :)I don't know if it's going to be feasible / easy to support other steps, but it's worth a shot (sh step was thankfully trivial to modify). Hopefully at some point Jenkins core will support custom labels for any step.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Vicky Chijwani commented on JENKINS-37324 Re: We would like a more meaningful description of a step Thales Pereira - I was thinking maybe we could add label support for other common steps as well. That's why I named the plugin labelled-steps instead of labelled-shell-step-plugin I don't know if it's going to be feasible / easy to support other steps, but it's worth a shot (sh step was thankfully trivial to modify). Hopefully at some point Jenkins core will support custom labels for any step. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Thales Pereira edited a comment on JENKINS-37324 Re: We would like a more meaningful description of a step [~vchijwani] You are a life saver, thank you. Let me know if you need help for maintaining it . Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Thales Pereira edited a comment on JENKINS-37324 Re: We would like a more meaningful description of a step [~vchijwani] You are a life saver, thank you. let Let me know if you need help for maintaining it Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Thales Pereira commented on JENKINS-37324 Re: We would like a more meaningful description of a step Vicky Chijwani You are a life saver, thank you. let me know if you need help for maintaining it Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Vicky Chijwani commented on JENKINS-37324 Re: We would like a more meaningful description of a step If anyone is looking for a way to provide a custom label to a shell step, I've created this plugin that adds a labelledShell step which accepts a label argument: https://github.com/jenkinsci/labelled-steps-plugin/ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Thales Pereira edited a comment on JENKINS-37324 Re: We would like a more meaningful description of a step Hi [~cliffmeyers], this was implemented ? or Or there's any alternative for this suggestion available for usage? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Thales Pereira commented on JENKINS-37324 Re: We would like a more meaningful description of a step Hi Cliff Meyers, this was implemented ? or there's any alternative for this suggestion available for usage? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-37324 We would like a more meaningful description of a step Change By: Michael Neale Component/s: workflow-api-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title James Dumay commented on JENKINS-37324 Re: We would like a more meaningful description of a step This ticket is still In Progress. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Alex Radinsky commented on JENKINS-37324 Re: We would like a more meaningful description of a step I'm on rc3 and don't see any change. Do I need to specify the name for each step or something? How it should work and parse the command I execute? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37324 We would like a more meaningful description of a step Change By: James Dumay Sprint: frank, tethys, christmas, pannonian, iapetus, 1.0, Blue Ocean 1.0-rc3 , Blue Ocean 1.0-rc4 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37324 We would like a more meaningful description of a step Change By: James Dumay Sprint: frank, tethys, christmas, pannonian, iapetus, 1.0 , 1.0-rc1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Zach Swanson commented on JENKINS-37324 Re: We would like a more meaningful description of a step This isn't restricted to just Blue Ocean, the same inadequate information in executing shell/bat/other steps exists in the 'standard' Pipeline Stage. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37324 We would like a more meaningful description of a step Change By: James Dumay Sprint: frank, tethys, christmas, pannonian, iapetus, release candidates 1.0 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Michael Neale commented on JENKINS-37324 Re: We would like a more meaningful description of a step I would think 80% of it is "Shell Script" - which ideally would be the script being called - or some part of it right? For things like archive, should parameters is highly useful, as are things like invoking jobs. The rest are a very very long very very thin tail of things - but things like the above would satisfy many people for a long time. Basically if the common ones are taken care of, the long tail can take its time. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title
Sam Van Oort commented on JENKINS-37324
Re: We would like a more meaningful description of a step
To answer from my understanding recampbell:
Sample outputs: this is a requirement, so I'll let Blue Ocean define this. I think for single-argument steps such as shell, batch, and node, probably just the input argument. For multi-argument steps, some sort of formatted string (format not agreed on at this point). One example, perhaps for git plugin: 'url: $ {gitUrl} , branch: $ {branch} , credentialsId: $ {id} , changeLog: [true/false], poll: [true/false]'
Steps supported: all steps will get their parameters saved, single-argument steps will get the format serialized via toString probably, multi-argument steps it's
New steps supported:
Blue Ocean agreed to submit PRs for initial implementation of the parameters-to-string method, others can be provided by plugin authors (optional API)
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title recampbell updated an issue Jenkins / JENKINS-37324 We would like a more meaningful description of a step Change By: recampbell URL: https://github.com/jenkinsci/workflow-durable-task-step-plugin/pull/22 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37324 We would like a more meaningful description of a step Change By: James Dumay Sprint: frank, tethys, christmas, pannonian, iapetus , Dropped Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37324 We would like a more meaningful description of a step Change By: James Dumay Sprint: frank, tethys, christmas, pannonian, iapetus , 1.0 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title James Dumay updated JENKINS-37324 Jenkins / JENKINS-37324 We would like a more meaningful description of a step Change By: James Dumay Status: In Review Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Hector David updated JENKINS-37324 Jenkins / JENKINS-37324 We would like a more meaningful description of a step Change By: Hector David Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title recampbell commented on JENKINS-37324 Re: We would like a more meaningful description of a step For Blue Ocean team to review this: We need examples of what the output would be What steps are supported vs. what aren't How are new steps supported? -> Do plugin authors provide this or must Blue Ocean provide every implementation? --> OK if not for first delivery, but need this for the definition of done. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37324 We would like a more meaningful description of a step Change By: James Dumay Sprint: frank, tethys, christmas, pannonian, iapetus , 1.0 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37324 We would like a more meaningful description of a step Change By: James Dumay Sprint: frank, tethys, christmas, pannonian, iapetus , 1.0 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37324 We would like a more meaningful description of a step Change By: James Dumay Sprint: frank, tethys, christmas, pannonian, iapetus , 1.0 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Jesse Glick commented on JENKINS-37324 Re: We would like a more meaningful description of a step We already have a task in progress to display a sh command (for example). If you need some additional human-readable display for one or a sequence of steps beyond that, stage already works (just not in Blue Ocean) and is as easy as anything else. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Patrick Wolf commented on JENKINS-37324 Re: We would like a more meaningful description of a step I agree with James Dumay. It is ridiculous to expect users to wrap every step in a pipeline in a new stage. This is especially true in Declarative Pipeline where stage has a much more defined meaning. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title James Dumay commented on JENKINS-37324 Re: We would like a more meaningful description of a step @jglick has noted in the nested stages issue (and previous discussions we've had on N-related tickets) nested stages aren't something we can recommend to people to solve the labeling of steps. The interpretation of what this means to users is loose and none of our visualizations support it. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title
Jesse Glick commented on JENKINS-37324
Re: We would like a more meaningful description of a step
stage('your description here') {
bat 'do stuff'
}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title
Ryan Hutchison edited a comment on JENKINS-37324
Re: We would like a more meaningful description of a step
[~svanoort] - I think one thing that the requirement doesn't capture, that is also request by JENKINS-41156, is the simple ability to rename a step. While the dynamic nature of pulling stuff out of the command for display _might_ be useful, a lot could be solved by providing a better solution than this workaround.{code}try {bat "do stuff"}finally {CpsThread.current().head.get().addAction(new LabelAction("name of step"))}{code}Unfortunately `stage` does not work.cc: [~jglick] [~jamesdumay]
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title
Ryan Hutchison commented on JENKINS-37324
Re: We would like a more meaningful description of a step
Sam Van Oort - I think one thing that the requirement doesn't capture, that is also request by JENKINS-41156, is the simple ability to rename a step. While the dynamic nature of pulling stuff out of the command for display might be useful, a lot could be solved by providing a better solution than this workaround.
try {
bat "do stuff"
}
finally {
CpsThread.current().head.get().addAction(new LabelAction("name of step"))
}
Unfortunately `stage` does not work. cc: Jesse Glick James Dumay
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37324 We would like a more meaningful description of a step Change By: James Dumay Sprint: frank, tethys, christmas, pannonian , iapetus Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37324 We would like a more meaningful description of a step Change By: James Dumay Sprint: frank, tethys, christmas , pannonian Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title James Dumay commented on JENKINS-37324 Re: We would like a more meaningful description of a step Thanks Sam Van Oort Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title
Sam Van Oort edited a comment on JENKINS-37324
Re: We would like a more meaningful description of a step
To capture discussion from today with [~jglick] and [~jamesdumay] and others:*Requirements added:** One of the implementation challenges here is that we need to mask sensitive variables in the step description (example: an access token used in a shell command invoking AWS CLI, bound into the shell command by environment variable). This information CANNOT be stored or displayed in a step* We also need to limit the size of data that is stored in recorded Step in case (for example writeFile) large data is being passed via variables * Implementation:** We will use the EnvVars (the only thing we have to work with here) to detect sensitive strings included in String parameters, by looking for the value of EnvVars in that content.* Where potentially hidden content is present, initially none of the String's content will be stored or displayable. Later we may try to replace the variable content with the EnvVars name, i.e. "my password is $passwordVar" which would execute as 'my password is s3cretC0ntent' becomes 'my password is ${passwordVar}' (so we know a variable was used). This is desirable and helpful for users but risks adds a slight risk of accidentally exposing leaking a secret if present in normal String content somewhere. *Implementation:** We will use the EnvVars (the only thing we have to work with here) to detect sensitive strings included in String parameters, by looking for the value of EnvVars in that content. * To reduce false positives, the safe/standard global environment variables for a pipeline will be removed from this list of EnvVars* We *may* also attempt to remove local computer environment variables as with https://github.com/jenkinsci/docker-workflow-plugin/blob/916bdb728fdff51709933e653ce6baa867b7bebb/src/main/java/org/jenkinsci/plugins/docker/workflow/WithContainerStep.java#L125-L127Comment: * Lots of discussion about how to separate sensitive and nonsensitive environment variable content (markers for data, whitelist/blacklist, or custom information in their EnvVars definitions) -- [~jglick] has suggested a clever approach:{quote} to play with a different way of detecting secrets you would patch `BindingStep` and `MaskPasswordsBuildWrapper` to, say, not just set `PASSWORD=s3cr3t` but also `PASSWORD+SECRET=true`, and then document this somewhere like in `EnvironmentExpander`{quote}
Add Comment
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title
Sam Van Oort commented on JENKINS-37324
Re: We would like a more meaningful description of a step
To capture discussion from today with Jesse Glick and James Dumay and others: Requirements added:
One of the implementation challenges here is that we need to mask sensitive variables in the step description (example: an access token used in a shell command invoking AWS CLI, bound into the shell command by environment variable). This information CANNOT be stored or displayed in a step
We also need to limit the size of data that is stored in recorded Step in case (for example writeFile) large data is being passed via variables
Implementation:
We will use the EnvVars (the only thing we have to work with here) to detect sensitive strings included in String parameters, by looking for the value of EnvVars in that content.
Where potentially hidden content is present, initially none of the String's content will be stored or displayable. Later we may try to replace the variable content with the EnvVars name, i.e. "my password is $passwordVar" which would execute as 'my password is s3cretC0ntent' becomes 'my password is $ {passwordVar} ' (so we know a variable was used). This is desirable and helpful for users but risks accidentally exposing a secret if present in normal String content somewhere.
To reduce false positives, the safe/standard global environment variables for a pipeline will be removed from this list of EnvVars
We may also attempt to remove local computer environment variables as with https://github.com/jenkinsci/docker-workflow-plugin/blob/916bdb728fdff51709933e653ce6baa867b7bebb/src/main/java/org/jenkinsci/plugins/docker/workflow/WithContainerStep.java#L125-L127
Comment:
Lots of discussion about how to separate sensitive and nonsensitive environment variable content (markers for data, whitelist/blacklist, or custom information in their EnvVars definitions) – Jesse Glick has suggested a clever approach:
to play with a different way of detecting secrets you would patch `BindingStep` and `MaskPasswordsBuildWrapper` to, say, not just set `PASSWORD=s3cr3t` but also `PASSWORD+SECRET=true`, and then document this somewhere like in `EnvironmentExpander`
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37324 We would like a more meaningful description of a step Change By: James Dumay Sprint: frank, tethys, christmas Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37324 We would like a more meaningful description of a step Change By: James Dumay Sprint: frank , christmas Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37324 We would like a more meaningful description of a step Change By: James Dumay Priority: Minor Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37324 We would like a more meaningful description of a step Change By: James Dumay Sprint: frank Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Michael Neale commented on JENKINS-37324 Re: We would like a more meaningful description of a step in progress NICE! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Sam Van Oort updated JENKINS-37324 Jenkins / JENKINS-37324 We would like a more meaningful description of a step Change By: Sam Van Oort Status: Reopened Open Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Sam Van Oort started work on JENKINS-37324 Change By: Sam Van Oort Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Michael Neale commented on JENKINS-37324 Re: We would like a more meaningful description of a step Julien Pivotto right, fair point. Are there other steps you use often that need a more useful description based on what they actually did? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Julien Pivotto commented on JENKINS-37324 Re: We would like a more meaningful description of a step If you want more background and why we clone so much repos – https://roidelapluie.be/blog/2016/11/18/gitslave-jenkins/ Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-37324 We would like a more meaningful description of a step Change By: Sam Van Oort URL: https://github.com/jenkinsci/workflow-durable-task-step-plugin/pull/22 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Sam Van Oort assigned an issue to Sam Van Oort Jenkins / JENKINS-37324 We would like a more meaningful description of a step Change By: Sam Van Oort Assignee: Sam Van Oort Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-37324 We would like a more meaningful description of a step Change By: Michael Neale Labels: adoption blueocean x-team Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Michael Neale commented on JENKINS-37324 Re: We would like a more meaningful description of a step cc Sam Van Oort this is the ticket I was talking about - some good ideas thrown around Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37324 We would like a more meaningful description of a step Change By: James Dumay Summary: We would like a more meaningful description of a step via flow nodes Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step via flow nodes
Title: Message Title Julien Pivotto commented on JENKINS-37324 Re: We would like a more meaningful description of a step via flow nodes same goes for almost any step – read file from repo – which file? sh – which script? which name? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step via flow nodes
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37324 We would like a more meaningful description of a step via flow nodes Change By: James Dumay Component/s: blueocean-plugin Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step via flow nodes
Title: Message Title
Julien Pivotto commented on JENKINS-37324
Re: We would like a more meaningful description of a step via flow nodes
We clone multiple SCM repositories. They are identified by the ScmName parameter, but we can not see the difference in BO. This is very annoying.
checkout([$class: 'GitSCM',
branches: [[name: branch]],
doGenerateSubmoduleConfigurations: false,
extensions: [[$class: 'CleanCheckout'], [$class: 'ScmName', name: 'super']],
submoduleCfg: [],
userRemoteConfigs: [[url: "${gitBaseUrl}/${superRepo}"]]])
Here is the repo called 'super'
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step via flow nodes
Title: Message Title Julien Pivotto updated an issue Jenkins / JENKINS-37324 We would like a more meaningful description of a step via flow nodes Change By: Julien Pivotto Attachment: changes.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step via flow nodes
Title: Message Title James Dumay reopened an issue Jenkins / JENKINS-37324 We would like a more meaningful description of a step via flow nodes Change By: James Dumay Resolution: Duplicate Status: Resolved Reopened Assignee: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step via flow nodes
Title: Message Title Jesse Glick commented on JENKINS-37324 Re: We would like a more meaningful description of a step via flow nodes Possibly “for free” from JENKINS-31582. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step via flow nodes
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-37324 We would like a more meaningful description of a step via flow nodes Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step via flow nodes
Title: Message Title James Dumay created an issue Jenkins / JENKINS-37324 We would like a more meaningful description of a step via flow nodes Issue Type: Task Assignee: Jesse Glick Attachments: unnamed-2.png Components: workflow-plugin Created: 2016/Aug/11 12:28 AM Labels: blueocean x-team Priority: Minor Reporter: James Dumay We want to provide the developer a more meaningful description of the steps in Blue Ocean. For example, if we have a shell script being executed we'd like to provide the command as the description of that step. If we don't have that information, we'd like to fall back to a description of the step otherwise fall back to the step name. Add Comment
