ci: transform branch to allow the Google Labels naming

[v1v]

What does this PR do?

Rename special chars

Why is it important?

Avoid issues with some special chars if the provider is Google

Issue

See elastic/elastic-package#799

[elasticmachine]

💔 Tests Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-04-25T15:22:10.416+0000

• Duration: 84 min 38 sec

Test stats 🧪

Test	Results
Failed	7
Passed	308
Skipped	0
Total	315

Test errors

Expand to view the tests failures

Initializing / End-To-End Tests / fleet_debian_amd64_system_integration / Adding cpu system/metrics Integration to a Policy – System Integration

Expand to view the error details

 Step "system/metrics" with "cpu" metrics are present in the datastreams 

• no stacktrace

Initializing / End-To-End Tests / fleet_debian_arm64_system_integration / Adding core system/metrics Integration to a Policy – System Integration

Expand to view the error details

 Step "system/metrics" with "core" metrics are present in the datastreams 

• no stacktrace

Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Logs collection from running pod – elastic-agent standalone

Expand to view the error details

 Step "elastic-agent" collects events with "kubernetes.pod.name:a-pod": context deadline exceeded 

• no stacktrace

Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Logs collection from a pod with an init container – elastic-agent standalone

Expand to view the error details

 Step "elastic-agent" collects events with "kubernetes.container.name:container-in-pod" 

• no stacktrace

Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Logs collection from short-living cronjobs – elastic-agent standalone

Expand to view the error details

 Step "elastic-agent" collects events with "kubernetes.container.name:cronjob-container": context deadline exceeded 

• no stacktrace

Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Logs collection from failing pod – elastic-agent standalone

Expand to view the error details

 Step "elastic-agent" collects events with "kubernetes.pod.name:a-failing-pod": context deadline exceeded 

• no stacktrace

Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Metrics collection configured from targeted Redis Pod – elastic-agent standalone

Expand to view the error details

 Step "elastic-agent" collects events with "kubernetes.pod.name:redis": context deadline exceeded 

• no stacktrace

Steps errors

Expand to view the steps failures

Shell Script

• Took 21 min 58 sec . View more details here
• Description: ssh -tt -o TCPKeepAlive=yes -o ServerAliveInterval=60 -o ServerAliveCountMax=10 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i /var/lib/jenkins/workspace/PR-2419-1-b252e0bc-3079-4adc-ad43-f095fee52a8b/e2essh [email protected] -- 'sudo bash /home/admin/e2e-testing/.ci/scripts/functional-test.sh "system_integration && ~@nightly" '

Archive the artifacts

• Took 0 min 1 sec . View more details here
• Description: [2022-04-25T16:20:19.208Z] Archiving artifacts script returned exit code 2

Shell Script

• Took 17 min 41 sec . View more details here
• Description: ssh -tt -o TCPKeepAlive=yes -o ServerAliveInterval=60 -o ServerAliveCountMax=10 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i /var/lib/jenkins/workspace/PR-2419-1-27a62407-b5ae-464e-8a67-95076c669c1f/e2essh [email protected] -- 'sudo bash /home/admin/e2e-testing/.ci/scripts/functional-test.sh "system_integration && ~@nightly" '

Archive the artifacts

• Took 0 min 1 sec . View more details here
• Description: [2022-04-25T16:16:56.919Z] Archiving artifacts script returned exit code 2

Shell Script

• Took 45 min 8 sec . View more details here
• Description: ssh -tt -o TCPKeepAlive=yes -o ServerAliveInterval=60 -o ServerAliveCountMax=10 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i /var/lib/jenkins/workspace/PR-2419-1-b88b1e34-4e57-472b-9076-684191752b66/e2essh [email protected] -- 'sudo bash /home/admin/e2e-testing/.ci/scripts/functional-test.sh "elastic-agent && ~@nightly" '

Archive the artifacts

• Took 0 min 1 sec . View more details here
• Description: [2022-04-25T16:45:35.912Z] Archiving artifacts script returned exit code 2

🐛 Flaky test report

❕ There are test failures but not known flaky tests.

Expand to view the summary

Genuine test errors

💔 There are test failures but not known flaky tests, most likely a genuine test failure.

• Name: Initializing / End-To-End Tests / fleet_debian_amd64_system_integration / Adding cpu system/metrics Integration to a Policy – System Integration
• Name: Initializing / End-To-End Tests / fleet_debian_arm64_system_integration / Adding core system/metrics Integration to a Policy – System Integration
• Name: Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Logs collection from running pod – elastic-agent standalone
• Name: Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Logs collection from a pod with an init container – elastic-agent standalone
• Name: Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Logs collection from short-living cronjobs – elastic-agent standalone
• Name: Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Logs collection from failing pod – elastic-agent standalone
• Name: Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Metrics collection configured from targeted Redis Pod – elastic-agent standalone

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.