Skip to content

fix(runner): use Jira Cloud auth for mcp-atlassian MCP server #2821

fix(runner): use Jira Cloud auth for mcp-atlassian MCP server

fix(runner): use Jira Cloud auth for mcp-atlassian MCP server #2821

Triggered via pull request March 16, 2026 13:18
Status Success
Total duration 17m 40s
Artifacts 2

components-build-deploy.yml

on: pull_request
detect-changes
5s
detect-changes
Matrix: build-and-push
update-rbac-and-crd
0s
update-rbac-and-crd
deploy-to-openshift
0s
deploy-to-openshift
deploy-with-disptach
deploy-with-disptach
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
detect-changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dorny/paths-filter@v3. 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/
build-and-push (ambient-runner, ./components/runners, quay.io/ambient_code/vteam_claude_runner, ....
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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. 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-push (frontend, ./components/frontend, quay.io/ambient_code/vteam_frontend, ./component...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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. 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
ambient-code~platform~3I00Z6.dockerbuild
85.8 KB
sha256:19a885023f1387e49580be6f2ad0113e93df9d8f279b3c4745a06c721dc64b67
ambient-code~platform~O869PO.dockerbuild
133 KB
sha256:d8de256da47f92bac57e7a3f0da4c664070d44acccce885c14da28dcdf1f8e54