Recently, the vyatta-wireless package builds failed a few times despite building successfully on a local virtual build host. While grinding through the Jenkins build output, I possibly found the culprit here:
dh_clean dpkg-source --after-build clearfog dpkg-buildpackage: binary-only upload (no source included) [clearfog] $ /bin/bash /tmp/jenkins1885836775543800418.sh current Pseudo-terminal will not be allocated because stdin is not a terminal. # CULPRIT BELOW! ssh: connect to host dev.packages.vyos.net port 222: Connection timed out # CULPRIT ABOVE! Build step 'Execute shell' marked build as failure Performing Post build task... Could not match :passed : False Logical operation result is FALSE Skipping script : #!/bin/bash TOKEN=`cat ~/tokennr` REPO="vyatta-wireless"
I then made a diff of both console output files -- jessie64devel.vyos.net left side, Clearfog right side (see screenshot):
So it seems that the Clearfog build machine just lacks some firewall ACLs to enable ssh access to dev.packages.vyos.net. The lack of it forces the whole package build to fail and the package won't be upgraded on dev.packages.vyos.net and therefore not be included in nightly builds.
I'd be glad if someone with access to the infrastructure would take a look into this :-)