In general, once software development (that is, such as feature, bug-fix, or hot-fix) is done, and code is committed last time to a specific forked source control branch, then it gets merged to a development and, subsequently, into the master branch. Usually, a peer code review takes place before merging a code into the development branch or any other branch from the forked branch. Now, if this development has been executed using a language that requires a compilation such as Java, VB.NET, or C#, it needs to trigger a build process. Again, upon committing a new change or development, a build process is triggered with the new change.
In broad terms, the build process is nothing but compiling the project. If this development or change is done at the level where compilation is not required, such as HTML, JavaScript, or PHP, then it doesn't need to trigger...
