Interviewer: Can you tell me about the release process of WeChat Mini Programs?

[[431428]]

This article is reprinted from the WeChat public account "JS Daily Question", the author is Huihui. Please contact the JS Daily Question public account to reprint this article.

1. Background

In medium and large companies, the division of labor is very detailed, and generally employees with different job roles will participate in the same Mini Program project at the same time. For this reason, the Mini Program platform has designed different permission management so that project managers can manage the collaborative work of the entire team more efficiently.

In the past, after developing a web page, we needed to put the web page code and resources on the server so that users could access them through the Internet.

In the mini program platform, after the developer completes the development, he needs to submit the mini program code package in the developer tool, and then publish the mini program in the mini program background.

2. Process

The release process is mainly divided into three parts:

• Upload the code
• Submit for review
• Release version

Upload the code

In the developer tools, you can click the code upload function:

Then you can fill in the version information:

Then click Upload, and the compiler will prompt that the code has been uploaded successfully.

Submit for review

After uploading the code, you can log in to the official website of the WeChat public account, click [Development Management], and view the application details:

The review process requires filling in the review information, as shown below:

After successful submission, the following figure is shown:

Release version

Once the review is passed, it can be submitted for release.

After the release is successful, it is as follows:

3. Extension

The above is the simplest process for publishing mini program code. The general process is as follows:

• Create a new branch on the code management server
• Develop and test new requirements
• After the test is completed, merge the local branch into the master branch
• Pull the latest code from the master branch and execute the build command to generate the mini-program executable file
• Click "Upload" in the developer tools
• Arraignment
• release

However, when faced with multi-person coordinated development, it is possible that the code that has been launched has not yet been merged into the master.

Therefore, we can consider automated build and deployment, which is to automate a series of processes from development to deployment, so that they are connected and coherent. When the build fails, the developer can be informed, and when the build succeeds, the tester and implementation personnel can be informed. Please refer to the following flowchart:

References

https://juejin.cn/post/6994414162700927012

https://www.leapcloud.cn/website/docs/doc_config/xiaochengxu/xiaochengxu.html