an Yazıcı 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
Yazıcı 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 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 wrote:
> Is there any way to pass data betw
that can be shared between buildbot vms and then
> give repositories a cache directory.
It looks like there is only one host for the pelican builds -
https://ci2.apache.org/#/builders/3
> Regards,
> Dave
>
>
> >
> >>> On Feb 13, 2024, at 6:49 AM, sebb wrote:
&
rage that can be shared between buildbot vms and then
> give repositories a cache directory.
I wonder if our Devlocity/gradle enterprise instance could be of help here?
>
> Regards,
> Dave
>
>
>>
>>>> On Feb 13, 2024, at 6:49 AM, sebb wrote:
>>&g
gt; On Feb 13, 2024, at 6:49 AM, sebb 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
>>
,
as well as requiring credentials to do the update.
> > On Feb 13, 2024, at 6:49 AM, sebb 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,
One way that could work is to put a cache into a branch of the repository …
It could double as a data cache.
> On Feb 13, 2024, at 6:49 AM, sebb wrote:
>
> Is there any way to pass data between runs of Buildbot Pelican builds?
>
> This would be useful for caching data that ha
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
there any way to pass data between runs of Jenkins Pelican builds?
> >
> > This would be useful for caching data that has to be fetched from
> > elsewhere, in case the remote site is down.
> >
> > Sebb
ata between runs of Jenkins Pelican builds?
>
> This would be useful for caching data that has to be fetched from
> elsewhere, in case the remote site is down.
>
> Sebb
Is there any way to pass data between runs of Jenkins Pelican builds?
This would be useful for caching data that has to be fetched from
elsewhere, in case the remote site is down.
Sebb
Hi Daniel,
> On Apr 28, 2021, at 7:52 AM, Daniel Gruno wrote:
>
>
>
> On 2021/04/28 14:26:08, Dave Fisher wrote:
>> Hi Kirs,
>>
>> I’m working on Pelican builds myself and I noticed you have failing builds
>> on the buildbot.
>
> dolphinsch
On 2021/04/28 14:26:08, Dave Fisher wrote:
> Hi Kirs,
>
> I’m working on Pelican builds myself and I noticed you have failing builds on
> the buildbot.
dolphinscheduler-website is a docsite repo, not pelican. Their .asf.yaml is
straight-up wrong. It should not have the pelica
Hi Kirs,
I’m working on Pelican builds myself and I noticed you have failing builds on
the buildbot.
For instance: https://ci2.apache.org/#/builders/3/builds/2309
You are missing configuration from your pelicanconf.py file specifically the
PATH.
See https://docs.getpelican.com/en/latest
15 matches
Mail list logo
