Diff for "LandingChanges"

Not logged in - Log In / Register

Differences between revisions 1 and 2
Revision 1 as of 2010-04-07 09:54:43
Size: 1374
Editor: james-w
Comment:
Revision 2 as of 2010-04-07 09:55:18
Size: 1398
Editor: james-w
Comment:
Deletions are marked like this. Additions are marked like this.
Line 14: Line 14:
{{{
Line 16: Line 16:
}}}
Line 23: Line 23:
{{{
Line 25: Line 25:
}}}
Line 33: Line 33:
{{{
Line 36: Line 36:
}}}
Line 38: Line 38:
{{{
Line 40: Line 40:
}}}

Landing Changes

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.

LandingChanges (last edited 2020-07-17 16:29:13 by doismellburning)