On the CI side of the story
Last time, as you pushed the changes to your GitHub repository, you probably received a couple of e-mails informing you about the success or failure of the new build. You can celebrate if your build is successful. However, if it is not, don't panic and just follow this two-step process.
First, make sure that all unit tests and functional tests in your local machine pass successfully. If there is something wrong here, you should not expect a successful build from your Jenkins instance on EC2. For those who created or modified the tests and codes themselves, it could be a simple misspelling error or some serious logical issue. Spot the problem using log messages and fix it. Then try again.
For those who cloned the code ...
Get Mastering Symfony now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
