Skip to content
Integration test

define different deploy strategy for jobservice #1323

Sign in to view logs

define different deploy strategy for jobservice

define different deploy strategy for jobservice #1323

Re-run triggered January 3, 2024 14:26
@Vad1moVad1mo
#1659
gminiba:main
Status Success
Total duration 5m 24s
Artifacts –

integration.yaml

on: pull_request
Matrix: integration-test
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
integration-test (v1.23.13)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, helm/[email protected], actions/setup-go@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
integration-test (v1.24.7)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, helm/[email protected], actions/setup-go@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
integration-test (v1.25.3)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, helm/[email protected], actions/setup-go@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/