Skip to content

[9.0] Include DiracX token in proxy PEM files #10613

[9.0] Include DiracX token in proxy PEM files

[9.0] Include DiracX token in proxy PEM files #10613

Triggered via pull request November 27, 2023 13:05
Status Success
Total duration 22m 15s
Artifacts

integration.yml

on: pull_request
Matrix: Integration
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Integration (Force DEncode, DIRAC_USE_JSON_ENCODE=NO)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@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 (MariaDB 10.6, elasticsearch:7.9.1, MYSQL_VER=mariadb:10.6.3 ES_VER=elasticsearch:7.9.1)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@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 (Backward Compatibility, CLIENT_INSTALLATION_BRANCH=rel-v8r0)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@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 (DIPS, TEST_HTTPS=No)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/