self-hosted in order to validate the usage for the PRs.
>> >>
>> >> -- Rajesh
>> >>
>> >>
>> >> From: Jarek Potiuk
>> >> Reply-To: "dev@airflow.apache.org"
>> >> Date: Friday, April 5, 2024 at 8:36 AM
>>
1 with trying this out. I agree with keeping the canary builds
> >> self-hosted in order to validate the usage for the PRs.
> >>
> >> -- Rajesh
> >>
> >>
> >> From: Jarek Potiuk
> >> Reply-To: "dev@airflow.apache.org"
> >>
"
>> Date: Friday, April 5, 2024 at 8:36 AM
>> To: "dev@airflow.apache.org"
>> Subject: RE: [EXTERNAL] [COURRIEL EXTERNE] [DISCUSS] Consider disabling
>> self-hosted runners for commiter PRs
>>
>>
>> CAUTION: This email originated from outside of
;
> Date: Friday, April 5, 2024 at 8:36 AM
> To: "dev@airflow.apache.org"
> Subject: RE: [EXTERNAL] [COURRIEL EXTERNE] [DISCUSS] Consider disabling
> self-hosted runners for commiter PRs
>
>
> CAUTION: This email originated from outside of the organization. Do not
>
[EXTERNAL] [COURRIEL EXTERNE] [DISCUSS] Consider disabling
self-hosted runners for commiter PRs
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you can confirm the sender and know the
content is safe.
AVERTISSEMENT: Ce courrier électr
ote:
> >
> > > Interested in seeing the difference, +1
> > >
> > >
> > > - ferruzzi
> > >
> > >
> > >
> > > From: Oliveira, Niko
> > > Sent: Thursday, Apr
ev@airflow.apache.org
> > Subject: RE: [EXTERNAL] [COURRIEL EXTERNE] [DISCUSS] Consider disabling
> > self-hosted runners for commiter PRs
> >
> > CAUTION: This email originated from outside of the organization. Do not
> > click links or open attachments unless you c
; - ferruzzi
> >
> >
> >
> > From: Oliveira, Niko
> > Sent: Thursday, April 4, 2024 2:00 PM
> > To: dev@airflow.apache.org
> > Subject: RE: [EXTERNAL] [COURRIEL EXTERNE] [DISCUSS] Consider disabling
> > self-hosted runne
iko
> Sent: Thursday, April 4, 2024 2:00 PM
> To: dev@airflow.apache.org
> Subject: RE: [EXTERNAL] [COURRIEL EXTERNE] [DISCUSS] Consider disabling
> self-hosted runners for commiter PRs
>
> CAUTION: This email originated from outside of the organization. Do not
> click
Interested in seeing the difference, +1
- ferruzzi
From: Oliveira, Niko
Sent: Thursday, April 4, 2024 2:00 PM
To: dev@airflow.apache.org
Subject: RE: [EXTERNAL] [COURRIEL EXTERNE] [DISCUSS] Consider disabling
self-hosted runners for commiter PRs
CAUTION
disabling
self-hosted runners for commiter PRs
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you can confirm the sender and know the
content is safe.
AVERTISSEMENT: Ce courrier électronique provient d’un expéditeur externe. Ne
cliquez
+1 from me to this idea.
Sounds very reasonable to me.
At times, my experience has been better with public runners instead of
self-hosted runners :)
And like already mentioned in the discussion, I think having the ability of
a applying the label "use-self-hosted-runners" to be used for critical
Hello everyone,
TL;DR With some recent changes in GitHub Actions and the fact that ASF has
a lot of runners available donated for all the builds, I think we could
experiment with disabling "self-hosted" runners for committer builds.
The self-hosted runners of ours have been extremely helpful
13 matches
Mail list logo
