As of upstream git (https://github.com/mika/jenkins-debian-glue/),
commit 29ccbab6fac0e62eb7b084ef4c42ab1a56128ac6
Upstream changes:
* 807dcd7 Release new version 0.23.0
* 2fb6064 Release new version 0.23.1
* d0e57c7 d/control: replace deprecated Recommends on pep8 with pycodestyle
* d386ec4 tap/jdg-tap-pep8: check for pycodestyle by default
* 7e78034 tap/jdg-tap-tool-dispatcher: enable jdg-tap-pep8 via pycodestyle
* 9cde559 Release new version 0.23.2
* ddb1157 Makefile: add missing test
* 9306b84 Release new version 0.23.3
* d5bd823 Release new version 0.23.4
* 2f0ce4e puppet: drop jenkins.grml.org usage, use j-d-g packages from Debian instead
* f263a20 puppet: drop Jenkins plugin support
* 58059f7 puppet: drop support for ancient openjdk releases
* ebfa17b puppet: update usage instructions to clarify current plugin situation
* 2044974 d/control: Bump Standards-Version to 4.7.2
* eb20a31 Release new version 0.23.5
* 52c40f3 build: Mark all current targets as .PHONY
* a7e6ca4 build: Split the test suite into its own check target
* 9552ba2 build: Do not remove Debian packaging artifacts from the clean target
* 389076c build: Remove target dependency on shell glob pattern
* 94d8184 build: Use GNU Make wildcard function instead of a raw shell glob pattern
* 4a3f89a build: For correctness make install and deploy depend on the build target
* bc4c414 Update changelog for 0.23.6 release
* f1eb26d build-and-provide-package: support usage of Debian packages without Priority field with bookworm and older
* d718db0 Revert "build-and-provide-package: support usage of Debian packages without Priority field with bookworm and older"
* 2cf878f debian/control: wrap-and-sort -sat
* 22fee1f Fix pycodestyle issues
Change-Id: I3e26dfe64bba43d161d6ffd1ef72a572674e6232
* debian/control:
- add ruby dependency when testing
- shunit2 is only needed for testing
Read just 32 bytes of the file trying to guess the type
Fix#247
Change-Id: I0f19d4593d2c477be79dea559964d3415624e8c4
eatmydata support gets enabled by default if it's installed on
the host system and when building for a recent Debian/Ubuntu
version (Debian/jessie + Ubuntu/vivid or newer). Usage can be
forced via USE_EATMYDATA=true and disabled via
USE_EATMYDATA=false.
ccache support can be enabled via USE_CCACHE=true
Thanks to Franco (nextime) Lanza for the initial patch in
https://github.com/mika/jenkins-debian-glue/pull/125
The parallel tools support different options, so we need
to check for the according version. But since moreutils
might be present because of other packages depending on
them we should support it as alternative.
When upgrading from jenkins-debian-glue <=0.13 we run into:
| Unpacking jenkins-debian-glue (0.14.0+0~20150822132303.252~1.gbp3da4c8) over (0.13.0+0~20150727152008.249~1.gbp026ace) ...
| dpkg: error processing archive /var/cache/apt/archives/jenkins-debian-glue_0.14.0+0~20150822132303.252~1.gbp3da4c8_all.deb (--unpack):
| trying to overwrite '/usr/bin/checkbashism_tap', which is also in package jenkins-debian-glue-buildenv-taptools 0.13.0+0~20150727152008.249~1.gbp026ace
When uploading towards Debian we shouldn't have to deal with
so many Debian packages, instead provide one single package
which depends on all relevant packages and if someone
wants to have just a specific subset installed on their
system they should do so through their own metapackage or
configuration management.
Thanks: Christian Hofstaedtler <christian@hofstaedtler.name>
if [ - z "$HO" ]; then
echo HOLA
fi
reports/source/t.sh_shellcheck.tap
1..3
not ok 1 source/t.sh:3:1: note: The mentioned parser error was in this if expression. [SC1009]
not ok 2 source/t.sh:3:4: error: Couldn't parse this test expression. [SC1073]
not ok 3 source/t.sh:3:8: error: Unexpected "z". Fix any mentioned problems and try again. [SC1072]
* Don't use qemu-debootstrap for building i386 on amd64 and arch all packages
* Recommend qemu-user-static package
* While at it run dpkg-architecture just once
* Explicitely add --architecture=... when (deb)bootstrapping the environments
via qemu, otherwise it might fail with:
| I: Running command: chroot . /debootstrap/debootstrap --second-stage
| chroot: failed to run command `/debootstrap/debootstrap': Exec format error
when running on Debian/wheezy (seems to work fine without explicit
--architecture on Debian/jessie systems)
Related to pull request #114, commit 392c8f4206826e4cd911932b2760824b2d3343d
Running the different *_tap tools in parallel allows for significant
speedups on our build server; a job with ~440 files took 1min35s
previously, and now takes < 30s to complete.
dpkg-buildpackage needs the fakeroot, otherwise fails with:
| + dpkg-buildpackage -uc -us -nc -d -S -i -I --source-option=--unapply-patches
| dpkg-buildpackage: error: fakeroot not found, either install the fakeroot
| package, specify a command with the -r option, or run this as root
| Build step 'Execute shell' marked build as failure
reprepro should be present on every system to avoid failures with
package inclusion in repository. Depending on reprepro in the
main jenkins-debian-glue package avoids that problem while still
supporting setups where cowbuilder etc aren't necessary on
repository-only systems.
Closes: #76
We want to have jenkins-debian-glue-repoenv by default on
automatically installed machines and users typically want it,
though they don't strictly need it, so add it to Recommends.
jenkins-debian-glue is the base package containing all required scripts
- jenkins-debian-glue-repoenv - virtual package for repo only slaves
- jenkins-debian-glue-buildenv - virtual package for build only slaves
When using the dpkg 3.0 (quilt) format (see debian/source/format)
there might be quilt patches still applied in the source tree,
either because of a broken build or under certain - though not yet
clearly identified - situations which seem to end with a
"diff: standard output: Broken pipe" message in the build log.
This then might end up in a build failure like:
| + cd /var/lib/jenkins/workspace/glusterfs-source
| + dpkg-source -i -I -b source
| dpkg-source: info: using source format `3.0 (quilt)'
| diff: standard output: Broken pipe
| diff: standard output: Broken pipe
| dpkg-source: info: building glusterfs using existing ./glusterfs_3.2.7.orig.tar.gz
| dpkg-source: info: local changes detected, the modified files are:
| source/ChangeLog
| source/doc/gluster.8
| source/doc/glusterfs.8
| source/libglusterfs/src/common-utils.c
| source/rpc/rpc-lib/src/rpcsvc.c
| source/xlators/mgmt/glusterd/src/glusterd-rpc-ops.c
| dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/glusterfs_3.2.7-2~bpo60+1.diff.3Wkisr
| dpkg-source: info: you can integrate the local changes with dpkg-source --commit
While everything has been cleanly integrated in debian/patches/
the build process fails because it looks like there have been
modifications to upstream sources whereas it's just wrong
information about patches applied.
So instead make sure we enter a clean git repository before doing
any changes (this can be skipped via SKIP_GIT_CLEANUP=true) and
also unapply all present quilt patches (this can be skipped via
SKIP_QUILT_CLEANUP=true). Finally replace the dpkg-source call
with dpkg-buildpackage and its --source-option=--unapply-patches
feature. While the combination of the git cleanup, quilt cleanup
and dpkg-source->dpkg-buildpackage is more than explicitely
necessary this provides more flexibility if needed.
Thanks: Raphael Hertzog <hertzog@debian.org> for his dpkg related feedback
svn2cl is no longer available in the unstable version of
subversion-tools, instead it's provided as separate package
as of subversion-tools 1.7.5-1.
Closes#45
Michael Prokop
Victor Seva
Debian Janitor
Michael Prokop
Guillem Jover
Michael Prokop
Christian Hofstaedtler
Bernhard Miklautz
Michael Prokop