Add known Jenkins pipeline references
Dandaedre/agent-tasks/pipeline/head This commit looks good
Details
Dandaedre/agent-tasks/pipeline/head This commit looks good
Details
This commit is contained in:
parent
9d58d1b78c
commit
8923682b95
|
|
@ -29,6 +29,19 @@ Do not guess infrastructure values from another project. Reuse project scripts
|
|||
instead of duplicating substantial build logic in Groovy or shell. Keep
|
||||
language-specific setup and gates only when the target project needs them.
|
||||
|
||||
## Known reference pipelines
|
||||
|
||||
Use the closest known Jenkinsfile as a structural reference, then confirm every
|
||||
project-specific value against the target repository:
|
||||
|
||||
- [Rust (`vsg-bridge-ls`)](https://proxy.dandaedre.com/gitea/MadGobblins/vsg-bridge-ls/raw/branch/main/Jenkinsfile)
|
||||
- [Websites (`SOTV_Websites`)](https://proxy.dandaedre.com/gitea/Books/SOTV_Websites/raw/branch/main/Jenkinsfile)
|
||||
- [Books/Typst (`ravenous_typst`)](https://proxy.dandaedre.com/gitea/Ravenous/ravenous_typst/raw/branch/candlelight/Jenkinsfile)
|
||||
|
||||
These are known-good examples, not drop-in templates. Do not copy credentials,
|
||||
worker labels, paths, branches, publication rules, or project identifiers
|
||||
without verifying them for the target repository.
|
||||
|
||||
## Pipeline structure
|
||||
|
||||
Use a declarative `pipeline {}` with clearly named stages. A typical order is:
|
||||
|
|
|
|||
Loading…
Reference in New Issue