ci-1

https://dzone.com/storage/assets/5628509-dzone-rc84-cipatternsandantipatterns.pdf

Automatically build the software at every change (eg. gerrit plugin for jenkins)
Branching policy: all changes to a branch, verification, merge to master
Tag or Label the build with unique name so that you can refer to run the same build at another time
Send automated feedback from the CI server to development team members involved in the build (email, slack, ...)
Fix broken builds (master) immediately!
Create build scripts
All builds should be run through a single command
Run building on a dedicated machine
Externalize all variable values from the application configuration into build-time properties.
Use tokens so the build process knows where to add variable values
Script database changes
The data for each environment should be a subset of the whole, and scrubbed of sensitive information.
Create a lightweight version of your database (only enough records to test functionality)
Any data import or manipulation should be scripted so it can be performed via command line.
Store the scripts for updating the database and its data in the version control system with the code and annotate appropriately

Tests running with every build ensures that nothing has been broken and that the code is maintaining superior quality.
The build scripts should include running tests against all code in the project. Tests should be as comprehensive as possible and can include unit tests, end-to-end tests, smoke tests, or UI tests. Testing should be done on all new code.

Create smoke tests that can be used by CI servers, developers, QA, and testing as a pre-check to confirm the most important functionality as they work, or before committing resources to a full build.