Groovy
You're viewing a free preview. Sign in free to read every script.
Why this exists In this setup the Jenkinsfile itself stays small. Each stage (build, code analysis, publish) lives in its own Groovy file in one central repository shared by every project, and the Jenkinsfile just…
How Central Groovy Files Are Loaded: load and the Stage Contract
The mechanics behind a central Groovy repository: checking it out after the application checkout, the load step, why every file ends with return this, what a loaded file can and cannot see, and the small contract every stage file follows.
Sign in free to read this script, along with the rest of the library.
Sign in free