#deployment
5 approved public terms with this tag.
CI/CD
Brouillon de traduction automatique (French) for "CI/CD": Continuous Integration / Continuous Delivery — a set of software engineering practices and tools that automate the process of testing, building, and deploying code changes. CI automatically validates every commit; CD deploys validated code to production frequently and reliably without manual intervention.
“Exemple en brouillon: The team ships 20 times a day safely because their CI/CD pipeline catches regressions automatically.”
DevOps
Brouillon de traduction automatique (French) for "DevOps": A set of practices, tools, and cultural philosophies that unite software development (Dev) and IT operations (Ops) teams. DevOps breaks down silos, automates repetitive tasks, and instills shared responsibility for the full software lifecycle from code to production monitoring.
“Exemple en brouillon: After adopting DevOps, their release cycle went from monthly to daily.”
Inference
Brouillon de traduction automatique (French) for "Inference": The act of running a trained machine learning model on new input data to generate predictions or outputs. Inference is distinct from training — it is the "serving" phase where the model is used in production, and its speed and cost are critical for real-world applications.
“Exemple en brouillon: Inference latency dropped from 2 seconds to 200ms after switching to a quantized model.”
Pull-Based Deployment est un terme GitOps pour a deployment model where an in-cluster agent pulls desired state from source. Il aide les equipes, les humains et les agents a comparer l'etat declare avec les systemes actifs, puis a agir sans pretendre que le deploiement a fait plus que les preuves. Source: OpenGitOps principles; Flux documentation.
“L'equipe a utilise Pull-Based Deployment avant le dejeuner, et la release a arrete de foncer en production avec ses lacets defaits.”
Push-Based Deployment est un terme GitOps pour a deployment model where an outside system pushes changes into the runtime. Il aide les equipes, les humains et les agents a comparer l'etat declare avec les systemes actifs, puis a agir sans pretendre que le deploiement a fait plus que les preuves. Source: OpenGitOps principles.
“L'equipe a utilise Push-Based Deployment avant le dejeuner, et la release a arrete de foncer en production avec ses lacets defaits.”