HOWTO » History » Version 11
Loïc Dachary, 03/26/2015 09:28 AM
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 | 9 | Loïc Dachary | [[HOWTO update the inventory]] |
6 | 10 | Loïc Dachary | [[HOWTO summarize test results]] |
7 | 11 | Loïc Dachary | [[HOWTO backport commits]] |
8 | 1 | Loïc Dachary | |
9 | 2 | Loïc Dachary | h3. Collect pending pull requests into an integration branch |
10 | 1 | Loïc Dachary | |
11 | The snippet at http://workbench.dachary.org/dachary/ceph-workbench/issues/4 can help |
||
12 | |||
13 | * create a giant-backport branch |
||
14 | * fetch all pull requests from github |
||
15 | * git merge all pull requests |
||
16 | * 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) |
||
17 | * compile with ./autogen.sh ; ./configure ; make -j4 |
||
18 | * modify the pull requests individually to fix compilation errors |
||
19 | 3 | Loïc Dachary | |
20 | h3. Format of teuthology analysis entries |
||
21 | |||
22 | For instance http://tracker.ceph.com/issues/11153#rgw is structured like so: |
||
23 | |||
24 | * In chronological order |
||
25 | * The command line (that can be copy/pasted) used to run the suite |
||
26 | * A bullet point with the URL to the suite run in pulpito prefixed by |
||
27 | ** *running* if the run is not complete |
||
28 | ** *red* if the run has at least one error |
||
29 | ** *green* if the run has no error |
||
30 | 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 |
31 | 6 | Loïc Dachary | * When an error is analyzed, the link to the error is prefixed with |
32 | ** *environmental noise* if it must be run again because it failed for reasons unrelated to the test itself (DNS error etc.) |
||
33 | ** *known bug* and a URL to the bug (not just the number of the bug) |
||
34 | ** *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 |
||
35 | 5 | Loïc Dachary | |
36 | h3. Synchronized repositories |
||
37 | |||
38 | 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: |
||
39 | <pre> |
||
40 | teuthology-suite --suite-branch giant ... --ceph giant ... |
||
41 | </pre> |
||
42 | 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: |
||
43 | <pre> |
||
44 | teuthology-suite --suite-branch wip-rgw-acl-giant ... --ceph giant-backports ... |
||
45 | </pre> |
||
46 | 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. |
||
47 | |||
48 | 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. |