On Wed, Jan 24, 2024 at 1:47 AM Alvin Wong <alvin@alvinhc.com> wrote:

Thanks for the info. I guess the scheduled jobs will do for now.

https://invent.kde.org/websites/krita-org does not seem to have a scheduled job at the moment. Please add the scheduled job there as well.


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.

If you don't have access i'd suggest asking one of the others to set it up for you.

Cheers,
Ben 

Cheers,
Alvin

On 22/1/2024 4:59, Ben Cooksley wrote:
On Mon, Jan 22, 2024 at 9:02 AM Albert Astals Cid <aacid@kde.org> wrote:
El dimecres, 17 de gener de 2024, a les 14:44:19 (CET), Alvin Wong va
escriure:
> Hi,
>
> This is a thing I noticed with the websites. Pick any projects under
> https://invent.kde.org/websites and check the commit history, you can
> see that commits made by Scripty has an icon that states that the CI/CD
> pipeline has been skipped. This means changes to translations won't be
> applied until someone else push commits to the site. I can understand
> skipping builds for applications, but this is not suitable for the
> websites. Can this be changed?

You can propose a patch to change it yes. But as far as I know this isn't
immediately needed, Ben from sysadmin mentioned he had workarounded it
somehow.

Correct, we're using scheduled jobs on Gitlab to rebuild the sites nightly.
See the log of builds at https://invent.kde.org/websites/kde-org/-/pipelines for some examples of this.

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.
 

Cheers,
  Albert

Cheers,
Ben
 

>
> Best Regards,
> Alvin