You almost made it correct. 😀

First at all, you should not create a package from jobs. Only classes that will be used should be packaged. In jobs, you only import necessary classes. So you’re job.groovy should look like this:

import aws.Builder

Your Builder.groovy should have:

package aws.Builder

class Builder {
...
}

Do you see the difference? In this example, I assume that jobDSL/builders is your additional classpath, that you have to add in the seed job configuration (this field will be available when script security is disabled). Packages names should contain ONLY the structure under the classpath and it would be great if they could have only one class with the same name as the package (see my code example with the class Builder).

jobDSL is just the directory of the whole project. Jobs directory contains only your jobs, and builders directory contains your helpers, builders, shared classes, or however you want to name those things. The thing is that all those paths have their own specialization and they are used according to Groovy syntax. During seed job configuration you should remember, that you need to configure it from the perspective of the root directory of the project. jobDSL as the directory should be committed (or classpath AND seed jobs paths should be extended, but it’s quite… unclear). Let’s assume that jobDSL is just the repository name with your stuff and it’s being cloned during the seed job run. So that’s your configuration:

DSL script: jobs/aws/job.groovy
Additional classpath (advanced settings): builders

Do you see how it works? With this, the job in jobs/aws/job.groovy will look for class aws.Builder, which is part of the aws.Builder package, that can be found in the builders classpath. If you want to change anything (like use jobDSL as the main directory and you want to get that directory in all the paths) just adjust this example. 😀

If anything is still unclear, don’t hesitate to ask! 🙂 And please remember about disabling the script security! Without that, you won’t even see the additional classpath field in the seed job configuration!

This is my current file structure
jobDSL/
├── builders/aws
└─── Builder.groovy
└── jobs/aws
└─── job.groovy

Builder.groovy:
package jobDSL.builders.aws
…

job.groovy:
package jobDSL.jobs.aws
import jobDSL.builders.aws.DeployStackJobBuilder
…

And I have a seed job set up to run on the following files “jobDSL/jobs/**/*.groovy”

Still I get this error when running:
ERROR: startup failed:
job.groovy: 2: unable to resolve class jobDSL.builders.aws.Builder
@ line 2, column 1.
import jobDSL.builders.aws.Builder

Of course, you can do that, but… you need to disable Script security in Security settings. If you do that, then “Additional classpath” will be available and you can type a classpath (in this scenario “utilities” directory). Unfortunately, I didn’t find any other option without the necessity of choosing only some of the possible methods inside the sandbox.

“`
dsl_scripts/
├── dsl
└── mainDSL.groovy
└── utilities
└── MyUtilities.groovy
“`

When you have a large amount of jobs, not being able to sort them by folders quickly becomes a mess.

Thanks! 🙂