[Ch 9] CI/CD — add lint, security scan, and test steps #18
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Type
Feature
Lineage
Standalone — scoped from platform-playbook chapter 9 for the full-stack mdview vision.
Repo
ldraney/mdviewUser Story
As a developer
I want CI to run lint and security scans before building
So that code quality and security issues are caught before deploy
Context
The current
.woodpecker.yamlonly builds and pushes the Docker image. rubocop, brakeman, and bundler-audit gems are in the Gemfile but not run in CI. This ticket adds those steps and gates the build on them passing.File Targets
.woodpecker.yaml— add lint step with rubocop, brakeman, bundler-audit before build-and-pushFiles the agent should NOT touch:
Dockerfile— no changes neededGemfile— gems already presentFeature Flag
none
Acceptance Criteria
Test Expectations
Constraints
harbor.tail5b443a.ts.net/library/rails-base:latestas the lint step imageChecklist
Related
project-mdview— project this affectsScope Review: NEEDS_REFINEMENT
Review note:
review-1949-2026-08-01Template is complete and file targets verified, but three issues need resolution before this is agent-ready:
arch-mdview-appdoes not exist in pal-e-docs. Create it to satisfy traceability.rails-base:latestbut the landscaping-assistant pattern (also referenced) usesruby-rails-build:latest. Clarify which image to use.bundle-installstep: the landscaping-assistant CI pattern has a separate bundle-install step that copies pre-cached gems before lint runs. Without it, rubocop/brakeman/bundler-audit won't be available. Either add the step to the spec or confirm the lint image has gems pre-installed.