<div dir="ltr"><div class="gmail_default" style="font-size:small">
<p>Hi all,</p>
<p>How about the option four (self-hosted runner). This could be done in our Hetzner infrastructure.</p><p>Since we do all our stuff at Hetzner, we could have Hetzner machines (physical or virtual) for self-hosted runners.</p>
<p>I really don't like Option 2 much. It sounds too scary to me to have a "pay as you go".</p>
<p>Andreas</p>
<br></div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Thu, 18 Sept 2025 at 12:25, Matthias Kuhn via QGIS-PSC <<a href="mailto:qgis-psc@lists.osgeo.org">qgis-psc@lists.osgeo.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>This is exactly what is currently being announced.</div><div>For convenience I pasted the GitHub announcement email below.</div><div>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.</div><div><br></div><div>We could:</div><div><br></div><div>- reach out to <a href="https://app.github.media/e/er?s=88570519&lid=6288&elqTrackId=4f19fd57fe8747c6b1f620ddc65e1132&elq=51461aa4de9344dc85aca0a4f2559d4d&elqaid=4592&elqat=1&elqak=8AF55301C1175DF4C84D72717A462B0629FB26D8A5C1B92C151B02792754C3A4E1C5" title="Using budgets to control spending on metered products" target="_blank">GitHub Support</a> and ask for goodwill (this is the point of contact from the mail from GitHub)</div><div>- pay on a "as you go basis" for additional cache</div><div>- use a workaround to store the cache somewhere else (requires development time, space somewhere else, potentially slower)</div><div>- 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)</div><div><br></div><div>KR<br>Matthias</div><div><br></div><div><div><span id="m_2055582209171094134m_7003574144324821482docs-internal-guid-38a5e494-7fff-f97c-d12a-b435dddcc82f"><h3 dir="ltr" style="line-height:1.38;margin-top:16pt;margin-bottom:4pt"><span style="font-size:14pt;font-family:Arial,sans-serif;color:rgb(67,67,67);background-color:transparent;font-weight:400;font-variant-numeric:normal;font-variant-east-asian:normal;font-variant-alternates:normal;vertical-align:baseline">Your total cache usage exceeds upcoming caching limits</span></h3><div><span style="font-size:14pt;font-family:Arial,sans-serif;color:rgb(67,67,67);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;font-variant-alternates:normal;vertical-align:baseline"><br></span></div></span></div>Hello,<br><br>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.<br><br>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:<ul><li style="margin-left:15px">Increase your cache retention past 10GB: This will have an associated cost but you will keep all cache up to the limit you set.</li><li style="margin-left:15px">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</li><li style="margin-left:15px">Modify caching practices: If you reduce what is cached, you will not hit the limit</li></ul><br><p style="margin:0em 0px 2em;text-align:center"><a href="https://app.github.media/e/er?s=88570519&lid=7727&elqTrackId=f1660b2c23804cb88c27f8b193d9eb6f&elq=51461aa4de9344dc85aca0a4f2559d4d&elqaid=4592&elqat=1&elqak=8AF5894EA84B6C3A8EBF9D7EEF23D8345EFB26D8A5C1B92C151B02792754C3A4E1C5" style="color:rgb(255,255,255);background:rgb(9,105,218);border:2px solid rgb(9,105,218);text-decoration-line:none;padding:10px 20px;border-radius:4px;display:inline-block;font-weight:bold" target="_blank">Follow these instructions</a></p>If you would like to view your current usage, follow the instructions <a href="https://app.github.media/e/er?s=88570519&lid=7727&elqTrackId=f1660b2c23804cb88c27f8b193d9eb6f&elq=51461aa4de9344dc85aca0a4f2559d4d&elqaid=4592&elqat=1&elqak=8AF5894EA84B6C3A8EBF9D7EEF23D8345EFB26D8A5C1B92C151B02792754C3A4E1C5" title="Using budgets to control spending on metered products" target="_blank">here</a>. If you have any questions, please reach out to <a href="https://app.github.media/e/er?s=88570519&lid=6288&elqTrackId=4f19fd57fe8747c6b1f620ddc65e1132&elq=51461aa4de9344dc85aca0a4f2559d4d&elqaid=4592&elqat=1&elqak=8AF55301C1175DF4C84D72717A462B0629FB26D8A5C1B92C151B02792754C3A4E1C5" title="Using budgets to control spending on metered products" target="_blank">GitHub Support</a><br><br>Best,<br>The GitHub Team<p></p><div><br style="font-family:-apple-system,"system-ui","Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol";font-size:16px"></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Sep 18, 2025 at 11:19 AM Marco Bernasocchi <<a href="mailto:marco@qgis.org" target="_blank">marco@qgis.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div>Hey Nyall,</div><div dir="auto">Not really sure we can do anything,</div><div dir="auto">It looks like it is not an existing feature yet and that it is in te 2025 roadmap <a href="https://github.com/github/roadmap/issues/1029" target="_blank">https://github.com/github/roadmap/issues/1029</a></div><div dir="auto"><br></div><div dir="auto">There are some ideas in this thread </div><div dir="auto"><a href="https://github.com/orgs/community/discussions/42506" target="_blank">https://github.com/orgs/community/discussions/42506</a></div><div><br></div><div dir="auto">What do you think?</div><div dir="auto"><br></div><div dir="auto">Cheers </div><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr">Marco Bernasocchi<div><div><br></div><div>QGIS.org Chair<br>OSGEO.org VP Europe<br>OPENGIS.ch CEO</div></div><div><a href="http://berna.io" target="_blank">http://berna.io</a><br></div></div></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, 18 Sept 2025, 09:10 Nyall Dawson, <<a href="mailto:nyall.dawson@gmail.com" target="_blank">nyall.dawson@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, 18 Sept 2025, 4:42 pm Marco Bernasocchi, <<a href="mailto:marco@qgis.org" rel="noreferrer" target="_blank">marco@qgis.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div>Hey Nyall,</div><div dir="auto">What would we need?</div></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">I'd say at least 100gb. 500gb would be better and give us some breathing room.</div><div dir="auto"><br></div><div dir="auto">Nyall</div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div dir="auto"><br></div><div dir="auto">I'll try to find someone that knows someone but i need to know what we need to ask for.</div><div dir="auto"><br></div><div dir="auto">Cheers </div><div><br></div><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr">Marco Bernasocchi<div><div><br></div><div>QGIS.org Chair<br>OSGEO.org VP Europe<br>OPENGIS.ch CEO</div></div><div><a href="http://berna.io" rel="noreferrer noreferrer" target="_blank">http://berna.io</a><br></div></div></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, 18 Sept 2025, 01:34 Nyall Dawson, <<a href="mailto:nyall.dawson@gmail.com" rel="noreferrer noreferrer" target="_blank">nyall.dawson@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><br><br>On Tue, 22 Oct 2024 at 00:01, Matthias Kuhn <<a href="mailto:matthias@opengis.ch" rel="noreferrer noreferrer noreferrer" target="_blank">matthias@opengis.ch</a>> wrote:<br>><br>> Hi Nyall,<br>><br>> What did we hit specifically?<br>> 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)<br>><br>> What would be nice is more "cache" space, but to my knowledge, that's not something that github sells like this.<br>> Or more powerful machines, that's something they do sell.<br><br>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. 😱<div><br></div><div>Would it be possible now for someone officially to approach Github and ask for special consideration for our project?</div><div><br></div><div>Nyall</div><div><br><br> <br>><br>><br>> On Mon, Oct 21, 2024 at 4:57 AM Nyall Dawson via QGIS-PSC <<a href="mailto:qgis-psc@lists.osgeo.org" rel="noreferrer noreferrer noreferrer" target="_blank">qgis-psc@lists.osgeo.org</a>> wrote:<br>>><br>>><br>>><br>>> On Mon, 21 Oct 2024 at 12:18, Marco Bernasocchi <<a href="mailto:marco@qgis.org" rel="noreferrer noreferrer noreferrer" target="_blank">marco@qgis.org</a>> wrote:<br>>>><br>>>> Hey Nyall, <br>>>> I'll try my connections :)<br>>><br>>><br>>> Thanks Marco! <br>>>><br>>>><br>>>> Any specific goal you would like me to reach?<br>>><br>>><br>>> 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.<br>>><br>>> And then whatever specification bumps we can get for the runners we can get away with 😁<br>>><br>>>><br>>>> Cheers Marco <br>>>><br>>>> On Sun, 20 Oct 2024, 19:02 Nyall Dawson via QGIS-PSC, <<a href="mailto:qgis-psc@lists.osgeo.org" rel="noreferrer noreferrer noreferrer" target="_blank">qgis-psc@lists.osgeo.org</a>> wrote:<br>>>>><br>>>>> Hi PSC!<br>>>>><br>>>>> 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).<br>>>>><br>>>>> 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.<br>>>>><br>>>>> Any bump they can give us to cached storage limits/job resources/concurrent job limits would GREATLY assist QGIS development...<br>>>>><br>>>>> Thanks in advance!<br>>>>> Nyall<br>>>>><br>>>>> _______________________________________________<br>>>>> QGIS-PSC mailing list<br>>>>> <a href="mailto:QGIS-PSC@lists.osgeo.org" rel="noreferrer noreferrer noreferrer" target="_blank">QGIS-PSC@lists.osgeo.org</a><br>>>>> <a href="https://lists.osgeo.org/mailman/listinfo/qgis-psc" rel="noreferrer noreferrer noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-psc</a><br>>><br>>> _______________________________________________<br>>> QGIS-PSC mailing list<br>>> <a href="mailto:QGIS-PSC@lists.osgeo.org" rel="noreferrer noreferrer noreferrer" target="_blank">QGIS-PSC@lists.osgeo.org</a><br>>> <a href="https://lists.osgeo.org/mailman/listinfo/qgis-psc" rel="noreferrer noreferrer noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-psc</a></div></div>
</blockquote></div>
</blockquote></div></div></div>
</blockquote></div>
</blockquote></div>
_______________________________________________<br>
QGIS-PSC mailing list<br>
<a href="mailto:QGIS-PSC@lists.osgeo.org" target="_blank">QGIS-PSC@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/qgis-psc" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-psc</a><br>
</blockquote></div><div><br clear="all"></div><br><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><br>--<br>Andreas Neumann<br></div><a href="http://QGIS.ORG" target="_blank">QGIS.ORG</a> board member (treasurer)<br></div></div>