After adding /vendor to the git repository, docker deploys, the analysis of the upgrade failed

by 永夜 · 2020/05/11

浏览量： 1

1. Edit .gitignore and add /vendor to the git warehouse, as shown in Figure 1

Figure 1

# composer vendor dir
# /vendor

2. Failed to build in Jenkins, check Console output. as shown in Figure 2

Figure 2

[0mThe command '/bin/sh -c chown -R nginx:nginx /mcloud/www/ &amp;&amp;     rm -rf /etc/nginx/conf.d/status.conf &amp;&amp;     chmod +x /usr/local/bin/composer &amp;&amp;     composer config -g repo.packagist composer https://mirrors.aliyun.com/composer/ &amp;&amp;     cd /mcloud/www/pcs-api &amp;&amp;     composer install' returned a non-zero code: 1
Build step 'Docker Build and Publish' marked build as failure
Finished: FAILURE

3. Docker deployment, delete the composer install. Edit Dockerfile. as shown in Figure 3

Docker 部署，删除 composer install。编辑 Dockerfile。

Figure 3

RUN chown -R nginx:nginx /mcloud/www/ &amp;&amp; \
    rm -rf /etc/nginx/conf.d/status.conf &amp;&amp; \
    chmod +x /usr/local/bin/composer &amp;&amp; \
    composer config -g repo.packagist composer https://mirrors.aliyun.com/composer/ &amp;&amp; \
    cd /mcloud/www/pcs-api &amp;&amp; \
    composer install

RUN chown -R nginx:nginx /mcloud/www/ &amp;&amp; \
    rm -rf /etc/nginx/conf.d/status.conf

4. Build successfully in Jenkins. as shown in Figure 4

Figure 4

5. Failed to start in Rancher, check the log. as shown in Figure 5

Figure 5

2020/5/8 下午2:48:45
2020/5/8 下午2:48:45  ... initialization completed.
2020/5/8 下午2:48:45
2020/5/8 下午2:48:45 PCS_API_CFG_MIGRATE=true

6. Edit build/c_files/config/init/console_init.sh. Delete the related commands for $PCS_API_CFG_MIGrate == “true”. as shown in Figure 6

编辑 build/c_files/config/init/console_init.sh。删除 $PCS_API_CFG_MIGRATE == "true" 的相关命令。

Figure 6

7. Start successfully in Rancher, check the log. as shown in Figure 7

Figure 7

2020/5/8 下午2:48:45
2020/5/8 下午2:48:45  ... initialization completed.
2020/5/8 下午2:48:45
2020/5/8 下午2:48:45 PCS_API_CFG_MIGRATE=true

8. Enter the container and manually execute the related commands of $PCS_API_CFG_MIGrate == “true”. It didn’t run successfully because there is no corresponding output. as shown in Figure 8

进入容器，手动执行 $PCS_API_CFG_MIGRATE == "true" 的相关命令。未成功运行，因为无相应输出。

9. Enter the container that adds /vendor to the git warehouse. Manually execute the relevant commands of $PCS_API_CFG_MIGrate == “true”. Run successfully, because there is a corresponding output. as shown in Figure 9

进入将 /vendor 加入至 Git 仓库前的容器。手动执行 $PCS_API_CFG_MIGRATE == "true" 的相关命令。成功运行，因为有相应输出。

Figure 9

10. New deployment in the local environment, manually execute the relevant commands of $PCS_API_CFG_MIGrate == “true”. Failed to run successfully, an error is reported. As shown in Figure 10

在本地环境中全新部署，手动执行 $PCS_API_CFG_MIGRATE == "true" 的相关命令。未成功运行，报错。

Figure 10

PS E:\wwwroot\pcs-api-develop> ./yii migrate --migrationPath=@yii/log/migrations/ --interactive=0
PHP Warning:  require(E:\wwwroot\pcs-api-develop\vendor\composer/../codeception/verify/src/Codeception/function.php): fa
iled to open stream: No such file or directory in E:\wwwroot\pcs-api-develop\vendor\composer\autoload_real.php on line 6
6

Warning: require(E:\wwwroot\pcs-api-develop\vendor\composer/../codeception/verify/src/Codeception/function.php): failed
to open stream: No such file or directory in E:\wwwroot\pcs-api-develop\vendor\composer\autoload_real.php on line 66
PHP Fatal error:  require(): Failed opening required 'E:\wwwroot\pcs-api-develop\vendor\composer/../codeception/verify/s
rc/Codeception/function.php' (include_path='.;C:\php\pear') in E:\wwwroot\pcs-api-develop\vendor\composer\autoload_real.
php on line 66

Fatal error: require(): Failed opening required 'E:\wwwroot\pcs-api-develop\vendor\composer/../codeception/verify/src/Co
deception/function.php' (include_path='.;C:\php\pear') in E:\wwwroot\pcs-api-develop\vendor\composer\autoload_real.php o
n line 66

11. File E:\wwwroot\pcs-api-develop\vendor\composer/../codeception/verify/src/codeception/function.php does not exist, as shown in Figure 11

$文件 E:\wwwroot\pcs-api-develop\vendor\composer/../codeception/verify/src/Codeception/function.php 不存在$

Figure 11

12. Enter the container that adds /vendor to the git warehouse. The file \vendor\composer/../codeception/verify/src/codeception/function.php exists. as shown in Figure 12

$进入将 /vendor 加入至 Git 仓库前的容器。文件 \vendor\composer/../codeception/verify/src/Codeception/function.php 存在。$

Figure 12

13. Check e:\wwwroot\pcs-api\vendor\codeception\verify, there are corresponding files in its directory. And git shows that it has been submitted to the warehouse. as shown in Figure 13

$查看 E:\wwwroot\pcs-api\vendor\codeception\verify，其目录下存在相应的文件。且 Git 显示是已经提交至仓库。$

Figure 13

14. Enter the local environment before adding /vendor to the git warehouse. Discover that \vendor\codeception\verify already exists in git. It’s just the master branch. Figure 14

$进入将 /vendor 加入至 Git 仓库前的本地环境。发现 \vendor\codeception\verify 已经存在于 Git 中。只不过是 master 分支。$

Figure 14

15. Finally decide to switch to the master branch and merge the code of the develop branch. Push to the remote master branch. File in the remote repository:\vendor\composer/../codeception/verify/src/codeception/function.php still does not exist. as shown in Figure 15

$最终决定切换至 master 分支，合并 develop 分支的代码。再推送至远程的 master 分支。在远程仓库中文件：\vendor\composer/../codeception/verify/src/Codeception/function.php 仍然不存在。$

Figure 15

16. Delete the directory: E:\wwwroot\pcs-api\vendor\codeception\verify\.git, add the files that have not been submitted to the warehouse, and add them to the warehouse. As shown in Figure 16, 17

$删除目录：E:\wwwroot\pcs-api\vendor\codeception\verify\.git，将未显示已经提交至仓库的文件，添加至仓库。$

Figure 16

$删除目录：E:\wwwroot\pcs-api\vendor\codeception\verify\.git，将未显示已经提交至仓库的文件，添加至仓库。$

Figure 17

17. New deployment in the local environment, manually execute the relevant commands of $PCS_API_CFG_MIGrate == “true”. The error is not run successfully, but the corresponding error of /codeception/verify has been resolved. Refer to step 16 for the same processing. Any similar problems that follow the error when running the command can be handled in this way.

PS E:\wwwroot\pcs-api-develop> ./yii migrate --migrationPath=@yii/log/migrations/ --interactive=0
PHP Warning:  require(E:\wwwroot\pcs-api-develop\vendor\composer/../myclabs/deep-copy/src/DeepCopy/deep_copy.php): faile
d to open stream: No such file or directory in E:\wwwroot\pcs-api-develop\vendor\composer\autoload_real.php on line 66

Warning: require(E:\wwwroot\pcs-api-develop\vendor\composer/../myclabs/deep-copy/src/DeepCopy/deep_copy.php): failed to
open stream: No such file or directory in E:\wwwroot\pcs-api-develop\vendor\composer\autoload_real.php on line 66
PHP Fatal error:  require(): Failed opening required 'E:\wwwroot\pcs-api-develop\vendor\composer/../myclabs/deep-copy/sr
c/DeepCopy/deep_copy.php' (include_path='.;C:\php\pear') in E:\wwwroot\pcs-api-develop\vendor\composer\autoload_real.php
 on line 66

Fatal error: require(): Failed opening required 'E:\wwwroot\pcs-api-develop\vendor\composer/../myclabs/deep-copy/src/Dee
pCopy/deep_copy.php' (include_path='.;C:\php\pear') in E:\wwwroot\pcs-api-develop\vendor\composer\autoload_real.php on l
ine 66

18. New deployment in the local environment, manually execute the relevant commands of $PCS_API_CFG_MIGrate == “true”. run successfully. as shown in Figure 18

在本地环境中全新部署，手动执行 $PCS_API_CFG_MIGRATE == "true" 的相关命令。成功运行。

19. Enter the local environment before adding /vendor to the git warehouse. Execute the command: composer install. run successfully. as shown in Figure 19

进入将 /vendor 加入至 Git 仓库前的本地环境。执行命令：composer install。成功运行。

Figure 19

PS E:\wwwroot\pcs-api-feature-plan-tonglian> composer install
Loading composer repositories with package information
Installing dependencies (including require-dev) from lock file
Nothing to install or update
Generating autoload files

20. New deployment in the local environment, execute the command: composer install. failed to run successfully. As shown in Figure 20

Figure 20

PS E:\wwwroot\pcs-api-develop> composer install
Loading composer repositories with package information
Installing dependencies (including require-dev) from lock file
Nothing to install or update
Generating autoload files


  [RuntimeException]
  Could not scan for classes inside "E:\wwwroot\pcs-api-develop\vendor/sebastian/object-enumerator/src/" which does n
  ot appear to be a file nor a folder


install [--prefer-source] [--prefer-dist] [--dry-run] [--dev] [--no-dev] [--no-custom-installers] [--no-autoloader] [--n
o-scripts] [--no-progress] [--no-suggest] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [-a|--classmap-authoritative]
 [--apcu-autoloader] [--ignore-platform-reqs] [--] []...

21. In fact, steps 16 and 17 can be solved by executing the command: composer require codeception/verify mylabs/deep-copy, without having to submit these 2 packages to in git repository. However, even with this scheme, there are still problems with the 20th step. And it will also change other files in /vendor/composer . This scheme is not very desirable. as shown in Figure 21

实际上，第 16、17 步骤，可以通过执行命令：composer require codeception/verify myclabs/deep-copy 来解决，而无需一定要将这 2 个包提交至 Git 仓库中。不过，即使采用此方案，仍然会存在第 20 步骤中所存在的问题。而且还会改变 /vendor/composer 中的其他文件。此方案不太可取。

Figure 21

22. In the final decision, first delete /vendor, submit it to the git repository, and execute the command: composer install –no-dev. –no-dev: Skip the packages listed in the require-dev field. Submit /vendor to the git repository again. Because, it has been determined, –dev: install the package listed in the require-dev field (this is a default). Submit to the Git repository can only submit empty directories. Figure 22

最终决定，先删除掉 /vendor ，提交至 Git 仓库，执行命令：composer install --no-dev。--no-dev：跳过 require-dev 字段中列出的包。再将 /vendor 提交至 Git 仓库。因为，已经确定，--dev：安装 require-dev 字段中列出的包 ( 这是一个默认值 )。提交至 Git 仓库仅能够提交空目录。

Figure 22

23. Execute the command: composer install. Install the packages listed in the require-dev field. Submit /vendor to the git repository again. Figure 23

执行命令：composer install。安装 require-dev 字段中列出的包。再将 /vendor 提交至 Git 仓库。

Figure 23

24. New deployment in the local environment, manually execute the relevant commands of $PCS_API_CFG_MIGrate == “true”. run successfully. Not as expected. Figure 24

在本地环境中全新部署，手动执行 $PCS_API_CFG_MIGRATE == "true" 的相关命令。成功运行。不符合预期。

Figure 24

25. Check the newly deployed files, the directory: \codeception\verify, \vendor\myclabs\deep-copy all exist. as shown in Figure 25

$查看全新部署的文件，目录：\codeception\verify、\vendor\myclabs\deep-copy 皆存在。$

Figure 25

26. Search in the /vendor directory: .git, there is no corresponding directory. And the command is executed before: composer install. failed to run successfully. Search in the /vendor directory: .git, the corresponding directory exists. Figure 26

在 /vendor 目录中搜索：.git，不存在相应的目录。而之前执行命令：composer install。未成功运行。在 /vendor 目录中搜索：.git，存在相应的目录。

Figure 26

27. Edit build/c_files/config/init/console_init.sh. Restore the related commands for $PCS_API_CFG_MIGrate == “true”. Start successfully in Rancher, check the log. Figure 27

编辑 build/c_files/config/init/console_init.sh。恢复 $PCS_API_CFG_MIGRATE == "true" 的相关命令。在 Rancher 中启动成功，查看日志。

Figure 27

28. In another product, search in the /vendor directory: .git, there is a corresponding directory. as shown in Figure 28

Figure 28

29. Failed to start in Rancher, check the log. as shown in Figure 29

Figure 29

2020/5/9 下午7:01:07 PHP Fatal Error 'yii\base\ErrorException' with message 'Class 'wartron\yii2uuid\behaviors\UUIDBehavior' not found'
2020/5/9 下午7:01:07
2020/5/9 下午7:01:07 in /mcloud/www/channel-pub-api/common/behaviors/UUIDBehavior.php:7
2020/5/9 下午7:01:07
2020/5/9 下午7:01:07 Stack trace:
2020/5/9 下午7:01:07 #0 [internal function]: yii\base\ErrorHandler->handleFatalError()
2020/5/9 下午7:01:07 #1 {main}

30. Since there is only one directory: .git, it is decided to adopt the scheme of steps 16 and 17. Start successfully in Rancher, check the log. as shown in Figure 30

由于仅有一个目录：.git，决定采用第 16、17 步骤的方案。在 Rancher 中启动成功，查看日志。

Figure 30

31. The before and after comparison of the construction time in Jenkins are: 13 minutes and 43 seconds respectively. as shown in Figure 31

Figure 31

After adding /vendor to the git repository, docker deploys, the analysis of the upgrade failed

You may also like...

Leave a Reply Cancel reply

After adding /vendor to the git repository, docker deploys, the analysis of the upgrade failed

You may also like...

In Windows 10, a shell script is replaced with an implementation of a php script (execute a php script from another php script)

In Linux, Laravel 6, the task queue is always running for troubleshooting analysis (timeout time has been set)

In Yii 2.0, when the uniqueness verification fails, the prompt is not friendly enough, and the analysis of automatic adjustment and optimization is automatically adjusted.

Leave a Reply Cancel reply