Skip to content

FOUR-18841 Fix process flow is not completed, when we have a subprocess in the middle #1518

FOUR-18841 Fix process flow is not completed, when we have a subprocess in the middle

FOUR-18841 Fix process flow is not completed, when we have a subprocess in the middle #1518

Triggered via pull request August 27, 2024 20:44
Status Success
Total duration 48m 9s
Artifacts 1

deploy-package.yml

on: pull_request
Run Build PM4-workflow  /  build-docker-image-EKS
23m 28s
Run Build PM4-workflow / build-docker-image-EKS
Run Build PM4-workflow  /  Delete Instance
0s
Run Build PM4-workflow / Delete Instance
Run Build PM4-workflow  /  build-deploy-EKS
0s
Run Build PM4-workflow / build-deploy-EKS
Run Build PM4-workflow  /  run-phpunit
24m 16s
Run Build PM4-workflow / run-phpunit
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
Run Build PM4-workflow / build-docker-image-EKS
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/login-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Run Build PM4-workflow / run-phpunit
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Run Build PM4-workflow / run-phpunit
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, docker/login-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Artifacts

Produced during runtime
Name Size
code-coverage Expired
235 KB