Problems encountered in Jenkins' release of H5 developed by uniapp

​

 ​ edit

Catalog

​ edit  

Preface ：

One 、 problem ：        

Two 、 Solving experiences ：

        1、 Ideas 1（ You don't succeed ）：

       2、 Ideas 2（ success ）：        

3、 ... and 、 Cause analysis ：

summary

---

Preface ：

        background ： For historical reasons , The company has a historical project using vue Developed official account H5, A native wechat applet . The functions of both ends are exactly the same , But two projects need to be maintained , Recently, the customer has raised a need to modify some functions , After the blogger receives the demand , I feel that maintaining two sets of code is not just repeated development , It's troublesome to test , Because two people developed different terminals before , Lead to most bug It's all caused by inconsistency at both ends . To save time and maintenance costs , Improve the efficiency of development and testing , In repeated comparative research , Finally, I chose uniapp The technical framework is reconstructed by merging both ends .

---

One 、 problem ：        

         Company use Jenkins Issue official account H5, In the use of uniapp Before , The release has been very stable , Replace uniapp after , Issue official account H5 Occasionally, there will be inexplicable abnormalities , It makes me and O & M have a headache , An error is as follows ：

​ edit

---

Two 、 Solving experiences ：

         The exception throw cannot locate whether it is the front-end problem or the operation and maintenance deployment problem , At first, we can only follow the routine Jenkins Error reporting search process , But this is strange Jenkins Release normal , It's just that the project can't run , Only the screenshot of the console appeal is wrong , So there is no corresponding solution at all , I can only continue to guess whether it is Jenkins Is there a problem here .

        1、 Ideas 1（ You don't succeed ）：

         Because local compilation , Local packaging and publishing can be successful , Later, I guessed whether it was local node Version follows Jenkins Online configuration node The version is wrong , So we tried again , Local node The version is modified to try to troubleshoot as online , It's OK not to try , Try to scare , There is also a problem with local packaging after trying . Fortunately, I made a backup before , Otherwise, there is no alternative distribution plan ...

       2、 Ideas 2（ success ）：        

         Readjust your thinking , It is used to point to the location where the error is found during local debugging  async+await , So I wondered if it was node Chinese analysis ES6 turn ES5 Of babel There is a problem with the plug-in version , Because I always use yarn, This time try to delete node-modules,node The version is still fixed in  14, Use npm install, then npm run serve try , Finally, it's ok .

---

3、 ... and 、 Cause analysis ：

        yarn install The reason for the error is because npm and yarn The merge strategy is different when installing dependencies , Cause the dependent version to be different from the expected result .
If you still want to pass yarn Management dependence , You can modify the project root directory package.json in devDeps rely on @babel/runtime The version is ~7.17.9, And increase

···"resolutions":{"@babel/runtime": "~7.17.9"}···

Lock the dependent version .

---

summary

         From problem discovery to solution , At first, I thought it was Jenkins The problem of , Wasted some energy , Then adjust the direction. , Until we find a solution . Although it is very tortuous , But still happy . So record that . I hope this record can help you to see this article .

​ edit

​