One of the key points of agility is fast feedback.
From the earliest daily build to the present continuous integration, developers have taken a series of measures to quickly obtain system feedback. In addition, the feedback information is getting faster and faster, and the information requirements are getting higher and higher.
The steps for an integration process are as follows: automatic update-> compile and build-> Automatic Test-> report integration results. You need to write the process commands (such as the updated version), and automatically link the processes with the support of the integrated server.
There are many available integration servers, and dstp also provides support for continuous integration.
Dstp provides the following functions to support continuous integration.
1. Set the integrated command through the graphical interface, and send the command to the specified Machine for execution in order. Complete version updates, build compilation, and test.
2. allow you to automatically send the Integration Report to the specified personnel when the integration ends/fails/succeeded/partially fails. In the Integration Report, the failure part is automatically highlighted in red; the error message is automatically displayed, and even the line of code that contains the error is displayed.
3. You can set the integration cycle, such as daily/weekly/monthly/, or automatically start the integration every fixed minute.
4. Integration with SVN to automatically detect changes to the svn repository. You can set SVN to automatically start integration after each modification. When the integration fails, the system automatically sends a Report to the Code submitter and the specified project personnel, urging rapid correction to ensure that the Code is available at any time.
Set the integration command:
Dstp uses the graphical interface to set commands. The setting process is simple. You can right-click to add, delete, and modify commands (activities) and set the order of commands. For example, it indicates that several processes are set. After the version is updated, the system continues to compile the version. After the version is compiled, the system runs the automatic test.
Let's take a look at how to set the compile version command. Double-click the build node. A dialog box is displayed, as shown in figure
When setting a command, you can set the Command Execution Machine (the machine must be integrated with the installation client) and the environment variable in advance. Dstp automatically sends the command to the specified Machine for execution. And get the execution result.
At the same time, commands are executed sequentially. For example, if the version compilation fails, the version loading test is invalid. dstp can determine whether the execution result returned by each machine is successful or fails, determine whether to continue the next integration step based on the settings.
Integrated Report:
After the integration steps are completed, dstp can send the Integration Report to the specified project personnel as required.
You can select whether to send notifications based on the integrated results, and set the notification recipient.
The dstp integrated report format sent to the notification recipient is as follows:
The report lists the running time and running results of the integrated commands. The failed commands are highlighted in red.
Click error information. The system automatically displays the error information of this integration.
The error message shows that an error occurs in row 4 of test. C.
Integration cycle:
Dstp integration servers can set the integration cycle to automatically start integration at the specified time. In addition, dstp is closely integrated with SVN to automatically detect SVN changes. You can set SVN to automatically start integration after each modification. When the integration fails, the system automatically sends a Report to the Code submitter and the specified project personnel, urging rapid correction to ensure that the Code is available at any time.
There have been many discussions about continuous integration. But there are not many companies that actually implement it. Many companies may only build on a daily basis and do not perform many automated tests. This is because the automatic test environment usually involves the cooperation of multiple machines, and it is difficult to implement without a good integrated server. More importantly, the automatic test should be constructed according to the actual project, the technical difficulty and workload in this area are not small.
When agility becomes popular, test-driven development is also gaining popularity, and the value of testing is becoming more and more recognized. When you gradually realize that integration is valuable in testing, continuous integration becomes popular, and development becomes more agile ~~
