Diff for "Packaging/SourceBuilds"

Not logged in - Log In / Register

Differences between revisions 10 and 11
Revision 10 as of 2011-03-24 11:23:49
Size: 3083
Editor: host217-44-165-42
Comment:
Revision 11 as of 2011-03-24 11:30:57
Size: 3083
Editor: host217-44-165-42
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
<<Include(Packaging/SourceBuilds/Header)>>
Line 4: Line 6:

<<Include(Packaging/SourceBuilds/Header)>>

Launchpad Help > Packaging > Daily builds

lp-diamond-16.png Source package recipes in Launchpad

Home

Getting Started

Knowledge Base

List of Daily Builds

Daily builds

Daily builds are a great way of trying out the latest code from a project, with relatively little effort.

Whether you want to help others test your code, or you want to run a modified or bleeding edge version of your favourite software, Launchpad's daily builds lets you:

  • take the code in one or more Bazaar branches
  • borrow the packaging information from the software's existing Ubuntu package
  • sit back and get an automatic build one every day the source changes, which is then published in the PPA of your choice.

So you can run the latest code, with or without your chosen modifications, without having to install from source. Plus, you get automatic Ubuntu update reminders whenever the package changes.

Why daily builds?

If you're running a software project, the main advantage of daily builds is that it helps with testing. In particular, it can help:

  • Tighten the feedback loop: making new code available almost straight away, in a way that's easy to install, brings developers and testers closer together

  • Lowers the barrier to becoming a tester: adding a PPA is an easy and common task for Ubuntu users, meaning that anyone can help test your software

  • Easier verification testing: people who've reported a bug can quickly and simply check that the bug is fixed in a future revision.

There are also some considerations that may mean daily builds are not suitable for your project, such as:

  • Your project doesn't use feature branches or keep the trunk in a buildable state.
  • Your project is in the early stages of development or in the middle of a major refactoring and not yet ready for testing.
  • Sometimes users think daily builds are supported releases, which can both add to bug noise and generate support requests.
  • If users cannot easily go back to their previous version of your software after using daily builds (for example you do a one-time database upgrade or something from one version to another) then this can be problematic.

Finding existing daily build archives

Launchpad provides a list of all daily builds and the Ubuntu community has a slightly more detailed but manually maintained list of daily builds.

Getting started with daily builds

To get started with your own daily builds you'll need source code in Launchpad, packaging information and a recipe that brings them all together. Let's take a look in more detail.

How Launchpad prioritises builds

Getting started with daily builds >

Packaging/SourceBuilds (last edited 2016-03-15 11:51:31 by cjwatson)