| <?xml version="1.0" encoding="UTF-8"?> |
| <!DOCTYPE html PUBLIC "-//W3C/DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd"> |
| <!-- VERSION rmc:7.1.0 --> |
| <html xmlns="http://www.w3.org/1999/xhtml"> |
| <head> |
| <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> |
| <!-- START NON-TRANSLATABLE --> |
| <title>\openup_basic\guidances\concepts\continuous_integration.xmi</title> |
| </head> |
| <!-- WARNING: do not modify the generated comments in this file below this line. They are used as markers for the import process. --> |
| <body> |
| Element Name: continuous_integration.xmi<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: presentationName<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:presentationName,_B3xkEPD0EdqYgerqi84oCA CRC: 751312288 -->Continuous Integration<!-- END:presentationName,_B3xkEPD0EdqYgerqi84oCA --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: briefDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:briefDescription,_B3xkEPD0EdqYgerqi84oCA CRC: 3377508991 -->This concept introduces the idea of creating regular (at least daily) integrations in order to reduce integration risks, find bugs earlier, and drive a collaborative work environment.<!-- END:briefDescription,_B3xkEPD0EdqYgerqi84oCA --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: mainDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:mainDescription,-dhAMzNZNWufBnW0fPYQtBA CRC: 1198681502 --><p> |
| Continuous integration is an implementation practice where team members compile and test (integrate) their work |
| frequently (at least daily). Integration errors should be detected as quickly as possible, either from compiler errors |
| or errors reported by the test suite. Ideally the integration is done automatically when an updated version of |
| source code is checked into the configuration management system. |
| </p> |
| <p> |
| Benefits: |
| </p> |
| <ol> |
| <li> |
| Improved error detection. Continuous integration enables you to detect and address errors early, often |
| minutes after they’ve been injected into the product. Note that you still need a good test suite. |
| </li> |
| <li> |
| Improved system integration. By integrating continuously throughout your project you know that you can |
| actually build it, thereby mitigating integration surprises at the end of the lifecycle. |
| </li> |
| <li> |
| Reduced technical risk. You always have an up-to-date system against which to test. |
| </li> |
| <li> |
| Reduced management risk. By continuously integrating your system you know exactly how much functionality that |
| you’ve built to date, improving your ability to predict when and if you’re actually going to be able to deliver the |
| necessary functionality. |
| </li> |
| <li> |
| Improved collaboration. Continuous integration enables team members to work together safely. They know |
| that they can make a change to their code, integrate the system, and determine very quickly whether or not their |
| change worked.<br /> |
| </li> |
| </ol><!-- END:mainDescription,-dhAMzNZNWufBnW0fPYQtBA --> |
| </body> |
| </html> |
