launchpad development|
Size: 1374
Comment:
|
← Revision 8 as of 2020-07-17 16:29:13 ⇥
Size: 223
Comment: Drop obsolete documentation in favour of something more current (if very light and very vague)
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| This page describes how a developer with PQM access can land a change. == Using ec2 == To run the tests on ec2 before submitting to PQM to try and ensure you won't break the build use ''./utilities/ec2''. To use this you must be setup to use [[EC2Test]]. From a local branch of the code that you want to submit (which should have a public branch set (TODO: link to documentation of how to set that stuff up)) simply run ./utilities/ec2 land This finds the merge proposal and infers the target branch, adds the correct reviewer etc. information, and commit message. It relies on having an approved merge proposal with the commit message set. If you want to land someone elses branch on their behalf then you can run, from any LP branch, ./utilities/ec2 land lp:~user/launchpad/branch-name == Using lp-land == If you have the bzr-pqm plugin installed then you can use the "lp-land" command, which works in a similar way to "ec2 land", but doesn't run the testsuite first. First ensure that you have the PQM submission address set for your launchpad branches in ~/.bazaar/locations.conf [/home/user/launchpad/] pqm_email = Canonical PQM <launchpad@pqm.canonical.com> Again, from any copy of a launchpad branch run bzr lp-land and it will infer the details from the approved merge proposal. |
Developers can land changes by flagging the Merge Proposal as "Approved" - assuming a conventionally-configured Launchpad project, this will cause the appropriate bots to merge and test the changes. |
Landing Changes
Developers can land changes by flagging the Merge Proposal as "Approved" - assuming a conventionally-configured Launchpad project, this will cause the appropriate bots to merge and test the changes.
