On Thu, Feb 23, 2023 at 05:30:58PM -0300, Fabiano Rosas wrote:
>
> Hi Alex,
>
> > Daniel P. Berrangé writes:
> >
> >> On Thu, Feb 23, 2023 at 11:21:53AM -0300, Fabiano Rosas wrote:
> >>> I'm not sure if this was discussed previously, but I noticed we're not
> >>> pulling the images we push to th
Hi Alex,
> Daniel P. Berrangé writes:
>
>> On Thu, Feb 23, 2023 at 11:21:53AM -0300, Fabiano Rosas wrote:
>>> I'm not sure if this was discussed previously, but I noticed we're not
>>> pulling the images we push to the registry at every pipeline run.
>>>
>>> I would expect we don't actually ne
Daniel P. Berrangé writes:
> On Thu, Feb 23, 2023 at 11:21:53AM -0300, Fabiano Rosas wrote:
>> I'm not sure if this was discussed previously, but I noticed we're not
>> pulling the images we push to the registry at every pipeline run.
>>
>> I would expect we don't actually need to rebuild contai
Daniel P. Berrangé writes:
> On Thu, Feb 23, 2023 at 11:21:53AM -0300, Fabiano Rosas wrote:
>> I'm not sure if this was discussed previously, but I noticed we're not
>> pulling the images we push to the registry at every pipeline run.
>>
>> I would expect we don't actually need to rebuild cont
On Thu, Feb 23, 2023 at 11:21:53AM -0300, Fabiano Rosas wrote:
> I'm not sure if this was discussed previously, but I noticed we're not
> pulling the images we push to the registry at every pipeline run.
>
> I would expect we don't actually need to rebuild container images at
> _every_ pipeline ru
I'm not sure if this was discussed previously, but I noticed we're not
pulling the images we push to the registry at every pipeline run.
I would expect we don't actually need to rebuild container images at
_every_ pipeline run, so I propose we add a "docker pull" to the
container templates. We alr
