launchpad help|
Size: 3083
Comment:
|
Size: 3087
Comment: +daily-builds no longer exists.
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ~-[[FrontPage|Launchpad Help]] > [[Packaging]] > Daily builds -~ | ~-[[FrontPage|Launchpad Help]] > [[Packaging]] > Source package recipes -~ |
| Line 7: | Line 7: |
| = Daily builds = | = Source package recipes = |
| Line 9: | Line 9: |
| Daily builds are a great way of trying out the latest code from a project, with relatively little effort. | Source package recipes are a great way of trying out the latest code from a project, with relatively little effort. |
| Line 11: | Line 11: |
| 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: | Whether you want to help others test your code, or you want to run a modified or bleeding edge version of your favourite software, with Launchpad's source package recipes you can: |
| Line 15: | Line 15: |
| * sit back and get an automatic build one every day the source changes, which is then published in the PPA of your choice. | * sit back and get an automatic build on every day the source changes, which is then published in the PPA of your choice. |
| Line 19: | Line 19: |
| == Why daily builds? == | Source package builds is the name we give to this Launchpad feature. Most source package builds are automatically built each day and you'll see those referred to as daily builds. |
| Line 21: | Line 21: |
| If you're running a software project, the main advantage of daily builds is that it helps with testing. In particular, it can help: | == Why source package recipes? == If you're running a software project, the main advantage of source package recipes is that they help with testing. In particular, they can help: |
| Line 27: | Line 29: |
| There are also some considerations that may mean daily builds are not suitable for your project, such as: | There are also some considerations that may mean source package recipes are not suitable for your project, such as: |
| Line 31: | Line 33: |
| * 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. |
* Sometimes users think source package 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 source package builds (for example you do a one-time database upgrade or something from one version to another) then this can be problematic. |
| Line 34: | Line 36: |
| == Finding existing daily build archives == | = Getting started with source package recipes = |
| Line 36: | Line 38: |
| Launchpad provides a [[https://code.launchpad.net/+daily-builds|list of all daily builds]] and the Ubuntu community has a [[https://wiki.ubuntu.com/DailyBuilds/AvailableDailyBuilds|slightly more detailed but manually maintained list of daily builds]]. | To [[/GettingStarted|get started with your own source package recipes]] 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. |
| Line 38: | Line 40: |
| = Getting started with daily builds = To [[/GettingStarted|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. ||<tablestyle="width: 100%;" style="width: 50%;"> ~- [[Packaging/PPA/BuildScores|How Launchpad prioritises builds]] -~ ||<style="text-align: right; width: 50%;">~-[[/GettingStarted|Getting started with daily builds >]]-~ || |
||<tablestyle="width: 100%;" style="width: 50%;"> ~- [[Packaging/PPA/BuildScores|How Launchpad prioritises builds]] -~ ||<style="text-align: right; width: 50%;">~-[[/GettingStarted|Getting started with source package recipes >]]-~ || |
Launchpad Help > Packaging > Source package recipes
|
|||
Source package recipes in Launchpad
Source package recipes
Source package recipes 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, with Launchpad's source package recipes you can:
- 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 on 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.
Source package builds is the name we give to this Launchpad feature. Most source package builds are automatically built each day and you'll see those referred to as daily builds.
Why source package recipes?
If you're running a software project, the main advantage of source package recipes is that they help with testing. In particular, they 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 source package recipes 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 source package 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 source package builds (for example you do a one-time database upgrade or something from one version to another) then this can be problematic.
Getting started with source package recipes
To get started with your own source package recipes 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.
