Re: [Tails-dev] Build failed in Jenkins: build_Tails_ISO_exp…

Delete this message

Reply to this message
Author: intrigeri
Date:  
To: The Tails public development discussion list
Subject: Re: [Tails-dev] Build failed in Jenkins: build_Tails_ISO_experimental #2276
anonym wrote (19 May 2015 00:44:47 GMT) :
> On 05/19/2015 01:04 AM, tails-sysadmins@??? wrote:
>> [...]
>> W: Failed to fetch http://ftp.us.debian.org/debian/dists/experimental/main/binary-i386/Packages Hash Sum mismatch
>>
>> E: Some index files failed to download. They have been ignored, or old ones used instead.
>> Fetched 43.1 MB in 19s (2224 kB/s)
>> P: Begin unmounting filesystems...
>> [...]


> Would it be possible to teach jenkins to detect this particular type of
> transient APT issue (which isn't that uncommon), and trigger a rebuild?


I guess that's somehow possible with Jenkins only, but it most likely
requires twisting its semantics quite a bit. I'm happy to give
a closer look at it one of these days, in case there's a neat solution
to this problem => please give me a research ticket :)

However, long-term I think we'll have to use something like Zuul [1],
that's dedicated to orchestrating jobs and to mediating between our
Jenkins job needs, their result, and whatever action should be taken.
IIRC that's how the OpenStack project CI handles this kind
of problems.

On the short term, perhaps teaching APT or our build system to retry
such operations on failures would be a good enough, and muuuch
simpler, workaround.

[1] https://www.mediawiki.org/wiki/Continuous_integration/Zuul

Cheers!
--
intrigeri