Naming steps in Declarative Pipeline-As-Code

[Ram D]

I am trying to give names to different steps in a stage using Declarative pipeline, but unable to do that. This was reported and fixed as part of JENKINS-37324, but I am unable to find any documentation that shows how to use this.

I tried to use following, based on a SO answer, but it does not work:

sh cmd: "mvn -U versions:set versions:update-child-modules -DnewVersion=${MAJOR_VERSION}.${SVN_REVISION}-SNAPSHOT" , name: "Update Versions"

This gives following error:

WorkflowScript: 49: Invalid parameter "cmd", did you mean "script"? @ line 49, column 11.
   							sh cmd: "mvn -U versions:set versions:update-child-modules -DnewVersion=${MAJOR_VERSION}.${SVN_REVISION}-SNAPSHOT" , name: "Update Versions"
             ^

Please note that I am using Declarative pipeline, not scripted.

[Stuart Rowe]

I'm not familiar with JENKINS-37324. To fix the specific error you posted, use 'script' instead of 'cmd':

See: https://jenkins.io/doc/pipeline/steps/workflow-durable-task-step/#-sh-%20shell%20script

sh script: "mvn -U versions:set versions:update-child-modules -DnewVersion=${MAJOR_VERSION}.${SVN_REVISION}-SNAPSHOT" , name: "Update Versions"