Alawein Cicd Pipeline Standardization Prompt

assetactive

Alawein Cicd Pipeline Standardization Prompt

Source: alawein-cicd-pipeline-standardization-prompt.md (ingested 2026-03-28)

Develop and implement a standardized Continuous Integration/Continuous Deployment (CI/CD) pipeline for the "alawein" folder and its repos/projects, focusing on efficiency, reliability, and resource optimization.

Phase 1: Standardize CI/CD for "alawein"

  1. Define CI/CD Workflow:

    • Establish a consistent workflow structure for all repositories within the "alawein" project.
    • Include stages for:
      • Linting and Static Analysis: Integrate tools for code quality checks (e.g., ESLint, Prettier, SonarQube).
      • Unit and Integration Testing: Execute comprehensive test suites.
      • Build Artifact Generation: Compile code and create deployable artifacts.
      • Security Scanning: Incorporate vulnerability scanning (SAST/DAST) where applicable.
      • Deployment (Staging/Production): Define automated deployment steps to target environments.
    • Ensure the pipeline is triggered appropriately on code pushes, pull requests, and scheduled events.

  2. Implement Best Practices:

    • Utilize a consistent CI/CD platform (e.g., GitHub Actions, GitLab CI, Jenkins).
    • Implement caching mechanisms for dependencies to speed up build times.
    • Parameterize sensitive information using secrets management.
    • Ensure proper versioning and tagging of releases.

Phase 2: Optimize Resource Usage and Prevent Loops

  1. Monitor and Optimize "Actions 3000" Usage:

    • Implement monitoring for CI/CD resource consumption, specifically targeting GitHub Actions minutes or equivalent platform metrics.
    • Analyze workflow run times and identify bottlenecks.
    • Optimization Strategies:
      • Conditional Runs: Configure jobs or steps to run only when necessary (e.g., based on changed files, branch names).
      • Parallelization: Break down long-running jobs into smaller, parallelizable tasks.
      • Caching: Aggressively cache build dependencies and intermediate artifacts.
      • Self-Hosted Runners (if applicable): Evaluate the cost-effectiveness of using self-hosted runners for specific workloads.
      • Artifact Retention Policies: Set appropriate retention periods for build artifacts to manage storage.
    • Success Criteria: Maintain CI/CD resource consumption below the "actions 3000" limit consistently.

  2. Prevent Infinite Loops and Redundant Triggers:

    • Carefully define CI/CD triggers to avoid recursive or self-triggering workflows.
    • Implement conditional logic within workflows to prevent unnecessary re-runs (e.g., if: github.event.pull_request.head.repo.full_name == github.repository).
    • Ensure that deployment steps do not inadvertently trigger new CI/CD runs on the same branch or repository.
    • Validate that workflow changes are thoroughly tested in a non-production environment before deployment.

Phase 3: CI/CD Management Across Organizations

  1. Remove CI/CD from Other Organizations:

    • Identify all organizations owned by the user, excluding "morphism-systems".
    • For each repository within these identified organizations, systematically disable or remove all existing CI/CD configurations (e.g., .github/workflows directories for GitHub Actions, .gitlab-ci.yml files, Jenkinsfile configurations).
    • Verify that no automated build or deployment processes remain active in these organizations.

  2. Revise CI/CD for "morphism-systems" (Optional but Recommended):

    • Conduct a comprehensive audit of the existing CI/CD pipelines within the "morphism-systems" organization.
    • Review Areas:
      • Efficiency: Identify opportunities to reduce build times and resource consumption.
      • Reliability: Enhance error handling, retry mechanisms, and notification systems.
      • Security: Ensure adherence to security best practices, including secret management and dependency scanning.
      • Maintainability: Refactor complex workflows, improve documentation, and standardize naming conventions.
      • Scalability: Assess the pipeline's ability to handle increased load and project growth.
    • Implement recommended revisions to optimize the "morphism-systems" CI/CD pipelines based on the audit findings.