El dimecres, 19 de febrer del 2025, a les 22:54:00 (Hora estàndard d’Europa central), Ingo Klöcker va escriure: > On Mittwoch, 19. Februar 2025 22:12:58 Mitteleuropäische Normalzeit Albert > > Astals Cid wrote: > > El dimecres, 19 de febrer del 2025, a les 9:58:30 (Hora estàndard del > > Centre> > > d’Europa), Ingo Klöcker va escriure: > > > @Albert: Part of the problem was that you have triggered the flatpak > > > jobs > > > on old pipelines (at least for kwordquiz and kteatime) with an obsolete > > > definition of the flatpak job. To avoid such problems you should always > > > trigger a new pipeline instead of using an old pipeline even if it takes > > > more time to run a full pipeline. In the end it may cost less > > > people-time. > > > > This is the first time i have such a problem. > > > > Restarting the whole pipeline (which may include compiling macos craft > > which is mega slow beacuse we only have 1 builder) is what I did earlier > > and I ended up deciding it took too much CPU time (and my time waiting > > for things to finish to build). > > You are right. It probably doesn't happen that often that a job in a > pipeline gets outdated (provided that new pipelines are triggered more or > less frequently). > > What's your current approach? Do you look at the last master (or release/ > xx.yy) pipeline that ran for a project and then just re-trigger failed jobs?
If the last pipeline is older than 10 days i run a new pipeline else if the pipeline is successful i don't do anything else [pipeline < 10 days and not successful] i retrigger the failed jobs Cheers, Albert > > Regards, > Ingo
