[JENKINS-46119] Use the job name in context string

[dubrsl]

No description provided.

[jglick]

Do not do this. There was an issue specifically requesting that the context string not include details like a job name, and that was fixed. The reason is that GitHub has features whereby you can control various workflows by specifying approved status context strings, and they need to be an exact match.

[dubrsl]

Different approaches require different settings. IMHO context should be configurable with defaults like now.

[stephenc]

This should be handled using traits to control the naming behaviour.

As such I recommend splitting this into a PR on this repo that enabled a trait to configure the notification context naming by decorating the GitHubSCMSourceContext / Request and then a new separate extension plugin that provides the trait with the new behaviour.

Closing this PR not as a rejection of the principle of the change but as a rejection of the chosen implementation strategy

[Puneeth-n]

Is there a way to set a configurable context?

[fho]

I also also need a way to set the shown status to something more descriptive.
If you have multiple multibranch Jenkins jobs running you end up with multiple 'continuous-integration/jenkins/' statuses and you have no clue what was successful or what failed