Daniel P. Berrangé writes:
> On Tue, Sep 27, 2022 at 08:40:44PM +0200, Thomas Huth wrote:
>> On 27/09/2022 19.57, Daniel P. Berrangé wrote:
>> > On Tue, Sep 27, 2022 at 01:36:20PM -0400, Stefan Hajnoczi wrote:
>> > > On Tue, 27 Sept 2022 at 11:54, Daniel P. Berrangé
>> > > wrote:
>> > > >
>>
On Wed, 28 Sept 2022 at 08:28, Alex Bennée wrote:
> We shall find out soon enough. The code came through today so I've
> applied it to the project which shows we are now on the "Ultimate" tier.
Thank you, Alex!
Stefan
On Tue, Sep 27, 2022 at 03:10:54PM -0400, Stefan Hajnoczi wrote:
> On Tue, 27 Sept 2022 at 15:04, Thomas Huth wrote:
> >
> > On 27/09/2022 20.47, Stefan Hajnoczi wrote:
> > > On Tue, 27 Sept 2022 at 14:40, Thomas Huth wrote:
> > >>
> > >> On 27/09/2022 19.57, Daniel P. Berrangé wrote:
> > >>> On
On Tue, Sep 27, 2022 at 08:40:44PM +0200, Thomas Huth wrote:
> On 27/09/2022 19.57, Daniel P. Berrangé wrote:
> > On Tue, Sep 27, 2022 at 01:36:20PM -0400, Stefan Hajnoczi wrote:
> > > On Tue, 27 Sept 2022 at 11:54, Daniel P. Berrangé
> > > wrote:
> > > >
> > > > On Tue, Sep 27, 2022 at 11:44:45
On 27/09/2022 21.10, Stefan Hajnoczi wrote:
On Tue, 27 Sept 2022 at 15:04, Thomas Huth wrote:
On 27/09/2022 20.47, Stefan Hajnoczi wrote:
On Tue, 27 Sept 2022 at 14:40, Thomas Huth wrote:
On 27/09/2022 19.57, Daniel P. Berrangé wrote:
On Tue, Sep 27, 2022 at 01:36:20PM -0400, Stefan Hajno
On Tue, 27 Sept 2022 at 15:04, Thomas Huth wrote:
>
> On 27/09/2022 20.47, Stefan Hajnoczi wrote:
> > On Tue, 27 Sept 2022 at 14:40, Thomas Huth wrote:
> >>
> >> On 27/09/2022 19.57, Daniel P. Berrangé wrote:
> >>> On Tue, Sep 27, 2022 at 01:36:20PM -0400, Stefan Hajnoczi wrote:
> On Tue, 27
On 27/09/2022 20.47, Stefan Hajnoczi wrote:
On Tue, 27 Sept 2022 at 14:40, Thomas Huth wrote:
On 27/09/2022 19.57, Daniel P. Berrangé wrote:
On Tue, Sep 27, 2022 at 01:36:20PM -0400, Stefan Hajnoczi wrote:
On Tue, 27 Sept 2022 at 11:54, Daniel P. Berrangé wrote:
On Tue, Sep 27, 2022 at 11
On Tue, 27 Sept 2022 at 14:40, Thomas Huth wrote:
>
> On 27/09/2022 19.57, Daniel P. Berrangé wrote:
> > On Tue, Sep 27, 2022 at 01:36:20PM -0400, Stefan Hajnoczi wrote:
> >> On Tue, 27 Sept 2022 at 11:54, Daniel P. Berrangé
> >> wrote:
> >>>
> >>> On Tue, Sep 27, 2022 at 11:44:45AM -0400, Stefa
On 27/09/2022 19.57, Daniel P. Berrangé wrote:
On Tue, Sep 27, 2022 at 01:36:20PM -0400, Stefan Hajnoczi wrote:
On Tue, 27 Sept 2022 at 11:54, Daniel P. Berrangé wrote:
On Tue, Sep 27, 2022 at 11:44:45AM -0400, Stefan Hajnoczi wrote:
On Tue, 27 Sept 2022 at 05:02, Thomas Huth wrote:
now th
On Tue, Sep 27, 2022 at 01:36:20PM -0400, Stefan Hajnoczi wrote:
> On Tue, 27 Sept 2022 at 11:54, Daniel P. Berrangé wrote:
> >
> > On Tue, Sep 27, 2022 at 11:44:45AM -0400, Stefan Hajnoczi wrote:
> > > On Tue, 27 Sept 2022 at 05:02, Thomas Huth wrote:
> > > > now that Gitlab is giving us pressur
On Tue, 27 Sept 2022 at 11:54, Daniel P. Berrangé wrote:
>
> On Tue, Sep 27, 2022 at 11:44:45AM -0400, Stefan Hajnoczi wrote:
> > On Tue, 27 Sept 2022 at 05:02, Thomas Huth wrote:
> > > now that Gitlab is giving us pressure on the amount of free CI minutes, I
> > > wonder whether we should maybe
On Tue, 27 Sept 2022 at 05:02, Thomas Huth wrote:
> now that Gitlab is giving us pressure on the amount of free CI minutes, I
> wonder whether we should maybe move the Cirrus-CI jobs out of the gitlab-CI
> dashboard again? We could add the jobs to our .cirrus-ci.yml file instead,
> like we did it
On Tue, Sep 27, 2022 at 11:44:45AM -0400, Stefan Hajnoczi wrote:
> On Tue, 27 Sept 2022 at 05:02, Thomas Huth wrote:
> > now that Gitlab is giving us pressure on the amount of free CI minutes, I
> > wonder whether we should maybe move the Cirrus-CI jobs out of the gitlab-CI
> > dashboard again? We
Hi all,
now that Gitlab is giving us pressure on the amount of free CI minutes, I
wonder whether we should maybe move the Cirrus-CI jobs out of the gitlab-CI
dashboard again? We could add the jobs to our .cirrus-ci.yml file instead,
like we did it in former times...
Big advantage would be
14 matches
Mail list logo