[JENKINS-27092] create a step to abort the build with a NOT_BUILT status

The error step results in a workflow with a "FAILURE" state.

It is desirable to be able to end a workflow early from within the workflow itself but not have the workflow in an error state (which would imply a user needs to take a look at why it failed and perform so work).

e.g.

say I do not want to deploy any code to production on a Friday afternoon

A step that stops the workflow on a Friday afternoon should not result in the build being failed but in one that it has been intentionally cut short.

---
Originally reported by teilo, imported from: create a step to abort the build with a NOT_BUILT status

• status: Reopened
  
• priority: Minor
  
• component(s): workflow-basic-steps-plugin
  
• label(s): community-bee
  
• resolution: Unresolved
  
• votes: 24
  
• watchers: 33
  
• imported: 20251215-220547
  

Raw content of original issue

The error step results in a workflow with a "FAILURE" state.


It is desirable to be able to end a workflow early from within the workflow itself but not have the workflow in an error state (which would imply a user needs to take a look at why it failed and perform so work).


e.g.

 say I do not want to deploy any code to production on a Friday afternoon


A step that stops the workflow on a Friday afternoon should not result in the build being failed but in one that it has been intentionally cut short.

Comienza revisando el paso de error existente y cómo workflow-basic-steps-plugin representa un workflow que termina prematuramente. Aclara la semántica prevista de un nuevo paso que detiene la ejecución sin FAILURE y produce NOT_BUILT, incluido cómo debe notificarse la finalización. Se considera terminado cuando el comportamiento está especificado y cubierto por las pruebas relevantes del plugin.

Escrito por el modelo de indexación a partir del texto del issue.