taking autobuilds down? - Pd-dev

7 May 2016


      hi,
a couple of years ago, hans has set up an autobuild farm for Pd-extended.
unfortunately hans has shifted focus to more wondrous things and
Pd-extended has faded away.
only the autobuilders are still running.
this wouldn't be a problem (apart from global warming and all *that*),
if the autobuilders would actually do something meaningful.
as it stands, the only signs of life we had from those machines for
months have been a daily(!) panic mail to the pd-cvs list, detailing how
the build failed.
actually it's not even the build that fails, but - it seems - only the
final upload of the build artefacts.
(though that doesn't matter much: at the end the autobuild is for
naught, as there is no build artefact available for general consumption).
i doubt that anybody ever reads one of those emails. for me, they are
just spamming my mailbox.
apart from that, the build artefacts that are produced are
Pd-extended-0.44 on Debian squeeze (and later): proving that a package
that was obsolete before it was ever released can be build on a system
where the even the long-term support was terminated...
i would therefore like to ask the maintainers of the autobuild farm to
- either fix the build script so it actually succeeds in what it is doing
- OR turn off the autobuilds
i would prefer the 2nd option.
i'm writing this to this list, since according to [1] this is the
official address for the PdLab autobuild farm.
it seems that all active autobuilders are hosted by the hfbk, but i
don't have any more specific contact.
mfgdsar
IOhannes
http://puredata.info/docs/developer/PdLab