@[email protected] to Jellyfin: The Free Software Media [email protected]English • 7 months agoNew CI, New Repo, A Renewed Push for 10.9.0jellyfin.orgexternal-linkmessage-square19fedilinkarrow-up1191arrow-down12
arrow-up1189arrow-down1external-linkNew CI, New Repo, A Renewed Push for 10.9.0jellyfin.org@[email protected] to Jellyfin: The Free Software Media [email protected]English • 7 months agomessage-square19fedilink
minus-square@AMillionMonkeyslinkEnglish6•7 months agoAwesome! … What’s a CI? (I started reading the link but it doesn’t introduce the term.)
minus-square@FribbtasticlinkEnglish15•7 months agoCould 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-squareDessalineslinkfedilinkEnglish2•7 months agoIt’s how programmers test code (on machines that aren’t the ones they develop on).
minus-squarePossibly linuxlinkfedilinkEnglish1•7 months agoIt 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.