[JIRA] (JENKINS-41156) [Pipeline] Have shell and batch steps be renamable
Title: Message Title
Sean Sutherland commented on JENKINS-41156
Re: [Pipeline] Have shell and batch steps be renamable
Our current workaround is to do something like:
try {
bat "do stuff"
}
finally {
CpsThread.current().head.get().addAction(new LabelAction("name of step"))
}
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-41156) [Pipeline] Have shell and batch steps be renamable
Title: Message Title Sean Sutherland created an issue Jenkins / JENKINS-41156 [Pipeline] Have shell and batch steps be renamable Issue Type: Improvement Assignee: Unassigned Components: workflow-durable-task-step-plugin Created: 2017/Jan/17 11:14 PM Priority: Major Reporter: Sean Sutherland Our build process typically requires a series of batch calls into our build system. However, in looking at the steps of a build in pipeline, this results in a bunch of steps which are just "Windows Batch Script". This makes them difficult to differentiate from eachother, and provides a poor reporting experience overall. Could we have an optional second argument to the batch step (and the shell step as well) to specify a name for the step, which would get added as a LabelAction? Add Comment
