Define the new internet.
Look up the words people use online, add the ones we missed, and help make the internet easier to understand.
Look up the words people use online, add the ones we missed, and help make the internet easier to understand.
2,337 definitions
Rascunho de traducao automatica (Portuguese) for "Pipeline Data Split": Pipeline Data Split is a ml experimental control that separates examples for training, validation, and testing for automated data and model workflow. It uses randomization rules, leakage checks, and seed tracking so teams can measure generalization honestly while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The machine learning team used Pipeline Data Split when the pipeline missed a validation step, so the team could measure generalization honestly before the model moved into evaluation.”
Rascunho de traducao automatica (Portuguese) for "Artifact Incident Timeline": Artifact Incident Timeline is a devops response record that orders alerts, actions, and decisions during an incident for build output and package delivery. It uses timestamps, owners, and evidence links so teams can learn from outages without guesswork while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The DevOps team used Artifact Incident Timeline when the container image was signed, so the team could learn from outages without guesswork before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) for "CI Trace Link": CI Trace Link is a devops observability link that connects a deployment or workflow to runtime evidence for continuous integration workflows. It uses trace IDs, span metadata, and release identifiers so teams can debug production changes faster while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The DevOps team used CI Trace Link when a pull request entered the build queue, so the team could debug production changes faster before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) for "CD Trace Link": CD Trace Link is a devops observability link that connects a deployment or workflow to runtime evidence for deployment automation and promotion. It uses trace IDs, span metadata, and release identifiers so teams can debug production changes faster while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The DevOps team used CD Trace Link when the release moved toward production, so the team could debug production changes faster before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) for "Rollback Config Drift Check": Rollback Config Drift Check is a devops consistency check that finds differences between intended and live configuration for recovery from a bad deployment. It uses desired state, live state, and diff reports so teams can avoid surprise environment behavior while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The DevOps team used Rollback Config Drift Check when the error budget started burning, so the team could avoid surprise environment behavior before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) for "Rollback Infra Plan": Rollback Infra Plan is a devops change preview that shows expected infrastructure changes before apply for recovery from a bad deployment. It uses resource graphs, policy checks, and cost notes so teams can review platform changes safely while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The DevOps team used Rollback Infra Plan when the error budget started burning, so the team could review platform changes safely before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) for "Artifact Build Gate": Artifact Build Gate is a devops quality gate that blocks promotion when required checks fail for build output and package delivery. It uses tests, lint, security scans, and policy rules so teams can prevent broken releases while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The DevOps team used Artifact Build Gate when the container image was signed, so the team could prevent broken releases before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) for "Artifact Artifact Signature": Artifact Artifact Signature is a devops supply-chain record that proves that an artifact came from an expected build path for build output and package delivery. It uses cryptographic signatures, provenance, and verification so teams can trust deployed packages while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The DevOps team used Artifact Artifact Signature when the container image was signed, so the team could trust deployed packages before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) for "CI Incident Timeline": CI Incident Timeline is a devops response record that orders alerts, actions, and decisions during an incident for continuous integration workflows. It uses timestamps, owners, and evidence links so teams can learn from outages without guesswork while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The DevOps team used CI Incident Timeline when a pull request entered the build queue, so the team could learn from outages without guesswork before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) for "Rollback Secret Rotation": Rollback Secret Rotation is a devops credential workflow that replaces sensitive keys without service interruption for recovery from a bad deployment. It uses dual credentials, rollout steps, and revocation so teams can reduce credential exposure while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The DevOps team used Rollback Secret Rotation when the error budget started burning, so the team could reduce credential exposure before the deployment window opened.”