This repository is the Jenkins Job DSL Plugin, a Jenkins plugin that allows users to define Jenkins jobs, folders, views, and configuration files programmatically using a Groovy-based domain-specific language (DSL). The DSL is executed as a build step (the "Process Job DSL Scripts" step) or via Configuration as Code (JCasC), and it generates the corresponding Jenkins XML configuration, which is then applied to the Jenkins instance. The plugin manages the lifecycle of generated items, tracking which jobs/views/config files were created by a seed job and handling updates, renames, and deletions when the DSL script changes. The architecture is a multi-module Maven project: job-dsl-core contains the DSL implementation with a hierarchy of context classes (e.g., StepContext, PublisherContext, ScmContext, WrapperContext) that build XML node trees using Groovy's NodeBuilder. job-dsl-plugin integrates with Jenkins, providing the build step descriptor, script loaders (sandboxed, secure, approval-based), job management (creating/updating jobs via Jenkins API), and actions for tracking generated items. job-dsl-ast provides AST transformations for plugin version checks and deprecation warnings. The DSL is extensible via ContextExtensionPoint, allowing other Jenkins plugins to contribute DSL methods. Key entry points include the DslFactory class (top-level DSL methods like job(), folder(), listView()), the ExecuteDslScripts build step, and the ScriptRequestGenerator that resolves DSL script sources. The primary data flow is: DSL script text → GroovyShell execution → context objects generate XML nodes → JobManagement writes config to Jenkins (or filesystem for testing). External dependencies include the Jenkins core API, numerous optional Jenkins plugins (git, subversion, email-ext, etc.), and the structs plugin for dynamic DSL generation. The plugin is widely used in the Jenkins ecosystem for automating job creation and maintaining configuration as code. It includes a built-in API viewer (JavaScript web app) for browsing available DSL methods and their documentation. The codebase is mature with extensive Spock test coverage, but it carries some technical debt due to its long history and the need to support many Jenkins plugin versions.