Continuous integration Experiment--Personal summary

Continuous integration Experiment--Personal summary thudmteam Li Sanghe

The nearly 10-day continuous integration experiment is finally over, and the continuous integration experiment requires that each team perfect a public number to rob a ticket. I mainly

Responsible for unit testing and functional testing content, summer vacation in the back-end of the curriculum in the self-study Report preparation is unit testing, the experiment

Have a lot of help.

In general, the final result of the continuous integration experiment is not particularly satisfied, a little problem in the division of labor, estimating the overall workload of the experiment is wrong,

Also separated a few people to continue to develop large operations, and finally feel a little less time. But take this experiment as a valuable experience and remember not to do it again next time.

This kind of mistake, assigning a good workload, to catch the job DDL is really not very good, do not want to feel again.

Through this experiment, our THUDM team has a deeper understanding of the public number, how the public number works, the public number is really used for the development of a product,

What are the benefits and what are the disadvantages? THUDM team to develop the missile screen system launch client is also based on the public number, in the future we have to think about our

How to make the advantage of the public is more prominent, how to make up for the shortcomings of the public, but also remember to control the amount of division of labor, pay attention to the iteration cycle and continuous integration work.

this the THUDM team's next experiment the foundation for the development of large operations.

Continuous integration Experiment--Personal summary