Untold1707@lemm.ee to Jellyfin: The Free Software Media System@lemmy.mlEnglish · 2 年前New CI, New Repo, A Renewed Push for 10.9.0jellyfin.orgexternal-linkmessage-square19linkfedilinkarrow-up1196arrow-down12
arrow-up1194arrow-down1external-linkNew CI, New Repo, A Renewed Push for 10.9.0jellyfin.orgUntold1707@lemm.ee to Jellyfin: The Free Software Media System@lemmy.mlEnglish · 2 年前message-square19linkfedilink
minus-squareAMillionMonkeys@lemmy.worldlinkfedilinkEnglisharrow-up6·2 年前Awesome! … What’s a CI? (I started reading the link but it doesn’t introduce the term.)
minus-squareFribbtastic@lemmy.worldlinkfedilinkEnglisharrow-up15·2 年前Could also be “Continous Integration” (from CI/CD - Continous integration/Continous deployment/delivery) judging by the “Why build a new CI?” section their old “CI” was built on Azure DevOps so I would go with Continous Integration here.
minus-squareDessalines@lemmy.mllinkfedilinkEnglisharrow-up3arrow-down1·2 年前It’s how programmers test code (on machines that aren’t the ones they develop on).
minus-squarePossibly linux@lemmy.ziplinkfedilinkEnglisharrow-up1·2 年前It is part of the automation pipeline. It is basically a system to take new code and process it.
Awesome! … What’s a CI?
(I started reading the link but it doesn’t introduce the term.)
Probably “Code Integration”?
Could also be “Continous Integration” (from CI/CD - Continous integration/Continous deployment/delivery)
judging by the “Why build a new CI?” section their old “CI” was built on Azure DevOps so I would go with Continous Integration here.
Ahh yes, makes more sense
It’s how programmers test code (on machines that aren’t the ones they develop on).
It is part of the automation pipeline. It is basically a system to take new code and process it.