Re: building and testing d-i with jenkins
Hi,
On Samstag, 24. November 2012, Holger Levsen wrote:
> > d_i_build_* - there is one job for each git repo referred to in
> > http://anonscm.debian.org/viewvc/d-i/trunk/.mrconfig?view=co
> > Each job pdebuilds the master branch of its git repo on every git push in
> > a sid environment.
> problems found:
All d-i_build_* jobs are now either successful or unstable (meaning, the job
ended with exitcode 0, but the string "^Warning" was found in the logs..)
For most of the last failing ones I've achieved that by exiting with a
warning, if debian/control doesn't exit.
For busybox (and all other "3.0 (quilt)" packages, but that's the only one
atm) I have solved this by running "uscan --download-current-version) before
building.
So there is only one failure left:
> http://jenkins.debian.net/view/d-i_packages/job/d-i_build_debian-installer-
> netboot-images/5/console shows two problems: first, it needs network to
> build (which makes sense for package, but violates policy..) and second,
> it fails to build, even with network.
which is due to having a version in debian/changelog for which no images were
released. debian/control _is_ generated from control.in by rules, but thats a
special target and normaly not needed so run, so maybe removing debian/control
from git is a bit too much?
OTOH it would make this jenkins job turn "unstable" and bring down the
(current) number of problems shown at http://jenkins.debian.net/ from 4 to
3...
The other option would be to special case this package... or some other which
I dont see yet?!
cheers,
Holger
Reply to: