Testing code before committing using Jenkins and Jetbrains IDE (IDEA, PhpStorm ...)

In this article I want to tell about setting up Jenkins and almost any IDE from Jetbrains for the so-called Pre-Tested Commit . Pre-Tested Commit is a process of testing a modified code before a commit in which the developer, based on local changes, forms a diff, loads it into Jenkins and checks that the project build with its changes is successful. After that, the developer commits the changes to the repository.

Let's start with setting up Jenkins. For this we need the Patch Parameter Plugin .

Install it in Jenkins.


')
After installing the plugin, we set up a specific job to be able to transfer a patch with changes to it.



Pay attention to the “Check-out Strategy” setting. Before each new build we need to roll back the changes that came with the patch using “svn revert”.

After setting up Joba, we can download the patch directly through the Jenkins interface.



But this is not very convenient, so we will go further and configure the ability to run builds with changes directly from the IDE. For this we need the Jenkins Control Plugin plugin with Patch Parameter Plugin support .

Download it from here and install it in the IDE.



After installation, go to the settings of the plugin.



In the settings, set the address of Jenkins and the suffix added to the path of the files in diff. Updating the list of jobs I recommend to set to 1 minute for quick notification of the results of the build.



Everything! Now we can run builds with local changes directly from the IDE.

Through the download of the patch file.



Or, immediately based on the Changelist, create a patch and start a build with it.



The build status is displayed next to the Changelist name.



Thank you for your attention and stable builds!

Patch Parameter Plugin
Jenkins Control Plugin with Patch Parameter Plugin support

ps Wishes and comments on the plugin to the IDE are accepted.