[noxToken]

CI will always be product specific unless you're going to create your own scripts for your pipeline. Even then, your script for executing tests, deploying, etc. will still be dependent on your stack.

Some general guidelines:

When a developer's branch is pushed publicly, compile it and run tests. It must pass before being allowed to merge into develop/master/${specific-branch}. Require that merges to those branches are only fast-forward merges.

The types of tests needed will be dependent on your application. Make sure they're all green before proceeding. If not, log the failing tests. Depending on your application, you may want to have certain testing metrics also fail the build. For example, require that at least 50% of new lines of code have test coverage and 60% of your overall source code have coverage.

Run any static analysis tools and linters. Configure which rules should trigger failures or warnings.

Run any other scripts that aren't related to code quality like minification or building binaries.

Deploy your application to the proper environment.

This is a bare-bones list. Your application may have many more steps, but this should get you started.