Always Green CI - Owners of CI jobs - Your help is needed #403
Comments
chavafg
added
enhancement
|
Hello @chavafg -, thanks for figure out these. I will take job of maintaining "jenkins-ci-ARM-ubuntu-18-04". |
|
Hi @chavafg, Thank you for the proposal. I want to add that I'm working on making the Can the job be added to the above list? I will take the responsible of maintaining it. However, I would be requiring the necessary permissions(jenkins) for managing the job. Can someone please help me with it? |
You'll be given the permissions / access to the jenkins. |
|
Thanks @fidencio! :) |
|
@chavafg yes, I would like to become first maintainer of jenkins-ci-s390x-ubuntu-20-04 (and maybe more s390x in the future, but let's fully stabilize that first :)). Let me get back to you about backups. |
|
@chavafg please list @stevenhorsman and @davidhay1969 as second & third owners for s390x CI. Unfortunately, we cannot cover other time zones at this time. |
|
@jongwu thanks for confirming. is there someone else that may cover you in case you are on PTO? @Amulyam24 I have added @Jakob-Naucke Thanks for confirming and for providing backups. I have added them in the table above. |
|
@chavafg hello! just a heads-up: @ariel-adam has worked internally to figure out the jobs we gonna maintain. By tomorrow I believe we will have it figured out. |
Just remember that Today & Tomorrow are holidays in Israel. :-) |
hehehe so probably |
happy to take on the FC-related CI tests. I think we should plan for all the supported archs/variants too (IIRC, FC officially supports Intel; AMD support is flaky on some CPU versions and aarch64 is still considered experimental). We'll have a chat about backups and get back to you once I get an update. |
@chavafg -, Yeah, you can add @justin-he as the second maintainer of Arm CI. |
|
@chavafg, please, would be possible to add to the table the CI that CRI-O relies on? That's http://jenkins.katacontainers.io/job/kata-containers-2-crio-PR/ and the maintainers will be @fgiudici and @littlejawa from the Red Hat side, and myself from the Intel side. |
|
If we have a project for "Green CI" already this could be linked to it. |
|
@chavafg Hi, can you please add me as owner of the jobs:
I will maintain them temporary until we will discuss it internally. |
|
@fidencio I have added the cri-o job with the three maintainers. Thanks! @marcel-apf I have also added you as maintainer of the items you described above, let me know if there is a change and I can modify the table. Thanks! @cmaf, thanks for the recommendation, I think it is worth tracking this in a project. |
|
any idea when the jobs that do not have maintainer will be removed from the CI? |
|
@chavafg could you please list me the maintainer of following jobs? kata-containers-2.0-qemu-x86_64 They are used by the other jobs, so they need to be maintained. Any volunteer(s) to co-maintain them with me? |
Good question @GabyCT ! Our Jenkins today have a bunch of what seems garbage. One related topic... after the clean up and if we continue to manage the jobs via the web UI, then I bet we will end up on the same situation (i.e. a bunch of unmaintained jobs) soon. I suggest that we threat the jobs as code by adopting the Jenkins Job Builder (JJB) (unless someone has others suggestions of tools). I provide a proof-of-concept (PoC) in #359, and what I need right now is a go/no-go from the community to continue integrating JJB into our workflow. |
|
As I previously stated, I was the interim maintainer until we will find the right people. |
|
Closing this issue as we already defined owners and baselines |
|
@Jakob-Naucke sorry for my late reply. I added @BbolroC name here and in the Jenkins view. |
As we talked in last AC meeting, we are proposing a number of ideas to improve the results that we currently have in our CI. One of the first items that we would like to have is a list of owners/maintainers that will help us maintain the good state of the jobs reporting to the CI.
In this issue, I want to document the jobs that are currently reporting back to the CI.
Scope:
Jenkins Jobs that are reporting back to GitHub in every PR.
Out of scope:
GitHub actions, Jenkins nightly jobs, jobs that do not report back to GitHub
Job reporting to CRI-O repository:
Jobs that are WIP to be stable that would like to report back to GitHub:
I have added some names in the jobs above, including the ones that Intel would be able to maintain.
@jongwu, @Jakob-Naucke, @ananos, I added your names there as I understand you are currently working in those areas, so please confirm that you can be taken as owners or feel free to change them. It would be great if you could also identify backups for these jobs.
@ariel-adam If you can take a look at the jobs that need owner with your team, it would be great. There are some cri-o, fedora and centos related jobs that I think are important for RedHat.
For anyone else in the community, please consider joining this effort. Feel free to leave a comment below if you would like to be added and I'll update the table. Your help is really appreciated!
To understand which tests are being executed in each of the jobs, I have added the column
Job Type. You can look at the tests that are executed in that job depending on the value of theCI_JOBvariable. Details in therun.shscript.Owners for tests
One of the comments that we received in the AC meeting discussion was that it would also be good to have owners of the tests that are run in the CI. For this, I think we can make use of: Areas of Interest wiki page, where we have documented areas of interest of the different community members. The wiki page needs to be updated, so my other ask to everyone is to open the link and add your names where it make sense. There, we would be able to track who can help if a certain test has become unstable.
/cc @kata-containers/architecture-committee @wainersm @marcel-apf @GabyCT @jcvenegas @egernst @c3d @fidencio
Related:
google doc proposal
The text was updated successfully, but these errors were encountered: