处理在 Jenkins 的 docker 容器内运行的失败测试

如何解决处理在 Jenkins 的 docker 容器内运行的失败测试

同时寻找最佳实践和标准。这是我的工作架构：

这表示我正在从 Jenkins 触发构建，使用 SSH publisher plugin 将工件发布到 AWS EC2，并运行 PyTest 在 docker 容器内进行测试。 ＆ 而已。但是当 PyTest 因任何断言而失败，并且整个操作意外崩溃时，这真的变得非常具有挑战性！

如果所有测试都通过，那么日志：

Step 6/6 : RUN pytest SOWTest/src/test.py --config="$CONFIG"
 ---> Running in 7122a1209546
============================= test session starts ==============================
SOWTest/src/test.py::TestSOWModel::test[2021-05-17 111718-1] PASSED      [ 50%]
SOWTest/src/test.py::TestSOWModel::test[2021-05-17 111718-2] PASSED      [ 50%]

- generated html file: file:///auto-test/SOWTest/resources/reports/Test Report.html -
============================== 2 passed in 0.47s ===============================
Removing intermediate container 7122a1209546
 ---> 1e8e030a30e1
Successfully built 1e8e030a30e1
Successfully tagged sow-auto-test:latest
Copying generated reports outside from the container
Cleaning up
auto -- Deleting Docker Container
auto -- Deleting Docker Image
Untagged: sow-auto-test:latest
Deleted: sha256:1e8e030a----some-kind-of-hash--------------67144af7039986098fd0a
Deleted: sha256:2d18bd6176533d838098a----some-kind-of-hash--------------4bbdad45
SSH: EXEC: completed after 41,028 ms
SSH: Disconnecting configuration [server-dev] ...
SSH: Transferred 28 file(s)
Email was triggered for: Always
Sending email for trigger: Always
Sending email to: [e-mail]
Condition: 'build result equal UNSTABLE' not met. Triggering skipped.
Finished: SUCCESS

另一方面，如果任何测试失败，最终会出现很多错误：

Step 6/6 : RUN pytest SOWTest/src/test.py --config="$CONFIG"
 ---> Running in f5872b03f7e7
============================= test session starts ==============================
SOWTest/src/test.py::TestSOWModel::test[2021-05-11 131500-1] FAILED      [ 50%]
SOWTest/src/test.py::TestSOWModel::test[2021-05-11 131500-2] PASSED      [ 50%]
=================================== FAILURES ===================================
____________________ TestSOWModel.test[2021-05-11 131500-1] ____________________
>           assert expected_response == current_response
SOWTest/src/comparator.py:14: AssertionError

- generated html file: file:///auto-test/SOWTest/resources/reports/Test Report.html -
=========================== short test summary info ============================
FAILED SOWTest/src/test.py::TestSOWModel::test[2021-05-11 131500-1] - Asserti...
========================= 1 failed,1 passed in 0.58s ==========================

The command '/bin/sh -c pytest SOWTest/src/test.py --config="$CONFIG"' returned a non-zero code: 1
Unable to find image 'sow-auto-test:latest' locally
docker: Error response from daemon: pull access denied for sow-auto-test,repository does not exist or may require 'docker login': denied: requested access to the resource is denied.
See 'docker run --help'.
Copying generated reports outside from the container
Error: No such container:path: auto:/auto-test/SOWTest/resources/reports/Test Report.html
Cleaning up
Error response from daemon: No such container: auto
Error: No such container: auto
Error: No such image: sow-auto-test
SSH: EXEC: completed after 12,016 ms
SSH: Disconnecting configuration [server-dev] ...
ERROR: Exception when publishing,exception message [Exec exit status not zero. Status [1]]
Build step 'Send build artifacts over SSH' changed build result to UNSTABLE
Email was triggered for: Always
Sending email for trigger: Always
Sending email to: [e-mail]

然而，我在测试完成后删除了 docker 容器和图像，但如果测试失败，我最终会在 AWS EC2 上看到很多死容器。意味着我的清理命令也没有像我们在日志中看到的那样工作。这是从 Jenkins SSH Publisher 的 Exec 命令 运行的构建脚本：

sudo docker build --build-arg CONFIG=$1 -t $IMAGE -f SOWTest/docker/docker .
sudo docker run -d -t --name $CONTAINER $IMAGE

echo "Copying generated reports outside from the container"
sudo rm -rf reports
sudo mkdir reports
sudo docker cp "${CONTAINER}:${REPORT}" reports/

echo "Cleaning up"
sudo docker stop $CONTAINER
sudo docker rm $CONTAINER
sudo docker rmi $IMAGE

根据我的理解，以非零值退出，是操作失败的原因，我也理解在测试失败的情况下预期非零！那么，我们如何才能提出解决方案，同时避免这些 docker 错误？