[Qgis-psc] Github account limits

Thu Sep 18 03:41:18 PDT 2025

Hi all,

How about the option four (self-hosted runner). This could be done in our
Hetzner infrastructure.

Since we do all our stuff at Hetzner, we could have Hetzner machines
(physical or virtual) for self-hosted runners.

I really don't like Option 2 much. It sounds too scary to me to have a "pay
as you go".

Andreas

On Thu, 18 Sept 2025 at 12:25, Matthias Kuhn via QGIS-PSC <
qgis-psc at lists.osgeo.org> wrote:

> Hi,
>
> This is exactly what is currently being announced.
> For convenience I pasted the GitHub announcement email below.
> In short, we currently benefit from the fact that Github didn't do a lot
> to enforce cache limits. This will change soon and our CI/CD pipelines will
> be affected.
>
> We could:
>
> - reach out to GitHub Support
> <https://app.github.media/e/er?s=88570519&lid=6288&elqTrackId=4f19fd57fe8747c6b1f620ddc65e1132&elq=51461aa4de9344dc85aca0a4f2559d4d&elqaid=4592&elqat=1&elqak=8AF55301C1175DF4C84D72717A462B0629FB26D8A5C1B92C151B02792754C3A4E1C5> and
> ask for goodwill (this is the point of contact from the mail from GitHub)
> - pay on a "as you go basis" for additional cache
> - use a workaround to store the cache somewhere else (requires development
> time, space somewhere else, potentially slower)
> - or even run the jobs on self hosted runners (which will also come with a
> requirement for hardware and development time, but could potentially speed
> up things)
>
> KR
> Matthias
>
> Your total cache usage exceeds upcoming caching limits
>
> Hello,
>
> GitHub Actions is changing it’s cache policies beginning on October 15th,
> 2025. In the past, all repositories received a maximum 10GB of cache. After
> this date, all repositories will receive 10GB for free and have the option
> to pay for additional storage at a per GB/month rate that is checked at
> hourly intervals.
>
> You are receiving your email because your consumption exceeds 10GB within
> a 24 hour period. As a result, you will need to do one of the following:
>
>    - Increase your cache retention past 10GB: This will have an
>    associated cost but you will keep all cache up to the limit you set.
>    - Maintain your existing limit of 10GB: This will not occur additional
>    cost, but your least recently used cache will be evicted once it reaches
>    the 10GB limit
>    - Modify caching practices: If you reduce what is cached, you will not
>    hit the limit
>
>
> Follow these instructions
> <https://app.github.media/e/er?s=88570519&lid=7727&elqTrackId=f1660b2c23804cb88c27f8b193d9eb6f&elq=51461aa4de9344dc85aca0a4f2559d4d&elqaid=4592&elqat=1&elqak=8AF5894EA84B6C3A8EBF9D7EEF23D8345EFB26D8A5C1B92C151B02792754C3A4E1C5>
> If you would like to view your current usage, follow the instructions here
> <https://app.github.media/e/er?s=88570519&lid=7727&elqTrackId=f1660b2c23804cb88c27f8b193d9eb6f&elq=51461aa4de9344dc85aca0a4f2559d4d&elqaid=4592&elqat=1&elqak=8AF5894EA84B6C3A8EBF9D7EEF23D8345EFB26D8A5C1B92C151B02792754C3A4E1C5>.
> If you have any questions, please reach out to GitHub Support
> <https://app.github.media/e/er?s=88570519&lid=6288&elqTrackId=4f19fd57fe8747c6b1f620ddc65e1132&elq=51461aa4de9344dc85aca0a4f2559d4d&elqaid=4592&elqat=1&elqak=8AF55301C1175DF4C84D72717A462B0629FB26D8A5C1B92C151B02792754C3A4E1C5>
>
> Best,
> The GitHub Team
>
>
>
> On Thu, Sep 18, 2025 at 11:19 AM Marco Bernasocchi <marco at qgis.org> wrote:
>
>> Hey Nyall,
>> Not really sure we can do anything,
>> It looks like it is not an existing feature yet and that it is in te 2025
>> roadmap https://github.com/github/roadmap/issues/1029
>>
>> There are some ideas in this thread
>> https://github.com/orgs/community/discussions/42506
>>
>> What do you think?
>>
>> Cheers
>> Marco Bernasocchi
>>
>> QGIS.org Chair
>> OSGEO.org VP Europe
>> OPENGIS.ch CEO
>> http://berna.io
>>
>> On Thu, 18 Sept 2025, 09:10 Nyall Dawson, <nyall.dawson at gmail.com> wrote:
>>
>>>
>>>
>>> On Thu, 18 Sept 2025, 4:42 pm Marco Bernasocchi, <marco at qgis.org> wrote:
>>>
>>>> Hey Nyall,
>>>> What would we need?
>>>>
>>>
>>> I'd say at least 100gb. 500gb would be better and give us some breathing
>>> room.
>>>
>>> Nyall
>>>
>>>
>>>> I'll try to find someone that knows someone but i need to know what we
>>>> need to ask for.
>>>>
>>>> Cheers
>>>>
>>>> Marco Bernasocchi
>>>>
>>>> QGIS.org Chair
>>>> OSGEO.org VP Europe
>>>> OPENGIS.ch CEO
>>>> http://berna.io
>>>>
>>>> On Thu, 18 Sept 2025, 01:34 Nyall Dawson, <nyall.dawson at gmail.com>
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Tue, 22 Oct 2024 at 00:01, Matthias Kuhn <matthias at opengis.ch>
>>>>> wrote:
>>>>> >
>>>>> > Hi Nyall,
>>>>> >
>>>>> > What did we hit specifically?
>>>>> > If it's about storage for packages, that has been solved by making
>>>>> all packages public (it took me an hour of clicking through each of them
>>>>> ... thanks for adjusting the configuration Nyall)
>>>>> >
>>>>> > What would be nice is more "cache" space, but to my knowledge,
>>>>> that's not something that github sells like this.
>>>>> > Or more powerful machines, that's something they do sell.
>>>>>
>>>>> This morning I received an email from Github stating that we'll soon
>>>>> be force limited to a 10gb cache size, and have the option to pay to
>>>>> upgrade this. This is going to hurt badly, given how poorly the github
>>>>> workflows already perform and how reliant we are on the caching to hold our
>>>>> infrastructure together.  😱
>>>>>
>>>>> Would it be possible now for someone officially to approach Github and
>>>>> ask for special consideration for our project?
>>>>>
>>>>> Nyall
>>>>>
>>>>>
>>>>>
>>>>> >
>>>>> >
>>>>> > On Mon, Oct 21, 2024 at 4:57 AM Nyall Dawson via QGIS-PSC <
>>>>> qgis-psc at lists.osgeo.org> wrote:
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >> On Mon, 21 Oct 2024 at 12:18, Marco Bernasocchi <marco at qgis.org>
>>>>> wrote:
>>>>> >>>
>>>>> >>> Hey Nyall,
>>>>> >>> I'll try my connections :)
>>>>> >>
>>>>> >>
>>>>> >> Thanks Marco!
>>>>> >>>
>>>>> >>>
>>>>> >>> Any specific goal you would like me to reach?
>>>>> >>
>>>>> >>
>>>>> >> For the storage side of things we hit our limit at about the 20th
>>>>> of the month -- so ideally at **least** 1/3rd extra for storage.
>>>>> >>
>>>>> >> And then whatever specification bumps we can get for the runners we
>>>>> can get away with 😁
>>>>> >>
>>>>> >>>
>>>>> >>> Cheers Marco
>>>>> >>>
>>>>> >>> On Sun, 20 Oct 2024, 19:02 Nyall Dawson via QGIS-PSC, <
>>>>> qgis-psc at lists.osgeo.org> wrote:
>>>>> >>>>
>>>>> >>>> Hi PSC!
>>>>> >>>>
>>>>> >>>> The QGIS Github account is currently bumping up against monthly
>>>>> limits, which impacts development as we approach the end of month. When we
>>>>> hit these limits we get jobs which are canceled and/or timeout (due to
>>>>> missing caches).
>>>>> >>>>
>>>>> >>>> I am wondering if someone from PSC is able to officially approach
>>>>> GitHub and request some special consideration here, and see if they'll
>>>>> extend our limits (without cost 😉) as a goodwill gesture toward a popular
>>>>> open source project.
>>>>> >>>>
>>>>> >>>> Any bump they can give us to cached storage limits/job
>>>>> resources/concurrent job limits would GREATLY assist QGIS development...
>>>>> >>>>
>>>>> >>>> Thanks in advance!
>>>>> >>>> Nyall
>>>>> >>>>
>>>>> >>>> _______________________________________________
>>>>> >>>> QGIS-PSC mailing list
>>>>> >>>> QGIS-PSC at lists.osgeo.org
>>>>> >>>> https://lists.osgeo.org/mailman/listinfo/qgis-psc
>>>>> >>
>>>>> >> _______________________________________________
>>>>> >> QGIS-PSC mailing list
>>>>> >> QGIS-PSC at lists.osgeo.org
>>>>> >> https://lists.osgeo.org/mailman/listinfo/qgis-psc
>>>>>
>>>> _______________________________________________
> QGIS-PSC mailing list
> QGIS-PSC at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/qgis-psc
>

-- 

--
Andreas Neumann
QGIS.ORG board member (treasurer)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-psc/attachments/20250918/13990488/attachment-0001.htm>