I just found out that the job description is just populated from GitHub’s repo description which is “Apache sling” by default for new repos. That can be overwritten via .asf.yaml (https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INFRA&title=git+-+.asf.yaml+features#Git.asf.yamlfeatures-Repositorymetadata) I am gonna enrich our wiki page a bit to clarify that. Konrad
> On 17. Oct 2023, at 16:44, Konrad Windszus <[email protected]> wrote: > > According to > https://cwiki.apache.org/confluence/display/SLING/Sling+Jenkins+Setup we > leverage the https://github.com/jenkinsci/github-branch-source-plugin for > automatically creating Jobs for new repos. > I noticed though that new Jobs have the generic description “Apache sling” > though in https://ci-builds.apache.org/job/Sling/job/modules/ (e.g. in > https://ci-builds.apache.org/job/Sling/job/modules/job/sling-org-apache-sling-feature-analyser-classes/configure). > > As the description field is read-only on the Jobs Configuration I am > wondering what is populating that field initially and how to affect it > Name seems to be derived from the repository name and I was kind of hoping > that the description could be extracted from the pom.xml (for Maven based > projects)…. > > Does anyone have any insights here because most of our Jobs have actually > proper names. > > Thanks in advance, > Konrad
