Last time I mentioned the problems that need to be dealt with in continuous integration. The biggest problem is the coordination and writing of the team. I also said that confluence and SVN must be equipped to fight. We chose Confluence to work with SVN and Jenkins on the development.

Practice the management style of a large project team of more than 50 people

We did it in accordance with the style of our previous project. We did not use automatic tools at that time, but also supported the national project by relying on the process of this project. Later, the industry was in recession, but we basically had no problems with this process.

  • Project name

Online processes: goods, transactions, Web

1. Commodity item. War 2. Transaction Item. War 3. Web display item. War

#### Release process

  • 1. Make release plans

The creation of tables is done by testers or platform managers and filled by developers

    1. The SVN builds a version library

Create two folders, one daily and one release. 1. Update the WAR package under the daily version number to know how many versions are released online and which systems are designed for each version. 2. Release is a collection of WAR packages upgraded by a project

  • 3. Submit the program version file to the daily directory

Submit the project to the Daily directory according to the form in confluence for this update

  • 4. Submit the configuration file and database script to the daily directory

Submit the project to the Daily directory according to the form in confluence for this update

  • 5. Update the test environment

Update the test environment through the projects in the release. For example, there are three WAR packages in V1.0.0. O&m personnel update the specified project according to these three WAR packages

  • 6. Update the test environment. 7

The tester notifies operations to place the WAR in the V1.0.0 project under the specified release

  • 8. Post to rehearsal environment

The testers continued to test and there were no problems

  • 9. Release to production

  • Process general

If the number of people in the company is very small, only 1-3 people, it is not recommended to be so complicated, in fact, so complicated is for multi-personnel control, rationalization of personnel control. Avoid mistakes and write collaboratively. The diagram is drawn in accordance with the process of all success. In fact, it is also repeated in the testing stage until there is no problem with the system.

PS: Actually, this flow chart is quite standard. It is best to work with tomcat.sh and deploy.sh written earlier. Engage in development must be a tool process, the future is such a tool, process, modular. It’s not a single soldier, coordination is more important than your code ability, code companies hire people who write code, in fact. To be honest, I’m not very good at coordination. Very bad at doing 4 or 5 things in parallel. In process management, in addition to testers, daily managers, perhaps the project manager, he needs to deal with all aspects of coordination, this ability needs more training.