[DevOps] Automated CI Pipeline Integration for Azure DevOps

[AlAfiz]

Description: Create a comprehensive CI pipeline configuration (azure-pipelines.yml) to automatically lint, test, and build the backend API on every Pull Request.
Context / Motivation: We must maintain a strict quality gate. Automating test execution guarantees that external GrantFox PRs do not break the API build before maintainers merge them into the main branch.
Acceptance Criteria: - [ ] Define the pipeline stages: Lint, Test, and Build.

• Configure the pipeline to run eslint and prettier checks.
• Execute the Jest test suite and generate a code coverage report.
• Ensure the pipeline fails and blocks the PR if any stage fails or if test coverage drops below 80%.
  Technical Pointers: Optimize the pipeline duration by caching the npm or yarn dependency directories between runs. Use a Node.js toolchain task to enforce the correct runtime version across all build agents.

[MoscowDev]

Hello,

I would like to implement a comprehensive Azure DevOps CI pipeline to enforce quality gates for the backend API and ensure every Pull Request is properly validated before merging.

I have experience working with CI/CD systems, Node.js backend pipelines, and automated testing workflows, and I can deliver a reliable and optimized pipeline configuration.

My approach will include:

• Creating an azure-pipelines.yml file with clearly defined stages: Lint, Test, and Build.
• Configuring a Node.js toolchain task to enforce a consistent runtime version across all build agents.
• Implementing a Lint stage that runs both ESLint and Prettier checks to enforce code style and consistency.
• Adding a Test stage that executes the full Jest test suite and generates a code coverage report.
• Enforcing a strict coverage threshold of 80%, ensuring the pipeline fails if coverage drops below this limit.
• Adding a Build stage to compile and verify the backend API successfully builds after tests pass.
• Optimizing pipeline performance by caching node_modules or package manager dependency directories between runs to reduce build time.
• Ensuring the pipeline is configured to run on every Pull Request and block merges when any stage fails.

This setup will provide a strong quality gate, prevent broken code from entering the main branch, and improve the overall reliability of the backend system.

Best regards,
Nnaji Moses Ogomegbunam

[grantfox-oss]

🦊 GrantFox — @MoscowDev has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #174)
2. Your PR will be reviewed by the BETAIL-BOYS maintainers

Good luck! Track your progress on GrantFox.