ci: k8s workers
Test the k8s workers
WIP
There are test failures while running in Pod workers:
Stats
I'm still gathering details regarding the build times improvements, but this build started at 17:20:15 and reached the Coverage stage at 2022-02-11T17:48:03.714Z (see here)
Therefore it took ~ 28 mints while this build with the k8s pods took 20 mints -> ~28% much faster!
We are evaluating the k8s plugin in terms of the complexity versus fast feedback in addition if it scales without affecting the CI controller.
:broken_heart: Build 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-09-07T17:20:33.717+0000
-
Duration: 26 min 47 sec
Test stats :test_tube:
| Test | Results |
|---|---|
| Failed | 0 |
| Passed | 2901 |
| Skipped | 90 |
| Total | 2991 |
Steps errors 
Expand to view the steps failures
Build
- Took 10 min 22 sec . View more details here
- Description:
./scripts/jenkins/build.sh
Build
- Took 2 min 15 sec . View more details here
- Description:
./scripts/jenkins/build.sh
Build
- Took 2 min 7 sec . View more details here
- Description:
./scripts/jenkins/build.sh
Build
- Took 10 min 14 sec . View more details here
- Description:
./scripts/jenkins/build.sh
Build
- Took 2 min 15 sec . View more details here
- Description:
./scripts/jenkins/build.sh
Build
- Took 2 min 8 sec . View more details here
- Description:
./scripts/jenkins/build.sh
:robot: GitHub comments
To re-run your PR in the CI, just comment with:
-
/test: Re-trigger the build. -
run benchmark tests: Run the benchmark test. -
runelasticsearch-ci/docs: Re-trigger the docs validation. (use unformatted text in the comment!)
to support Docker in Docker https://github.com/elastic/apm-pipeline-library/pull/1484/files#diff-ef8b2f5e4d21d81c0eba4754dea3a3dfc2c67d26284f195165b650cf4aff7beaR104-R141
@v1v @kuisathaverat can this be closed or is it still used for further testing?
We will use a different approach, rather than using the K8s for the CI, we will use K8s for the developers and the CI will be one of the consumers.
For such, we are still working on preparing the K8s ecosystem and run some PoC.
I'll close this now as we will implement something different. Thanks