GitHub Pipelines

[shahraz1998]

User story

1. As a team
2. We want readable, well tested, and working code
3. So that our codebase does not break and stays manageable

Acceptance criteria

• Create a CI/CD Pipeline that performs the following actions:
• on main:
  • [x] lint
  • [x] build
  • [x] test
  • [x] deploy (when we have an environment)
• on branch/merge-request
  • [x] lint
  • [x] build
  • [x] test
• scheduled:
  • check that the dependencies of the project are in the list of whitelisted dependencies (no copyleft licenses); e.g. like this license-checker --csv --onlyAllow \"Apache-2.0; Apache*; BSD; BSD-2-Clause; BSD-3-Clause; ISC; MIT; Unlicense; WTFPL; CC-BY-3.0; CC0-1.0\" --production

Definition of done (DoD)

• A CI/CD Pipeline satisfying the AC is running for the project

DoD general criteria

• Feature has been fully implemented
• Feature has been merged into the mainline
• All acceptance criteria were met
• Product owner approved features
• All tests are passing
• Developers agreed to release