Skip to content

Launchpad Setup History

Art edited this page Dec 12, 2016 · 5 revisions

Here we give a historical trace of how the NixNote project was set up in Launchpad to deliver automated builds for Ubuntu and its derivatives.

Before you start

These instructions assume you have already

Create basic Launchpad entities

Note: Many of the "Create Xxxxx" options in Launchpad use generic URLs, rather than sub-URLs of any user / site / repo you may already be browsed to.

Team

PPA

Under the team...

Project

Set up Code Branches under Project

head (or trunk)

Target version control system

Since October 2016, Launchpad supports importing git code directly into Git mirrors, rather than converting them into Bzr. Aside from other advantages, this mitigates the issue importing gpgsig commits.

When setting up new imports of code projects from Git, you should now check the option

Target version control system = Git

When importing the main code repo use Configure Code...

* https://code.launchpad.net/nixnote2/+configure-code
* Git Settings / Import a Git repository hosted somewhere else

And for all others just add a new import

* https://code.launchpad.net/nixnote2/+new-import

See Launchpad Git Mirroring documentation for more information.

Converting Bzr imports to Git Mirrors
  • See Converting from Bazaar to Git.
  • Don't forget to clean your bzr import settings from old setup or you couldn't set a recipe for git code even if it's there.

See also:

Branch

Set up Code Branches under packaging

create Recipe

After a few minutes, check the import logs

After an hour or so (?), check the build logs