b7ae663058
ci/woodpecker/pr/bolt-validate Pipeline was successful
ci/woodpecker/pr/yamllint Pipeline was successful
ci/woodpecker/pr/puppet-lint Pipeline was successful
ci/woodpecker/pr/epp-validate Pipeline was successful
ci/woodpecker/pr/erb-validate Pipeline was successful
ci/woodpecker/pr/ruby-validate Pipeline was successful
ci/woodpecker/pr/ruby-check Pipeline was successful
ci/woodpecker/pr/puppet-validate Pipeline was successful
currently, all woodpecker jobs jam onto one host, and have no resource limits resulting in one kubernetes host suddenly maxing its cpu - ensure we allocate resources for each woodpecker job
19 lines
435 B
YAML
19 lines
435 B
YAML
when:
|
|
- event: pull_request
|
|
|
|
steps:
|
|
- name: epp-validate
|
|
image: git.unkin.net/unkin/almalinux9-puppet-pr-validator:20260317
|
|
commands:
|
|
- uvx pre-commit run --all-files --config ci/epp-validate.yaml
|
|
backend_options:
|
|
kubernetes:
|
|
serviceAccountName: default
|
|
resources:
|
|
requests:
|
|
memory: 512Mi
|
|
cpu: 1
|
|
limits:
|
|
memory: 2Gi
|
|
cpu: 1
|