如何解决CircleCI上执行./gradlew assembleRelease时$TERM未设置问题？

Hey there, sorry to hear you're stuck on this TERM variable error during your Android assembleRelease step—let's get this sorted out for you.

First, let's break down why your initial fix might not have worked: if you set the TERM variable in a separate run command before calling Gradle, CircleCI runs each run step in a fresh shell session. That means the variable you set in one step doesn't carry over to the next one. Here are a few reliable solutions to try:

1. Set the TERM Variable Globally in Your Job #

The most straightforward fix is to define the TERM variable at the job level so it's available to every step in your Android build job. Add an environment block to your job config like this:

jobs:
  build-android:
    docker:
      - image: your-official-android-image  # The correct image you confirmed earlier
    environment:
      TERM: xterm-256color  # This makes the variable available to all steps
    steps:
      - checkout
      - run:
          name: Assemble Release Build
          command: ./gradlew assembleRelease

This ensures the TERM variable is present from the start of the job, so Gradle will pick it up without any extra steps.

2. Set and Use the Variable in the Same Run Step #

If you prefer not to set it globally, you can export the variable and run Gradle in the same shell session. This avoids the fresh shell issue mentioned earlier:

- run:
    name: Assemble Release Build
    command: export TERM=xterm && ./gradlew assembleRelease

Using && chains the commands together, so they run in the same shell—no more lost environment variables.

3. Verify Docker Image Environment (If Custom) #

If you're using a custom Docker image, double-check that it isn't clearing environment variables on startup. You could add ENV TERM xterm-256color directly to your Dockerfile to bake the variable into the image itself. This is a good long-term fix if you control the image.

One last thing to test: if you're still having issues, try running echo $TERM right before the Gradle command in the same step. That will confirm whether the variable is actually set when Gradle runs, which can help narrow down any remaining issues.

内容的提问来源于stack exchange，提问作者Brian Var