deleted: the suspect_managedcode_host_process and rootkit_files_detec… #483
JocLRojasv11-deployment-pipeline.yml
on: push
Setup Deployment
3s
Build Backend Microservice
/
Build & Push Java 17 Image
2m 34s
Build Frontend Microservice
/
build
4m 43s
Build User-Auditor Microservice
/
Build & Push Java 11 Image
1m 53s
Build Web-PDF Microservice
/
Build & Push Java 11 Image
3m 4s
Sign Windows Agent Binaries
/
Sign windows binaries
1m 19s
Sign macOS Agent Binaries
/
Sign macos binaries
1m 17s
Deploy Installer (Dev)
/
Deploy V10 to Dev Runner
0s
Deploy Installer (Dev)
/
Deploy V10 to RC Runner
0s
Deploy Installer (Dev)
/
Upload V10 Installer to Prerelease
0s
Deploy Installer (Dev)
/
Deploy V11 to Dev Runner
7s
Deploy Installer (Dev)
/
Build V11 Installer for Prerelease
0s
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
4s
Annotations
14 warnings
|
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 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 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, 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 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 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 Binaries
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 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/
|
|
Sign macOS Agent Binaries / Sign macos binaries
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@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/
|
|
Sign Windows Agent Binaries / Sign windows binaries
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, actions/setup-java@v4, actions/upload-artifact@v4, google-github-actions/auth@v2, google-github-actions/setup-gcloud@v2. 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 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/
|
|
Deploy Installer (Dev) / Deploy V11 to Dev Runner
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 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/
|
|
Deploy Installer (Dev) / Deploy V11 to Dev Runner
Restore cache failed: Dependencies file is not found in /home/utmstack/actions-runner/_work/UTMStack/UTMStack. Supported file pattern: go.sum
|
|
Publish New Version to Customer Manager
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. 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 | |
|---|---|---|---|
|
agents-darwin-signed
Expired
|
39 MB |
sha256:989c4ad6ce8e9a92d7f69529e3dfa20fb176e1295851c339ac99485ad0722bcc
|
|
|
agents-darwin-unsigned
Expired
|
39 MB |
sha256:ce064f94684dbee0b26a098abf7c4025584365ba39b3967aaa00cdec18eeff6a
|
|
|
agents-linux
Expired
|
76.9 MB |
sha256:485c0a4e59343000ebf7b31e826ba240fffc8f90672406a70d652099a60a0a17
|
|
|
agents-windows-signed
Expired
|
67.4 MB |
sha256:533d4c307d1738d38d948e97e2b498b901751aae8d0519cb217b1f635ed533c4
|
|
|
agents-windows-unsigned
Expired
|
67.4 MB |
sha256:424465eb9e6c185d60d062e3a22fd50f654d2048db3a532cec3c4d0de64ddf4d
|
|
|
utmstack-collectors
Expired
|
62.7 MB |
sha256:6cd99528e8f45d07f0a5d079ac3efd35a60433d92680ccaae1849781a4ca7315
|
|
|
utmstack~UTMStack~425NJY.dockerbuild
Expired
|
26.9 KB |
sha256:8b1ca0d7f4b2c73a65facda26e1a7e34a3cc707d82f78dcd08f193cad84457ef
|
|
|
utmstack~UTMStack~G3YCDZ.dockerbuild
Expired
|
40.8 KB |
sha256:dee6da348a5b4be95307fbb6cf371ccd0f4f5d874b01bfee8573af0400feb1ff
|
|
|
utmstack~UTMStack~I84JT3.dockerbuild
Expired
|
14.6 KB |
sha256:dd2020c7d48abeb2b663b5bac4c42a41c96f15dd5e93c027e690fdcf4785c042
|
|
|
utmstack~UTMStack~K39MQS.dockerbuild
Expired
|
14.2 KB |
sha256:268a4ff05762df6b1b104125645bed65b61bcc8b62b7d6c9c848ee4fdcfb6886
|
|
|
utmstack~UTMStack~KS1TWJ.dockerbuild
Expired
|
35.9 KB |
sha256:9dfec18f296924fdacbf53f03976a4af8fb2bc0aab5c8834abb88ae796f26f0c
|
|
|
utmstack~UTMStack~LNPU7K.dockerbuild
Expired
|
21.6 KB |
sha256:d4fdd9b0fed28b4319e875052bf672a5c3da2a055d3741ae9825d019a4d246e7
|
|