Dev Pipeline

This section covers the development pipeline: how code moves from your machine to production, CI/CD, and related workflows.

Developement usually is done by the LAN-HTTPS setup, which means the front end server is taken off docker to allow LIVE updates when coding.

Only repo owners are allowed to make changes to main and test-prod. Developers must make a feature branch to complete their work and must make a pull request.

When pull requests are made, gitlab will automatically start the pipeline which has 4 phases:

• Linting
• Building
• JUnit Testing and E2E Testing
• Deploying

If at any point one of these stages fail, the pipeline will stop, throw errors in the console and send out a notification to the Owner of the PR.