Skip to content

SITES-15109 - RFH - Applying Async in clientlibraries not working on customer instance #3056

SITES-15109 - RFH - Applying Async in clientlibraries not working on customer instance

SITES-15109 - RFH - Applying Async in clientlibraries not working on customer instance #3056

Triggered via pull request August 16, 2023 15:08
Status Success
Total duration 6m 52s
Artifacts

maven-test.yml

on: pull_request
Matrix: build-js
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
build (ubuntu-latest, 8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1, 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/
build (ubuntu-latest, 8, -Pcloud,adobe-public)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1, 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/
build (ubuntu-latest, 11)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1, 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/
build (ubuntu-latest, 11, -Pcloud,adobe-public)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1, 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/