The benefit is that you know – immediately – when someone has broken the build. This means either
- They committed code that prevents compilation, which would screw any one up who did an ‘update’, or
- They committed code that broke some tests, which either means they introduced a bug that needs to be fixed, or the tests need to be updated to reflect the change in the code.
Automated builds have become a cornerstone of agile development. Every time a developer checks in a change, a tool like Jenkins checks out all the sources, builds everything and reports back with immediate feedback. It is better described as Continuous Build.
Latest posts by Rajesh Kumar (see all)
- What is Mobile Virtual Network Operator? - April 18, 2024
- What is Solr? - April 17, 2024
- Difference between UBUNTU and UBUNTU PRO - April 17, 2024