HOWTO » History » Version 7
Yuri Weinstein, 03/23/2015 04:26 PM
1 | 2 | Loïc Dachary | h3. HOWTO backport |
---|---|---|---|
2 | 1 | Loïc Dachary | |
3 | Based on what would be done for the Giant branch |
||
4 | |||
5 | h3. Update the inventory |
||
6 | |||
7 | * ssh -p2222 backports@workbench.dachary.org |
||
8 | * screen -x |
||
9 | * ( cd .. ; github2gitlab --github-token $github_token --github-repo ceph/ceph --gitlab-url http://workbench.dachary.org --gitlab-token $gitlab_token --gitlab-repo ceph/ceph-backports --branches master,dumpling,emperor,firefly,giant,hammer,firefly-backports,giant-backports,dumpling-backports --verbose ) |
||
10 | * ( python ../sanity.py ; cd ../ceph-backports.wiki ; git commit -a -m 'update' ; git push ) |
||
11 | * firefox http://workbench.dachary.org/ceph/ceph-backports/wikis/giant |
||
12 | |||
13 | 7 | Yuri Weinstein | h3. Major release (e.g. hammer) QA suites results, open issues summarization process |
14 | |||
15 | * all planned features were committed to the branch |
||
16 | * ceph QA suites are being executed by "nightlies" (crontab teuthology@theuthology in Sepia lab) |
||
17 | * a new section is added to the http://tracker.ceph.com/rb/master_backlog/ceph-releases# , as for example for "hammer v0.94.1" with version number |
||
18 | * all suites listed as tasks and results summaries + related tickets are listed there |
||
19 | * as suite passed, and all issues resolved, the task is marked a resolved and thus indicates readiness for the final release cut |
||
20 | |||
21 | 1 | Loïc Dachary | h3. Backport issues |
22 | |||
23 | The helper snippet at http://workbench.dachary.org/dachary/ceph-workbench/issues/3 can be used to semi automate the process below |
||
24 | |||
25 | * For each entry at http://workbench.dachary.org/ceph/ceph-backports/wikis/giant#issues-that-need-backporting |
||
26 | * git cherry-pick -x the commits from the pull request that was targettig master (not from the pull requests targeting stable branches) |
||
27 | * create a pull request with the backport with a reference to the issue and set the milestone to giant |
||
28 | * add a reference to the pull request in the issue |
||
29 | * if the make check bot finds a problem, fix it |
||
30 | |||
31 | 2 | Loïc Dachary | h3. Collect pending pull requests into an integration branch |
32 | 1 | Loïc Dachary | |
33 | The snippet at http://workbench.dachary.org/dachary/ceph-workbench/issues/4 can help |
||
34 | |||
35 | * create a giant-backport branch |
||
36 | * fetch all pull requests from github |
||
37 | * git merge all pull requests |
||
38 | * modify the pull requests individually to fix merge conflicts (i.e. they must merge cleanly, which may involving aggregating two pull requests into a single one designed to properly resolve the conflict) |
||
39 | * compile with ./autogen.sh ; ./configure ; make -j4 |
||
40 | * modify the pull requests individually to fix compilation errors |
||
41 | 3 | Loïc Dachary | |
42 | h3. Format of teuthology analysis entries |
||
43 | |||
44 | For instance http://tracker.ceph.com/issues/11153#rgw is structured like so: |
||
45 | |||
46 | * In chronological order |
||
47 | * The command line (that can be copy/pasted) used to run the suite |
||
48 | * A bullet point with the URL to the suite run in pulpito prefixed by |
||
49 | ** *running* if the run is not complete |
||
50 | ** *red* if the run has at least one error |
||
51 | ** *green* if the run has no error |
||
52 | 4 | Loïc Dachary | * If the run has at least one error, the output of the fail formatter snippet (found at http://workbench.dachary.org/dachary/ceph-workbench/issues/2 is appened to it) is added and edited when the errors are analyzed |
53 | 6 | Loïc Dachary | * When an error is analyzed, the link to the error is prefixed with |
54 | ** *environmental noise* if it must be run again because it failed for reasons unrelated to the test itself (DNS error etc.) |
||
55 | ** *known bug* and a URL to the bug (not just the number of the bug) |
||
56 | ** *new bug* and a URL to the newly created bug if it was discovered during the analysis of this error: it is likely to be a regression |
||
57 | 5 | Loïc Dachary | |
58 | h3. Synchronized repositories |
||
59 | |||
60 | When running teuthology tests for a given branch (say giant), the "ceph-qa-suite":https://github.com/ceph/ceph-qa-suite branch must match. In the simplest case it is enough to write: |
||
61 | <pre> |
||
62 | teuthology-suite --suite-branch giant ... --ceph giant ... |
||
63 | </pre> |
||
64 | When a Ceph pull request (for instance "rgw acl response should start with <?xml version=1.0 ?>":https://github.com/ceph/ceph/pull/4082) needs to be synchronized with a ceph-qa-suite pull request (for instance "create a new get_acl helper to ensure proper xml is compared":https://github.com/ceph/ceph-qa-suite/pull/370), dedicated branches must be created in the Ceph and ceph-qa-suite repositories. For instance: |
||
65 | <pre> |
||
66 | teuthology-suite --suite-branch wip-rgw-acl-giant ... --ceph giant-backports ... |
||
67 | </pre> |
||
68 | Note that it is not possible to specify a branch that is outside of the Ceph or ceph-qa-suite repositories: write access to these repositories is necessary. |
||
69 | |||
70 | For S3 tests an additional repository must be synchronized in a similar way https://github.com/ceph/s3-tests: there must exist a branch with the same name as the branch specified with **--suite-branch**. For instance the "ceph-qa-suite wip-rgw-acl-giant":https://github.com/ceph/ceph-qa-suite/tree/wip-rgw-acl-giant branch must have a "s3-test wip-rgw-acl-giant":https://github.com/ceph/s3-tests/tree/wip-rgw-acl-giant counterpart. |