This job automatically created by CircleCI
Using build environment variables:
  BASH_ENV=/tmp/.bash_env-81c6858c-34eb-401c-9ec7-5ff325b7ce68-0-build
  CI=true
  CIRCLECI=true
  CIRCLE_BRANCH=main
  CIRCLE_BUILD_NUM=40
  CIRCLE_BUILD_URL=https://circleci.com/gh/alyvusal/circle-ci-test/40
  CIRCLE_JOB=destroy
  CIRCLE_NODE_INDEX=0
  CIRCLE_NODE_TOTAL=1
  CIRCLE_ORGANIZATION_ID=669e4830-3aa5-43f3-bbbf-a6146100c25a
  CIRCLE_PIPELINE_ID=fcc09f63-947f-448b-a423-dd5d7a3810db
  CIRCLE_PROJECT_ID=b6e8c429-b500-4847-8eb3-f3137d6035b7
  CIRCLE_PROJECT_REPONAME=circle-ci-test
  CIRCLE_PROJECT_USERNAME=alyvusal
  [email protected]:alyvusal/circle-ci-test.git
  CIRCLE_SHA1=a7fc50d316c563f021659fe4b6c5391398dde5e8
  CIRCLE_SHELL_ENV=/tmp/.bash_env-81c6858c-34eb-401c-9ec7-5ff325b7ce68-0-build
  CIRCLE_USERNAME=alyvusal
  CIRCLE_WORKFLOW_ID=d075b11d-e788-43d6-8726-fb07777e99a1
  CIRCLE_WORKFLOW_JOB_ID=81c6858c-34eb-401c-9ec7-5ff325b7ce68
  CIRCLE_WORKFLOW_WORKSPACE_ID=d075b11d-e788-43d6-8726-fb07777e99a1
  CIRCLE_WORKING_DIRECTORY=/root/project
Using environment variables from project settings and/or contexts:
  AWS_ACCESS_KEY_ID=**REDACTED**
  AWS_DEFAULT_REGION=**REDACTED**
  AWS_SECRET_ACCESS_KEY=**REDACTED**
  CIRCLE_OIDC_TOKEN=**REDACTED**
  CIRCLE_OIDC_TOKEN_V2=**REDACTED**
The redacted variables listed above will be masked in run step output.- Purpose: Reuse dependencies or build results across multiple workflow runs (i.e., across jobs and across pipelines).
 - Used For: Speeding up builds by avoiding re-downloading/installing dependencies (e.g., NPM packages, pip, Docker layers).
 - Stored Globally: Cache is shared between different workflow runs (with the same key).
 - You must manage cache keys to avoid stale data.
 
steps:
  - restore_cache:
      keys:
        - v1-dependencies-{{ checksum "package.json" }}
        - v1-dependencies-
  - run: npm install
  - save_cache:
      paths:
        - node_modules
      key: v1-dependencies-{{ checksum "package.json" }}- Purpose: Save output files (e.g., logs, binaries, test results) for external access after the job completes.
 - Used For: Making logs, test reports, screenshots, etc., available in the CircleCI web UI.
 - Scope: Job-level, but accessible after the job finishes in the CircleCI UI or via API.
 - Not shared between jobs.
 
steps:
  - run: mkdir -p test-results
  - run: echo "some logs" > test-results/log.txt
  - store_artifacts:
      path: test-results- Purpose: Share data between jobs in the same workflow.
 - Used For: Passing data (e.g., compiled code, test assets) from one job - to another within a single workflow.
 - Faster than artifacts, and meant for internal job-to-job communication - only.
 - Must use both 
persist_to_workspaceandattach_workspace. 
# First job
job1:
  docker:
    - image: cimg/node:20.0
  steps:
    - run: mkdir -p output && echo "data" > output/file.txt
    - persist_to_workspace:
        root: output
        paths:
          - file.txt
# Second job
job2:
  docker:
    - image: cimg/node:20.0
  steps:
    - attach_workspace:
        at: /workspace
    - run: cat /workspace/file.txt