NewbieGuide
Differences between revisions 4 and 21 (spanning 17 versions)
|
Size: 1863
Comment:
|
Size: 1636
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| So you want to ride the CI train? Great, here is what you need to know: | What you need to know if you are new to the citrain landing team: |
| Line 5: | Line 5: |
| == Introduction == * Its all in one google spreedsheet that mostly updates itself automatically (its a frontend to jenkins) * First column in the spreedsheet is important! Keep attention to the number of free silos, try to keep slios free * The spreedsheet has multiple page, the main one is "pending", but there is a important one "Archive" that contains *all* of the history * Merge propoosal to land (row F) is important, order is important too but its not limited to a single project * Additional source packages to land: you need to dput these additional source packages from the archive into the silo PPA * QA sign off needed: only in effect if we are in train-con-zero - and then *only* stuff with QA-sign-off: no can enter the image * Ready? : really important, once its ready, assign to a silo |
== What do do == * join #ubuntu-ci-eng and highlight on "trainguards" * wait for stuff to be ready for publishing (the bot will tell you about it) and perform the "steps for publishing" below * the expectation is to do up to 50% of your work time on landings |
| Line 14: | Line 10: |
| == Terms == * Silo are PPAs that are used to prepare a landing * Landers are trusted people of the upstream project who can drive landing and do the final testing * TrainCon-Zero: when no new image is generated for 7 buisiness days this "emergency" state is reached and only critical fixes can go in |
== What is it == |
| Line 19: | Line 12: |
| == Important links == | The citrain is a tool to coordinate landing of new features. This includes building/testing and publishing. |
| Line 21: | Line 14: |
| * Main landing spreadsheet: https://wiki.ubuntu.com/citrain (refreshes every 5min) * Jenkins that is controlled via the spreedsheet: https://ci-train.ubuntu.com/ * Code for the spreedsheet: lp:cupstream2distro |
== Steps for publishing == * when a landing is built queuebot will say so in the #ubuntu-ci-eng channel * click the link queuebot pings * click on "publish" on the request, that links to a jenkins page * '''WARNING''' publish means to publish into the REAL archive - do not publish '''NEW''' packages without consulting archive admins * click on "build" on the jenkins form * if there are packaging changes the circle on the left will turn red and you need to review the build artifact with the packaging diff (e.g. nuntium_packaging_changes.diff), then click on "Build with Parameters" on the left and select ACK_PACKAGING * the status should be "blue" (successful), you can close the jenkins tab now == Links == * Main landing spreadsheet: https://wiki.ubuntu.com/citrain |
| Line 25: | Line 27: |
| * Who is who: https://wiki.ubuntu.com/citrain/LandingTeam * The Daily release FAQ is valid under citrain: https://wiki.ubuntu.com/DailyRelease/FAQ (apart from "When do changes need to land in a coherent piece?" and "I want one of my commit not being part of debian/changelog") |
|
| Line 26: | Line 31: |
| == Tutorial == * landing for autopilot: * check if it has a testplan * check that its ready * go to the "Landing team tools" menubar and click on "assign silo" * this generates a request-id that is valid for 5min * opens a dialog that you need to check * the jenkins tab opens, click on "proceed" |
Newbie guide
What you need to know if you are new to the citrain landing team:
What do do
- join #ubuntu-ci-eng and highlight on "trainguards"
- wait for stuff to be ready for publishing (the bot will tell you about it) and perform the "steps for publishing" below
- the expectation is to do up to 50% of your work time on landings
What is it
The citrain is a tool to coordinate landing of new features. This includes building/testing and publishing.
Steps for publishing
- when a landing is built queuebot will say so in the #ubuntu-ci-eng channel
- click the link queuebot pings
- click on "publish" on the request, that links to a jenkins page
WARNING publish means to publish into the REAL archive - do not publish NEW packages without consulting archive admins
- click on "build" on the jenkins form
- if there are packaging changes the circle on the left will turn red and you need to review the build artifact with the packaging diff (e.g. nuntium_packaging_changes.diff), then click on "Build with Parameters" on the left and select ACK_PACKAGING
- the status should be "blue" (successful), you can close the jenkins tab now
Links
Main landing spreadsheet: https://wiki.ubuntu.com/citrain
Testing results: http://ci.ubuntu.com/smokeng/utopic/touch/
Who is who: https://wiki.ubuntu.com/citrain/LandingTeam
The Daily release FAQ is valid under citrain: https://wiki.ubuntu.com/DailyRelease/FAQ (apart from "When do changes need to land in a coherent piece?" and "I want one of my commit not being part of debian/changelog")
citrain/NewbieGuide (last edited 2015-09-02 04:12:32 by 1)