Skip to content

fix(jenkins): use only core pipeline steps - #8

Merged
untraceablez merged 2 commits into
mainfrom
fix/jenkinsfile-core-steps
Jul 21, 2026
Merged

fix(jenkins): use only core pipeline steps#8
untraceablez merged 2 commits into
mainfrom
fix/jenkinsfile-core-steps

Conversation

@untraceablez

Copy link
Copy Markdown
Owner

The first auto-triggered build failed to compile: the controller's pinned plugin set lacks Timestamper and Pipeline Utility Steps.

  • Drop options { timestamps() }.
  • Replace readProperties with a core readFile + parse of .work/decision.env.

No new plugins required (keeps the controller's minimal pinned set). GitHub Actions CI covers shell/bats; the Jenkinsfile itself is validated by an actual build (triggered post-merge).

🤖 Generated with Claude Code

untraceablez and others added 2 commits July 20, 2026 21:05
…-utility-steps)

The controller's pinned plugin set has neither Timestamper nor Pipeline
Utility Steps, so the pipeline failed to compile:
  - drop options { timestamps() }
  - replace readProperties with a core readFile + parse of .work/decision.env

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XHrdPEhFSuvzutLvD5xTmS
The Groovy sandbox rejects dynamic env[key]=value (DefaultGroovyMethods.putAt).
Read ACTION/VERSION/IS_NEWEST via sh(returnStdout) + fixed env.X assignments.
@untraceablez
untraceablez merged commit 186f9c7 into main Jul 21, 2026
1 check passed
@untraceablez
untraceablez deleted the fix/jenkinsfile-core-steps branch July 21, 2026 02:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant