The most recent example was build failures in www-site when Whimsy was
unavailable.

I thought it would be simple to implement a cache, given how easy it
is to do it so on some other build systems (e.g. the comdev-site
Jenkins job which runs on Cloudbees).

On Wed, 14 Feb 2024 at 08:35, Volkan Yazıcı <vol...@yazi.ci> wrote:
>
> Sebb, what is the real world problem we are trying to address? Do we have
> Pelican builds taking too much time causing trouble for certain projects?
> Do we have expensive network bills due to frequent downloads?
>
> On Tue, Feb 13, 2024 at 3:49 PM sebb <seb...@gmail.com> wrote:
>
> > Is there any way to pass data between runs of Buildbot Pelican builds?
> >
> > This would be useful for caching data that has to be fetched from
> > elsewhere, in case the remote site is down.
> >
> > Or for data that is expensive to generate but changes infrequently.
> >
> > Sebb
> >

Reply via email to