[JENKINS-7203] Description setter pick regexp for successful instead of failure on failed builds

We have 2 plugins on a job.

Description setter and Text finder.

For successful builds we have another description then failures (see attachment).

We have a text-finder config which marks the build as failed, in that case the failures description should be set.

But we see that even if there is a failure because of the text finder, the description-setter still reports the successful description.

Console output of the job:

....

Description set: Latest build: 28

Checking console output

/home/hudson/.hudson/jobs/install-crd21/builds/2010-08-12_02-01-32/log:

ERROR: SOAP fault during load. Check log for more details.

Finished: FAILURE

So text finder is executed before description setter

---
Originally reported by cbos, imported from: Description setter pick regexp for successful instead of failure on failed builds

• assignee: huybrechts
  
• status: Open
  
• priority: Major
  
• component(s): description-setter-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 0
  
• imported: 20251216-182730
  

Raw content of original issue

We have 2 plugins on a job.

Description setter and Text finder.


For successful builds we have another description then failures (see attachment).

We have a text-finder config which marks the build as failed, in that case the failures description should be set.

But we see that even if there is a failure because of the text finder, the description-setter still reports the successful description.


Console output of the job:

....

Description set: Latest build: 28

Checking console output

/home/hudson/.hudson/jobs/install-crd21/builds/2010-08-12_02-01-32/log:

ERROR: SOAP fault during load. Check log for more details.

Finished: FAILURE


So text finder is executed before description setter

• environment: 1.371

1 attachment

- [job_configuration.png](https://issues.jenkins.io/secure/attachment/19657/job_configuration.png)
> 

Start by reproducing the interaction between the Description setter and Text finder configurations described in the issue, using the provided console output as the expected failure case. Trace how the build result is passed to the description selection, then verify that a text-finder failure selects the failure description rather than the successful description.

Written by the indexing model from the issue text.