v11 - Build & Deploy Pipeline #409
Kbayerov11-deployment-pipeline.yml
on: release
Setup Deployment
3s
Build and Sign Agent
1m 55s
Build and Sign Agent (macOS)
2m 2s
Build UTMStack Collector
2m 3s
Build Backend Microservice
/
Build & Push Java 17 Image
1m 7s
Build Frontend Microservice
/
build
4m 26s
Build User-Auditor Microservice
/
Build & Push Java 11 Image
2m 22s
Build Web-PDF Microservice
/
Build & Push Java 11 Image
2m 8s
Deploy Installer (Dev)
/
Build V11 Installer for Prerelease
Deploy Installer (Dev)
/
Deploy V10 to Dev Runner
Deploy Installer (Dev)
/
Deploy V10 to RC Runner
Deploy Installer (Dev)
/
Deploy V11 to Dev Runner
Deploy Installer (Dev)
/
Upload V10 Installer to Prerelease
Build & Upload Installer (RC)
/
Build V11 Installer for Prerelease
Build & Upload Installer (RC)
/
Deploy V10 to Dev Runner
Build & Upload Installer (RC)
/
Deploy V10 to RC Runner
Build & Upload Installer (RC)
/
Deploy V11 to Dev Runner
Build & Upload Installer (RC)
/
Upload V10 Installer to Prerelease
Schedule release to our instances
0s
Annotations
1 error and 10 warnings
|
Build Backend Microservice / Build & Push Java 17 Image
Process completed with exit code 1.
|
|
Build Backend Microservice / Build & Push Java 17 Image
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/setup-java@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
Build and Sign Agent (macOS)
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/setup-go@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
Build and Sign Agent (macOS)
Restore cache failed: Dependencies file is not found in /Users/runner/work/UTMStack/UTMStack. Supported file pattern: go.sum
|
|
Build UTMStack Collector
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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
Build Web-PDF Microservice / Build & Push Java 11 Image
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/setup-java@v4, docker/build-push-action@v6, docker/login-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
Build User-Auditor Microservice / Build & Push Java 11 Image
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/setup-java@v4, docker/build-push-action@v6, docker/login-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
Build Event Processor Microservice
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/login-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
Default value for global ARG results in an empty or invalid base image name:
event_processor.Dockerfile#L3
InvalidDefaultArgInFrom: Default value for ARG ${BASE_IMAGE} results in empty or invalid base image name
More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
|
|
Build Agent Manager Microservice
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/download-artifact@v4, docker/build-push-action@v6, docker/login-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
Build Frontend Microservice / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
signed-agents
Expired
|
144 MB |
sha256:a706577302906d7f4ebd63705a65c89f95d06a805cdbec2af7dff4d0c713060b
|
|
|
signed-agents-darwin
Expired
|
39 MB |
sha256:a008299428f98be7903e9099ccf9d3cabe5753237cc4f70517173ba579d8e2c7
|
|
|
utmstack-collectors
Expired
|
62.7 MB |
sha256:8048f4ca0e5e9ee3138564bb8afb69fcf3a42732ff9feff8fa0dd2eb126d2cab
|
|
|
utmstack~UTMStack~3FXAI3.dockerbuild
|
26.9 KB |
sha256:e98100b888a303cb6ad8d3a255ed89e4cafeab9e35fe88ffb6593bd7ccdfda58
|
|
|
utmstack~UTMStack~5J55NO.dockerbuild
|
41.7 KB |
sha256:51c455a855d07c3e19c1b452fc4f1e1126fbf366b0b661378db1cdfb9b391c4c
|
|
|
utmstack~UTMStack~AKI236.dockerbuild
|
13.9 KB |
sha256:8dec9570fef18650391f3b8641110312541340f02214f6b3a4aaee9761c3f06a
|
|
|
utmstack~UTMStack~F7JW08.dockerbuild
|
21.9 KB |
sha256:cf0c577f0e103d9313dbad7c1e258c06d53c3f58bff91ac1dfad02502d4518f9
|
|
|
utmstack~UTMStack~W6K30L.dockerbuild
|
35.6 KB |
sha256:f2f1dc5c9b779c2d8e273f59e1f0291dd5493ce16b5eea50d9a49b3ef1e52032
|
|