LEP/BuildFromBranchIntoPrimary

Not logged in - Log In / Register

Revision 20 as of 2011-03-24 10:34:59

Clear message

Build from branch into the primary archive

Short description of feature

Contact: MartinPool
LEP: https://dev.launchpad.net/LEP/BuildFromBranchIntoPrimary
On Launchpad: build-from-branch bugs

As an Ubuntu developer
I want Launchpad to build source and binary packages from branches
so that I don't have to both push the branch and also dput a source package

Rationale

At the moment, after making a change, Ubuntu developers must use bzr-builddeb to build a source package, and then dput to upload it. This is unnecessary work. Some developers only upload and don't push the branch.

By allowing Ubuntu developers to build directly from a branch into the primary archive of Ubuntu, we would:

Risks

If the server-side building of packages does not work reliably, users will be blocked from uploading. We can allow a fallback to uploading some

Errors in packaging may be more difficult to see, understand, or debug if they happen on a server rather than locally. However, developers will still have the option to build the package locally.

Background:

Stakeholders

Constraints and Requirements

Must

Since the aim is to provide a superior alternative to something that already exists within Launchpad, we must be at least as good as the current system. Specifically:

Nice to have

Must not

Out of scope

Workflows

Publish a change into Ubuntu

  1. User branches from the source package branch.
  2. Make changes
  3. Commit
  4. Push
  5. Request publication
  6. How do we distinguish commits that ought to be built from those that don't? One way is to say we'll rebuild on things that add a new debian changelog (with a higher version.) Some people commit changes with a series target of 'unreleased' and we could then just actually assemble the package when that flips to be a real series.

Success

How will we know when we are done?

How will we measure how well we have done?

Thoughts?

Changes needed