NewbieGuide
Size: 246
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: |
… | == 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 7: | Line 10: |
== Important links == | == What is it == |
Line 9: | Line 12: |
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 == |
|
Line 10: | Line 26: |
* Testing results: ci.ubuntu.com/smokeng/utopic/touch/ | * 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") |
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)