Your message dated Sun, 23 Dec 2018 11:15:00 +0100
with message-id <[email protected]>
and subject line Re: [Qa-jenkins-dev] Bug#917119: jenkins.debian.org: Lintian
test jobs have not run since 21st November 2018
has caused the Debian Bug report #917119,
regarding jenkins.debian.org: Lintian test jobs have not run since 21st
November 2018
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
917119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917119
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: jenkins.debian.org
Severity: normal
Hey,
<lamby> Any pointers on why https://jenkins.debian.net/job/lintian-
tests_sid/ has not run in ~1 mo ?
<h01ger> no idea, no
<h01ger> other lintian jobs have run?
<lamby> No, https://jenkins.debian.net/job/lintian-tests_buster/
(for example)
<lamby> Well, more importantly I guess https://jenkins.debian.net/
job/lintian-tests_stretch-backports/
<h01ger> lamby: hm. i guess something killed the triggers. can you
please file a bug against jenkins.debian.org?
Filing bug as requested. Thank you for maintaining
jenkins.debian.org. :)
Best wishes,
--
,''`.
: :' : Chris Lamb
`. `'` [email protected] / chris-lamb.co.uk
`-
--- End Message ---
--- Begin Message ---
On Sat, Dec 22, 2018 at 10:30:41PM +0000, Chris Lamb wrote:
> <lamby> Any pointers on why https://jenkins.debian.net/job/lintian-
> tests_sid/ has not run in ~1 mo ?
Usual thing due to the lintian job being my guinea pig for special
gitlab<->jenkins integration, whereas the secret token gets overwritten
every time the packages-tests set of jobs is deployed.
As an update for those that are keeping tabs on that:
jenkins-job-builder now (it didn't when I started) has a new option so
that I could save the token in the .yaml, but I don't really want to
(it's supposed to be secret after all!).
> Filing bug as requested. Thank you for maintaining
> jenkins.debian.org. :)
I should have taken care of it, and reinstated the token back into the
job configuration, should trigger correctly at the next push.
BTW, you could see something if you looked at the salsa webhook
configuration, in the form of failed delivered (due to permission
errors).
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
--- End Message ---
