There are projects such as Capistrano, phpUnderControl, and so on.

Why use them in PCP, when you can just commit changes to the process, make an update on the girl's machine, and if everything is fine there, update the code on the production?

I do not understand what is the profit from their use. Explain, please?

    1 answer 1

    Read about continuous integration. Read what phpUnit is. About testing. In general, the project itself is usually stored in the VCS, from there it gets, various tests are run (on syntax, on functions, etc.) and if everything is good, then it goes further along the conveyor ... if not, then it will be updated again.

    I mean smoke tests and more detailed tests that run automatically.

    It is clear that for very small projects it is a waste of resources, but in large projects without it there is nowhere.

    • Ah, we don’t have any pipeline, as there are no tests. On the developer's machine, the project is working, which means the syntax is ok, the logic is ok, we are driving the machine to the dev to check with other dudes. If everything is OK there, an update on production. - nolka
    • Yes it can and depends on the project, on the requirements for the project. Such systems simply allow one button to do all the necessary operations, such as pulling a project out of VCS, running tests, uploading to the server, restarting (if necessary) some services ... in general, everything that will be programmed for this action. Check in, read, maybe like it. - thunder
    • I need that, all-nothing: In order to fill the project version with auto-increment every time before uploading it to the production, or to the dev in the config)) - nolka
    • Well, this is understandable, I suggested reading for general development, I also managed to live without this all my life, and indeed without vcs, I ran into work and now I understood what was missing for me before. :) - thunder