I encountered many pitfalls in the process of implementing Jenkins automated packaging. When I was preparing to use Jenkins to implement automated packaging a few days ago, I found that the console output log reported "unable to open png file". Many people on Baidu on the Internet say that it is because the image file path is too long. Windows has a length limit on the file path. If the image path length exceeds this limit, the file cannot be read, so the project cannot be placed too deep.
Why is the project placed so deep? The fundamental reason is that when we downloaded and installed Jenkins, the project storage address was selected as the default instead of a customized storage address . As a result, the file address was too long during automatic packaging, resulting in unsuccessful packaging. Then How to modify the project storage address?
1. Modify the project storage address to solve the problem of being unable to open png file when automatically packaging.
After entering, find "Configuration" and click to enter
Find the Advanced button as shown above. After clicking, the options shown below will appear:
Then click the Apply button to apply. It should be noted that after configuring the new project storage address, you need to close Jenkins and reopen it for it to take effect.