AYou're reviewing how a CI/CD pipeline handles credentials, tokens, and runtime configuration before promoting it to wider use. The goal is to avoid exposing sensitive values in source control, logs, or build agents while keeping deployments repeatable across environments.
How do you handle secrets management and environment variables securely within a Jenkins CI/CD pipeline?