El dilluns, 14 de juliol del 2025, a les 4:36:20 (Hora d’estiu d’Europa central), Aakarsh MJ va escriure: > Hi, sorry for the late reply. > > > That fork/pipeline is not using the template from > > https://invent.kde.org/sysadmin/ci-utilities/-/merge_requests/274 > > is it? > > The contents of the yml file that was tested in the above pipeline are the > same as the template. This > <https://invent.kde.org/aakarshmj/okular/-/blob/master/measurement.yml?ref_t > ype=heads> is the yml file used and this > <https://invent.kde.org/aakarshmj/okular/-/pipelines/946593> is the > pipeline that was run to test it but I understand your concern, in the > final testing I did skip the okular specific jobs (I had tested them in > previous pipeline runs before so I assumed it should work fine as well > since the incremental changes were minimal). What I can do is refork the > okular repo (since the one that I was working with is old now, so the newer > one will definitely be beneficial to incorporate the changes performed > since) and run the template from the .gitlab-ci.yml file by including the > kecolab runner. > > Also one more thing I wanted to ask, will it be fine to include the > manifest.json files that are present in the flathub repo in the okular > repo, since the flatpak pipeline needs it to build the okular flatpak > binary?
I am personally not really interested in maintaining a fork of the flathub manifest. Do you (or someone else) commit to maintain it for a long time? Cheers, Albert > > Cheers, > Aakarsh MJ > > On Tue, Jul 8, 2025 at 4:01 AM Albert Astals Cid <aa...@kde.org> wrote: > > El divendres, 4 de juliol del 2025, a les 11:11:28 (Hora d’estiu d’Europa > > > > central), Joseph P. De Veaugh-Geiss va escriure: > > > Dear Okular team, > > > > > > KDE contributor Aakarsh MJ has integrated KEcoLab into the pipeline for > > > KDE software. We would like to set this up and test it for Okular. > > > > > > Would the Okular team support this integration? > > > > > > https://invent.kde.org/sysadmin/ci-utilities/-/merge_requests/274 > > > > > > This change integration would automatically obtain an energy measurement > > > report at the time of a new Okular release (assigning of tags). Right > > > now the measurement process must be triggered manually. > > > > > > Note: The measurement process can still be triggered manually to test > > > specific changes for energy measurement without needing to deploy the > > > changes to Flathub by providing a manifest.json file. > > > > > > The set up has been tested against the fork of Okular: > > > https://invent.kde.org/aakarshmj/okular/-/pipelines/946593 > > > > That fork/pipeline is not using the template from > > https://invent.kde.org/sysadmin/ci-utilities/-/merge_requests/274 > > is it? > > > > Cheers, > > > > Albert > > > > > Integration would also help keep Okular in line with Blue Angel > > > certification rules, which requires certified software to be measured on > > > a regular basis. > > > > > > What do you think? Could we set this up for Okular? :) > > > > > > Cheers, > > > Joseph > > > (on behalf of the KEcoLab team)
