| Various existing tickets on this subject refer to naming steps in pipelines (for example, JENKINS-37324). I'd like to request the ability to name (and describe) each step in the GUI as well. The texts would play the same role in a build, that comments play in regular code. The names could also be shown in console output, and the descriptions could be shown as a user hovers over the name, etc. For example:
- Download sources
- Change paths in Makefile
- Build
- Test
Currently one's only indicator as to what's happening is the type of the build-step. But that's not always sufficiently descriptive... |