measuring software's embodied carbon; was: online meetup Wed. 20 Nov. 18h UTC | Green Coding Solutions: "Eco-CI" and "Powerletrics"

[Ingo Klöcker]

On Freitag, 29. November 2024 10:31:10 Mitteleuropäische Normalzeit Ben 
Cooksley wrote:
> On Fri, Nov 22, 2024 at 4:51 AM Volker Krause <vkrause at kde.org> wrote:
> > (2) Optimizing CI operations to reduce energy use
> > 
> > That's IMHO the more interesting goal. However there's probably bigger
> > things
> > to look into first, such as identifying unnecessary pipeline runs (a work
> > branch push/MR creation currently triggers two pipelines which are
> > identical
> > in most cases for example).
> 
> We already have optimisation in place to prevent duplicate jobs triggering
> when a merge request already exists, but yes there is potentially some work
> to be done here to improve efficiency.
> If a developer knows they are going to be immediately creating a MR then
> they can use the Git option ci.skip to prevent CI from running (git push
> -o ci.skip)

There's an even better approach. If one pushes a work branch with
`git push -o merge_request.create` then GitLab immediately creates an MR, runs 
an MR pipeline and does NOT run a branch pipeline. (I have just tested this.)

There's a whole family of merge_request.* options to specify all kinds of 
aspects of the created MR on the `git push` command line:
https://invent.kde.org/help/topics/git/commit.md#push-options

So, I guess `git push -o merge_request.create ...` should become our standard 
way to push a work branch for an MR.

Regards,
Ingo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-community/attachments/20241129/46bdfa97/attachment.sig>