Does CircleCI Docker executor preserve environment variables across re-queued jobs?
When utilizing the Docker executor in CircleCI, jobs are designed to run in isolated containers. A common requirement is the ability to maintain state or transient environment variables when a job is re-queued following a failure. Current documentation indicates that containers restart with a clean environment. While persist_to_workspace and save_cache are a
circleci