From: Florian Weimer <fw@deneb•enyo.de>
To: git@vger•kernel.org
Subject: sbuild (or whatever) integration
Date: Sat, 19 May 2007 15:17:04 +0200 [thread overview]
Message-ID: <87sl9t6jhr.fsf@mid.deneb.enyo.de> (raw)
I'd like to build something that integrates a Debian autobuilder
(sbuilder probably) with GIT. The intent is to get rid of a
designated integrator (our team is of a size where this seems a
reasonable thing to do[1]) and ensure predictable builds, independent
of what developers happen to have installed on their local
workstations.
Basically, what I want to do is this:
1. Perform a checkout from a specific branch.
2. Synthesize a new version number that is bigger than the previous
one. (This needs to keep a bit of extra-repository state. At
this stage, it's probably a good idea to ensure that the previous
commit built on this branch is an ancestor of the current HEAD.)
3. Generate a fake Debian changelog entry giving the HEAD commit and
the branch name, using the generated version number.
4. Build the whole thing in a controlled environment.
5. Store the build log for later review.
6. If the build was successful, transfer the packages to some
repository (based on the branch that was used).
The GIT repository in step one is a shared one, with an update hook
that that ensures fast-forward merges, as in:
<http://www.kernel.org/pub/software/scm/git/docs/howto/update-hook-example.txt>
The idea is that this means that features are monotonic along a
branch. Ideally, I would like to have something which can assign
meaningful version numbers across two branches, but this is of course
impossible to automatically. I hope to work with a single release
branch anyway, and use at most two (one for testing, one for
production).
Does this sound reasonable? Has anybody built something similar?
[1] This is for internal development, and due to various constraints,
we haven't got developer-specific integration testing
environments. That's why we need to linearize before actual
deployment.
next reply other threads:[~2007-05-19 13:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-19 13:17 Florian Weimer [this message]
2007-05-21 18:15 ` sbuild (or whatever) integration Jan Hudec
2007-05-29 9:26 ` Florian Weimer
2007-05-29 17:15 ` Jan Hudec
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sl9t6jhr.fsf@mid.deneb.enyo.de \
--to=fw@deneb$(echo .)enyo.de \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox