<div dir="ltr"><div dir="ltr">On Wed, Jan 24, 2024 at 1:47 AM Alvin Wong <<a href="mailto:alvin@alvinhc.com">alvin@alvinhc.com</a>> wrote:<br></div><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"><u></u>
<div>
<p>Thanks for the info. I guess the scheduled jobs will do for now.<br>
</p>
<p><a href="https://invent.kde.org/websites/krita-org" target="_blank">https://invent.kde.org/websites/krita-org</a> does not seem to have a
scheduled job at the moment. Please add the scheduled job there as
well.</p></div></blockquote><div><br></div><div>You should be able to set this up yourself if you have the ability to push to the repository - and i'd prefer not to set them all up myself as it means when things break I get the emails rather than those who are closer to working on the site (who are better placed to fix it). I have seen discussions going on in #krita regarding who gets that access so it may be that you don't have that access yet.</div><div><br></div><div>If you don't have access i'd suggest asking one of the others to set it up for you.</div><div><br></div><div><div>Cheers,</div><div>Ben </div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
<p>Cheers,<br>
Alvin</p></div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><p>
</p>
<div>On 22/1/2024 4:59, Ben Cooksley wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">On Mon, Jan 22, 2024 at 9:02 AM Albert Astals Cid
<<a href="mailto:aacid@kde.org" target="_blank">aacid@kde.org</a>> wrote:<br>
</div>
<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">El
dimecres, 17 de gener de 2024, a les 14:44:19 (CET), Alvin
Wong va <br>
escriure:<br>
> Hi,<br>
> <br>
> This is a thing I noticed with the websites. Pick any
projects under<br>
> <a href="https://invent.kde.org/websites" rel="noreferrer" target="_blank">https://invent.kde.org/websites</a>
and check the commit history, you can<br>
> see that commits made by Scripty has an icon that
states that the CI/CD<br>
> pipeline has been skipped. This means changes to
translations won't be<br>
> applied until someone else push commits to the site. I
can understand<br>
> skipping builds for applications, but this is not
suitable for the<br>
> websites. Can this be changed?<br>
<br>
You can propose a patch to change it yes. But as far as I
know this isn't <br>
immediately needed, Ben from sysadmin mentioned he had
workarounded it <br>
somehow.<br>
</blockquote>
<div><br>
</div>
<div>Correct, we're using scheduled jobs on Gitlab to rebuild
the sites nightly.</div>
<div>See the log of builds at <a href="https://invent.kde.org/websites/kde-org/-/pipelines" target="_blank">https://invent.kde.org/websites/kde-org/-/pipelines</a>
for some examples of this.</div>
<div><br>
</div>
<div>While not perfect, it is more than sufficient to meet our
needs at this stage until scripty gains the ability to not
skip CI for websites.</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Cheers,<br>
Albert<br>
</blockquote>
<div><br>
</div>
<div>Cheers,</div>
<div>Ben</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
> <br>
> Best Regards,<br>
> Alvin<br>
<br>
<br>
<br>
<br>
</blockquote>
</div>
</div>
</blockquote>
</div>
</blockquote></div></div>