Skip to content

Adding tests for deploying multiple vCluster in single namespace #63

Adding tests for deploying multiple vCluster in single namespace

Adding tests for deploying multiple vCluster in single namespace #63

Triggered via pull request August 27, 2024 19:53
Status Cancelled
Total duration 2m 42s
Artifacts 3

e2e-deploy-changes.yaml

on: pull_request
build-and-push-syncer-image
1m 2s
build-and-push-syncer-image
build-vcluster-cli
54s
build-vcluster-cli
Build tests binaries
2m 19s
Build tests binaries
generate-matrix
9s
generate-matrix
Matrix: execute-deploy-tests
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 2 warnings
execute-deploy-tests (./deploy_changes/deploy_changes_networking/)
Canceling since a higher priority waiting request for 'E2E Deploy Changes CI-2097' exists
execute-deploy-tests (./deploy_changes/deploy_changes_sync/)
Canceling since a higher priority waiting request for 'E2E Deploy Changes CI-2097' exists
build-and-push-syncer-image
You are using 'latest' as default version. Will lock to '~> v2'.
Build tests binaries
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Artifacts

Produced during runtime
Name Size
test-binaries Expired
95.6 MB
vcluster Expired
19.5 MB
vcluster_syncer Expired
52.6 MB