Runner (S4): - CPU and memory requests and limits for the runner and DinD containers, sized for one job at a time on a 2-CPU worker. - capacity 1, job timeout 2h, shutdown_timeout 15s and report_close_timeout 10s so a restarted runner can cancel and report its jobs inside the chart's fixed 30s grace period. - force_pull false and job images pinned to dated runner-images tags. Gitea (S6): ZOMBIE_TASK_TIMEOUT 5m, ENDLESS_TASK_TIMEOUT 2h30m, ABANDONED_JOB_TIMEOUT 12h, LOG_RETENTION_DAYS 90 and ARTIFACT_RETENTION_DAYS 30, all as role defaults with comments. Refs DevOps/software-infrastructure#37 Refs DevOps/software-infrastructure#39 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Role Name
A brief description of the role goes here.
Requirements
Any pre-requisites that may not be covered by Ansible itself or the role should be mentioned here. For instance, if the role uses the EC2 module, it may be a good idea to mention in this section that the boto package is required.
Role Variables
A description of the settable variables for this role should go here, including any variables that are in defaults/main.yml, vars/main.yml, and any variables that can/should be set via parameters to the role. Any variables that are read from other roles and/or the global scope (ie. hostvars, group vars, etc.) should be mentioned here as well.
Dependencies
A list of other roles hosted on Galaxy should go here, plus any details in regards to parameters that may need to be set for other roles, or variables that are used from other roles.
Example Playbook
Including an example of how to use your role (for instance, with variables passed in as parameters) is always nice for users too:
- hosts: servers
roles:
- { role: username.rolename, x: 42 }
License
BSD
Author Information
An optional section for the role authors to include contact information, or a website (HTML is not allowed).