Document Kernel CI Terms of Services
Define Terms of Services for CI Kernel Service:
+ Bug Process: where and how to file bugs? What info to attach to bugs? How to escalate urgent bugs? Point of Contact?
+ Subscription Process: where and how to get a kernel tree and defconfig added to our kernel CI service; what info to provide? (guess name, schedule, git tree url, branch name, defconfig, other envs/parameters needed by our job)
-> here this blueprint should come up with a blueprint template hat will be used to schedule a blueprint to setup new trees/defconfigs etc.; important to not (only) use bugs for that because bugs are typically not automatically screened for headlines and addition of additional trees/defconfig
Blueprint information
- Status:
- Complete
- Approver:
- David Zinman
- Priority:
- Medium
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- Deepti B. Kalakeri
- Definition:
- Approved
- Series goal:
- Accepted for engineering
- Implementation:
-
Implemented
- Milestone target:
-
11.12
- Started by
- Deepti B. Kalakeri
- Completed by
- David Zinman
Related branches
Related bugs
Sprints
Whiteboard
[ deepti Dec 13, 2011] All the below information is added into the wiki @ https:/
[danilos Dec 15, 2011] (05:23:09 IST) danilos: comments for the quick ref
(05:23:33 IST) danilos: you should probably include the <email address hidden> in the PoC as well (or at least link to the infra wiki/LP page)
(05:23:59 IST) danilos: also, it would be great if that was linked from ci.linaro.org somewhere, hopefully jenkins allows that
(05:24:22 IST) danilos: and finally, I think you should mention that once a job is set-up, it is requestor's responsibility to watch it for failures!
[deepti Dec 21, 2011] Added the link to quick reference under each view on ci.linaro.org
[deepti Dec 21, 2011] Added the email id of infrastructure team under the Point of Contact section.
[deepti Dec 21, 2011] Addressed the other review comments and a NOTE on who needs to monitor is added under the https:/
Meta:
Headline: Setting the Terms of Services for CI Kernel Service.
Acceptance: The Terms of Services for CI Kernel Service are established and approved by the TL/PM. Anyone who needs to make use of the CI service should find all the required information for creating a new job at one place.
Work Items
Work items:
1) Identify the primary Point of Contact for the CI related information. Document the same on a wiki: DONE
2) Establish the Bug process to include information like Where and how to file a bug. Document the same on a wiki: DONE
3) Establish the Bug process to include information like What info to attach to bugs for creation of new job. Document the same on a wiki: DONE
4) Establish the Bug process to include information like How to escalate urgent bugs . Document the same on a wiki: DONE
5) Establish the Bug process to include information like Where and how to file a bug. Document the same on a wiki: DONE
6) Add information on the BP template that one needs to create for setting up new builds for trees/defconfigs: DONE
7) Review the documentation of the BP: DONE
8) set BP state to implemented/
