Generate explicit seed job and run it once during start-up

Feature Request

I have multiple groovy job DSL scripts stored in a Git repository like this:

.
└───job-dsl
        javaapi-job-dsl.groovy
        webapps-job-dsl.groovy
        webservices-job-dsl.groovy

I would like to define only one pipeline seed job which checks out the Git repository and runs all groovy scripts it can find under the job-dsl sub-directory once during JCASC start-up phase (or when triggered manually through the UI or automatically (SCM Poll) later on).

Creating this seed job seems possible with the jobs directive but AFAICS there is no possibility to have it run once during the JCASC start-up phase, correct?

Would it make sense to add this feature or is there something fundamentally wrong in my approach?

[rmmacala]

Well I may have found a workaround that works for me. Using startup-trigger-plugin:2.9.3 and adding a trigger to my pipeline I was able to get the job to start on start up. There are still issues with trying to queue the job with - script: queue(‘unit-tests’).

- script: >
      pipelineJob('unit-tests') {
                triggers {
                    hudsonStartupTrigger {
                      quietPeriod("60")
                      runOnChoice("ON_CONNECT")
                      label("")
                      nodeParameterName("")
                    }
                }
        .............
     }

[AnalogJ]

we use the following queue command to trigger the DSL run after the JCasC plugin runs.

However it only seems to work 50% of the time…

- script: queue('Utility-Jobs-DSL')

After some additional research this could be related to https://github.com/jenkinsci/configuration-as-code-plugin/issues/619

I wonder if I’m just using an older version of the JCasC plugin.