[buildd-tools-devel] the state of daily-builds

[Frans Pop]

On Thursday 01 April 2010, Andreas Barth wrote:
> * Frans Pop (elendil at planet.nl) [100331 21:38]:
> > On Wednesday 31 March 2010, Andreas Barth wrote:
> > > The "svn update" inside the chroot fails now - nothing to worry, but
> > > would be nice if that wouldn't happen.
> >
> > Looks like you currently call 'daily-build build' which also does an
> > update. How about adding a 'build-only' option that skips the update?
>
> Sounds good to me.

I've added the 'build-only' target.

> If the build-only could also be more verbose (i.e. logging during build)
> I'd appreciate that even more. 

Would it be OK if you have to set 'LOG_TO_STDOUT=1' for that in the 
environment? If it is, I have a patch (not yet committed) that does that.

The patch is a bit of a hack due to the use of the pipefail option (needed 
in order not to lose the exit code from make in the pipe to tee), which 
requires bash. But it's the simplest way I could make it work. The main 
changes are included below in case anyone sees a more elegant solution.

> > There have been no amd64 builds the last few days. Any idea why?
>
> Yes. They used keys w/o a forced command.

Ah, OK. It would have been nice if disabling that could have waited until 
after the buildd was converted. Please give re-enabling amd64 priority 
over other arches.

> hppa waits on DSA right now. powerpc sometimes this week.

Great. Please let us know when builds are activated so we can update the 
D-I web page.

> > Should we now set up all arches this way, or do people want to keep
> > their existing builds? I would be happy to have the s390 builds (which
> > I currently run) done on a buildd.
>
> I don't mind. It doesn't take too much effort to set it up, once all
> the preconditions are in place. And it's just "yet another thing
> built".

OK. I guess we'll get back to you on that. I'd like to hear what Joey 
thinks of that as he currently runs two arches, including i386.

BTW, what contact address should we use for these builds? I.e, who (or 
better: what team) will be maintaining them?

Thanks again,
FJP


+do_build () {
+       local t=$1
+       local err=0
+
+       # Commands in these two branches should be the same.
+       if [ "$LOG_TO_STDOUT" = 1 ]; then
+               set -o pipefail
+               (
+               header BUILDING IMAGE FOR $t
+               $ROOTCMD $ROOTCMDOPTS make $t 2>&1
+               ) | tee -a dest/$t.log || err=$?
+               set +o pipefail
+       else
+               (
+               header BUILDING IMAGE FOR $t
+               $ROOTCMD $ROOTCMDOPTS make $t 2>&1
+               ) >> dest/$t.log || err=$?
+       fi
+
+       return $err
+}
[...]
        for t in $TARGETS; do
-               header BUILDING IMAGE FOR $t > dest/$t.log
-               if $ROOTCMD $ROOTCMDOPTS make $t >> dest/$t.log 2>&1; then
+               if do_build $t; then
                        overview "$t success"
                else