daniel/ansible-bind9-role
1
0
Fork 0
Code Issues 3 Pull Requests 1 Actions Releases Wiki Activity

ci: Debug and fix Gitea Actions CI/CD pipeline #16

New Issue
Closed
opened 2026-02-07 23:23:31 +00:00 by daniel · 1 comment
daniel commented 2026-02-07 23:23:31 +00:00
Owner
Copy Link

Description

Debug and fix the Gitea Actions CI/CD pipeline for ansible-bind9-role. The pipeline should validate role functionality across supported BIND9 versions and platforms.

Objectives

  1. Review existing workflows

    • Examine .gitea/workflows/ directory for existing configurations
    • Identify any broken or incomplete workflows
    • Check for proper GitHub Actions syntax compatibility

  2. Define test matrix

    • BIND9 versions: 9.18.x (main), 9.20+ (feature/9.20 branch)
    • Platforms: Debian 11/12/13, Ubuntu 20.04/22.04/24.04
    • Molecule scenarios: default and bind9-20

  3. Implementation requirements

    • Lint checks (yamllint, ansible-lint)
    • Syntax validation (named-checkconf)
    • Molecule testing across platform matrix
    • Conditional tests based on branch (9.18 vs 9.20)

  4. Test coverage

    • Meta/argument_specs validation
    • Template rendering
    • Role execution
    • Configuration syntax validation
    • Service startup and basic functionality

Success Criteria

  • Pipeline runs successfully on pull requests
  • Linting checks pass (YAML, Ansible)
  • Molecule tests run for appropriate scenarios
  • Tests execute across version/platform matrix
  • Pipeline gates merges on failure
  • Clear reporting of test results
  • Performance: Reasonable build time (target: < 15 min)

Related Issues

  • PR #14: BIND9 9.20 support implementation
  • Issue #15: Documentation clarification

Notes

  • Pipeline should validate both main (9.18.x) and feature branches (9.20+)
  • Consider resource constraints for CI/CD runners
  • Molecule tests require root/privileged access to systemd
  • Use matrix strategy to avoid duplicate workflow definitions
## Description Debug and fix the Gitea Actions CI/CD pipeline for ansible-bind9-role. The pipeline should validate role functionality across supported BIND9 versions and platforms. ## Objectives 1. **Review existing workflows** - Examine `.gitea/workflows/` directory for existing configurations - Identify any broken or incomplete workflows - Check for proper GitHub Actions syntax compatibility 2. **Define test matrix** - BIND9 versions: 9.18.x (main), 9.20+ (feature/9.20 branch) - Platforms: Debian 11/12/13, Ubuntu 20.04/22.04/24.04 - Molecule scenarios: default and bind9-20 3. **Implementation requirements** - Lint checks (yamllint, ansible-lint) - Syntax validation (named-checkconf) - Molecule testing across platform matrix - Conditional tests based on branch (9.18 vs 9.20) 4. **Test coverage** - Meta/argument_specs validation - Template rendering - Role execution - Configuration syntax validation - Service startup and basic functionality ## Success Criteria - [ ] Pipeline runs successfully on pull requests - [ ] Linting checks pass (YAML, Ansible) - [ ] Molecule tests run for appropriate scenarios - [ ] Tests execute across version/platform matrix - [ ] Pipeline gates merges on failure - [ ] Clear reporting of test results - [ ] Performance: Reasonable build time (target: < 15 min) ## Related Issues - PR #14: BIND9 9.20 support implementation - Issue #15: Documentation clarification ## Notes - Pipeline should validate both main (9.18.x) and feature branches (9.20+) - Consider resource constraints for CI/CD runners - Molecule tests require root/privileged access to systemd - Use matrix strategy to avoid duplicate workflow definitions
daniel commented 2026-02-07 23:25:46 +00:00
Author
Owner
Copy Link

Closing as wontfix.

The current CI/CD pipeline is sufficient for the project's needs. The existing workflow provides:

  • Linting checks (yamllint, ansible-lint)
  • Basic Molecule testing on PR events

Further expansion of the test matrix and additional validation workflows is not required at this time.

Closing as **wontfix**. The current CI/CD pipeline is sufficient for the project's needs. The existing workflow provides: - Linting checks (yamllint, ansible-lint) - Basic Molecule testing on PR events Further expansion of the test matrix and additional validation workflows is not required at this time.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
daniel
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: daniel/ansible-bind9-role#16
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?