vcswatch reports that
this package seems to have new commits in its VCS but has
not yet updated debian/changelog. You should consider updating
the Debian changelog and uploading this new version into the archive.
Here are the relevant commit logs:
commit ebfa17be59d6e8ef8b0def4827897ae7df6c2501
Author: Michael Prokop <mika@jenkins-debian-glue.org>
Date: Fri Apr 11 20:10:51 2025 +0200
puppet: update usage instructions to clarify current plugin situation
We no longer install the Jenkins plugins via puppet. Provide
instructions that are actually related to what Jenkins does nowadays
with its setup wizard (verified with v2.492.3).
commit 58059f71fcbca1bcafee443d5c455e82fa81fc56
Author: Michael Prokop <mika@jenkins-debian-glue.org>
Date: Fri Apr 11 20:31:19 2025 +0200
puppet: drop support for ancient openjdk releases
Ubuntu 18.01 as well as openjdk-8-jre-headless are no longer
relevant nor supported by current Jenkins versions.
commit f263a20a84e27603f8f11dfc9994676bb4690188
Author: Michael Prokop <mika@jenkins-debian-glue.org>
Date: Fri Apr 11 13:14:02 2025 +0200
puppet: drop Jenkins plugin support
It's impossible to catch up with the Jenkins plugin dependencies, and
even dependencies no longer exist and cause serious failures within the
puppet run, like:
| Error: 'wget http://updates.jenkins.io/latest/ace-editor.hpi' returned 8 instead of one of [0]
| Error: /Stage[main]/Jenkins::Software/Jenkins::Plugin::Install[ace-editor]/Exec[download-ace-editor]/returns: change from 'notrun' to ['0'] failed: 'wget http://updates.jenkins.io/latest/ace-editor.hpi' returned 8 instead of one of [0]
| [...]
| Error: 'wget http://updates.jenkins.io/latest/handlebars.hpi' returned 8 instead of one of [0]
| Error: /Stage[main]/Jenkins::Software/Jenkins::Plugin::Install[handlebars]/Exec[download-handlebars]/returns: change from 'notrun' to ['0'] failed: 'wget http://updates.jenkins.io/latest/handlebars.hpi' returned 8 instead of one of [0]
| [...]
| Error: 'wget http://updates.jenkins.io/latest/momentjs.hpi' returned 8 instead of one of [0]
| Error: /Stage[main]/Jenkins::Software/Jenkins::Plugin::Install[momentjs]/Exec[download-momentjs]/returns: change from 'notrun' to ['0'] failed: 'wget http://updates.jenkins.io/latest/momentjs.hpi' returned 8 instead of one of [0]
Let's not pretend to provide a working setup with this, but instead
point users to the setup wizard of Jenkins, which provides a pretty
OK-ish default setup for our needs.
commit 2f0ce4e60cad2182c1a3543e4dc5d4d77bfd68d3
Author: Michael Prokop <mika@jenkins-debian-glue.org>
Date: Fri Apr 11 13:16:40 2025 +0200
puppet: drop jenkins.grml.org usage, use j-d-g packages from Debian instead
The jenkins-debian-glue packages are shipped from within Debian, and
even Ubuntu provides them through universe.
We're deprecating the jenkins.grml.org service, so remove
its usage and support from within our automated setup.
commit 6fa08b890cf0eb72ac2d474aa23f8004d565acc6
Author: Michael Prokop <mika@jenkins-debian-glue.org>
Date: Thu Apr 10 10:03:32 2025 +0200
jdg-tap-tool-dispatcher: fix file-list handling with jdg-tap-merge-conflict
Noticed via:
| *** Skipping pep8 checks as tool pep8 isn't present ***
| mkdir -p reports/source/functions ; /usr/bin/jdg-tap-checkbashism source/functions/host-summary > reports/source/functions/host-summary_checkbashism.tap ; /usr/bin/jdg-tap-perlcritic source/functions/host-summary > reports/source/functions/host-summary_perlcritic.tap ; /usr/bin/jdg-tap-shellcheck source/functions/host-summary > reports/source/functions/host-summary_shellcheck.tap ;
| File source/functions/host-summary doesn't look like perl [Bourne-Again shell script, Unicode text, UTF-8 text executable]. Ignoring.
| Error: file {} could not be read.
| *** Getting rid of empty files ***
We're invoking jdg-tap-tool-dispatcher with the -f ... option,
to pass a certain list of files that should be checked.
Our generated execution script from jdg-tap-tool-dispatcher
looks like this:
sed 's#^#source/#g' < /code/git.change | parallel -v -- \
mkdir -p reports'/'{//} ';' \
/usr/bin/jdg-tap-checkbashism '{}' '>' reports'/{}_checkbashism.tap' ';' \
/usr/bin/jdg-tap-perlcritic '{}' '>' reports'/{}_perlcritic.tap' ';' \
/usr/bin/jdg-tap-shellcheck '{}' '>' reports'/{}_shellcheck.tap' ';'
/usr/bin/jdg-tap-merge-conflict '{}' '>' reports'/{}_mergecheck.tap' ';'
So we try to invoke /usr/bin/jdg-tap-merge-conflict outside of the
actual parallel run, as the trailing '\' in the shellcheck command line
is missing.
So /usr/bin/jdg-tap-merge-conflict is invoked with literally '{}', and
therefore complaining with:
Error: file {} could not be read.
To avoid such a failure we need to end all jdp-* command lines with a
"\" to mark them for continuation in next line. Also let's add a
noop line to the end of the script to get valid code syntax. New
execution script now looks like this then:
sed 's#^#source/#g' < /code/git.change | parallel -v -- \
mkdir -p reports'/'{//} ';' \
/usr/bin/jdg-tap-checkbashism '{}' '>' reports'/{}_checkbashism.tap' ';' \
/usr/bin/jdg-tap-perlcritic '{}' '>' reports'/{}_perlcritic.tap' ';' \
/usr/bin/jdg-tap-shellcheck '{}' '>' reports'/{}_shellcheck.tap' ';' \
/usr/bin/jdg-tap-merge-conflict '{}' '>' reports'/{}_mergecheck.tap' ';' \
# EOF
While at it, fix comment regarding generated script (we execute the
generated script, not generate the executed script :)), and also fix
a shellcheck issue reported for tap/jdg-tap-tool-dispatcher:
| In tap/jdg-tap-tool-dispatcher line 12:
| if [ $? -ne 0 ]; then
| ^-- SC2181 (style): Check exit code directly with e.g. 'if ! mycmd;', not indirectly with $?.
Development sponsored by Sipwise GmbH, recorded as
MT#61842 in customers' ticket system.
![[bug history graph]](https://qa.debian.org/data/bts/graphs/j/jenkins-debian-glue.png){kind=link}