Tiny CI of your Symfony project in 2 minutes
Without water about how to do in 10 minutes:
1. Check your composer.json for serious and not serious errors, like a non-optimal autoload
2. Check your composer.lock for security vulnerabilities in packages
3. Check your database for not forgetting anything.
4. Check your YAML files
5. Checking Coding Style by symfony
It surprises me why many people do not use this functionality in their projects that have long been working on sales. Tutorial is very small, but everything is on the case. And I still hope that you can emphasize to yourself something from this material.
1) Check your composer.json for serious and not serious errors, like a non-optimal autoload:
2) Check your composer.lock for vulnerabilities in packages:
If any vulnerabilities with this or that package are found in the database, we will see this picture:
And CI will return the status that the program was incorrectly completed, which will break the build and attract the attention of the developer.
Read more about the project - security.sensiolabs.org
Database - security.sensiolabs.org/database
3) Check your database
4) Check your YAML files
Install matthiasnoback / symfony-config-test to test our YAML files in the project:
5. Checking Coding Style by symfony
Install escapestudios / symfony2-coding-standard and squizlabs / php_codesniffer , then do the following:
In case there are violations, we will get something like this with a full description:
1. Check your composer.json for serious and not serious errors, like a non-optimal autoload
2. Check your composer.lock for security vulnerabilities in packages
3. Check your database for not forgetting anything.
4. Check your YAML files
5. Checking Coding Style by symfony
It surprises me why many people do not use this functionality in their projects that have long been working on sales. Tutorial is very small, but everything is on the case. And I still hope that you can emphasize to yourself something from this material.
1) Check your composer.json for serious and not serious errors, like a non-optimal autoload:
./composer.phar validate --no-check-all --strict2) Check your composer.lock for vulnerabilities in packages:
php vendor/bin/security-checker security:checkIf any vulnerabilities with this or that package are found in the database, we will see this picture:
And CI will return the status that the program was incorrectly completed, which will break the build and attract the attention of the developer.
Read more about the project - security.sensiolabs.org
Database - security.sensiolabs.org/database
3) Check your database
php bin/console doctrine:schema:validate -e=prodSituation:
The developer has made changes to the essence. But I forgot to create a migration, but we are normal and we use migrations in order to change something in the database during the sale? And then the team leader missed that there is no migration to new changes. Execute this command after rolling all migrations to the database. The team will verify that there are no more changes to the database in accordance with the entity mapping, which gives a 100% guarantee that no one is forgotten, nothing is forgotten.
4) Check your YAML files
Install matthiasnoback / symfony-config-test to test our YAML files in the project:
php bin/console lint:yaml app/config/php bin/console lint:yaml src/AppBundle/Resources/config/5. Checking Coding Style by symfony
Install escapestudios / symfony2-coding-standard and squizlabs / php_codesniffer , then do the following:
php vendor/bin/phpcs ./src -p --encoding=utf-8 --extensions=php --ignore=Tests --standard=./vendor/escapestudios/symfony2-coding-standard/Symfony2In case there are violations, we will get something like this with a full description:
')
Source: https://habr.com/ru/post/346472/
All Articles