Skip to content

FOUR-28426: Add custom executor in microservices feature #19549

FOUR-28426: Add custom executor in microservices feature

FOUR-28426: Add custom executor in microservices feature #19549

Triggered via pull request March 11, 2026 15:42
@gusysgusys
synchronize #8651
FOUR-28426
Status Cancelled
Total duration 55s
Artifacts

deploy-pm4.yml

on: pull_request
Run PM4-workflow  /  build-docker-image-EKS
50s
Run PM4-workflow / build-docker-image-EKS
Run PM4-workflow  /  Delete Instance
Run PM4-workflow / Delete Instance
Run PM4-workflow  /  deploy-EKS
0s
Run PM4-workflow / deploy-EKS
Run PM4-workflow  /  run-phpunit
0s
Run PM4-workflow / run-phpunit
Run PM4-workflow  /  Run API Tests
0s
Run PM4-workflow / Run API Tests
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 1 warning
Run PM4-workflow / build-docker-image-EKS
Canceling since a higher priority waiting request for Build PM4-8651- exists
Run PM4-workflow / build-docker-image-EKS
The operation was canceled.
Build PM4
Canceling since a higher priority waiting request for Build PM4-8651- exists
Run PM4-workflow / build-docker-image-EKS
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/