I'm seeing this too, but not only is the systemMessage prepended to any Folder description, it is also prepended to my jobDescriptions. Strangely, not all jobDescriptions only some of them. So far it looks like the ones that do NOT experience this oddity are 2 "regular" jobDSP job()s whose full definition is in the .groovy file, i.e. they do not define multibranch pipeline jobs. The other jobs I have are all multibranch pipeline jobs, and these experience this issue with the duplicated systemMessage.
I'm using CasC to configure my jenkins controller and all jobs through jobDSL, and I've tried deleting the jobs through the GUI and recreating them through CasC/jobDSL and this bug persists.
I've verified that the .groovy/jobdsl files that i have referenced from the jobs: section in my ~jenkins/jenkins.yaml all have a distinct job description (e.g. job('myJob')
{ description('my job') }
), but after reloading CasC and looking at the jobs in the GUI, they look like "<systemMessage><br>my job". Perplexed. I even tried deleting the jobs through the GUI and reprovisioning them through CasC, but the job descriptions still have my systemMessage in them.
I'm using jenkins 2.249.2, CasC v1.45, JobDSL v1.77, and Folders v6.14... I am also using html tags in all my descriptions using OWASP Markup Formatter Plugin v2.1.
What's an acceptable approach for this? Was looking at taking it on. Adding a property to AbstractFolderDescriptor for disabling system message toggleable under the Appearance section of the configure page might work, but is that too prominent?