Firgerprinting and status on partent task

[madpipeline]

tasks:
  build-all:
    deps: [find-services]
    vars:
      SERVICES:
        sh: cat services.txt | tr '\n' ' '
    cmds:
      - for: { var: SERVICES, as: SERVICE }
        task: build-service
        vars:
          SERVICE_NAME: "{{.SERVICE}}"

  find-services: # Generates the services.txt

    build-service:
    requires:
      vars:
        - SERVICE_NAME
    sources:
      - "foo-{{.SERVICE_NAME}}/src/**/*"
    generates:
      - "foo-{{.SERVICE_NAME}}/target/{{.SERVICE_NAME}}-*.jar"
    cmds:
      - task: build-maven
        vars:
          PROJECT_DIR: "foo-{{.SERVICE_NAME}}"
          SERVICE_NAME: "{{.SERVICE_NAME}}"

  build-maven: # builds the app within a docker container

$ task build-service SERVICE_NAME=crazy-dog-service
task: Task "build-service" is up to date

$ task build-service SERVICE_NAME=happy-lizzard-service
task: Task "build-service" is up to date

$ task --status=true build-all
task: Task "build-all" is not up-to-date

When running the build-service task for each service individually, the fingerprinting is done and recognized, but when running the build-service task via the build-all task, fingerprinting is not recognized and the build happens every time for all services.

How should I define my tasks so that when the build-all task runs the other sub-tasks they report back that they are up to date, just like they already do when I call them directly?

[Expand] Rant on having to debug to find out why fingerprinting check fails

I've debugged task so many times to understand why fingerprinting fails, that I grew tired of doing that again. Here's a list of issues I've had:

• Calling ExpandFiles on a path with spaces breaks fingerprinting #2321
• cannot use paths outside of the workspace because https://github.com/go-task/task/blob/main/internal/fingerprint/glob.go#L27
• wrong filename name in the "generates" block
• other mistakes I've done

It would be great if the fingerprinting check failure would print some message as to why this fails. Perhaps a different discussion for this.

[trulede]

This will help you I think:
https://taskfile.dev/usage/#by-fingerprinting-locally-generated-files-and-their-sources

Each task has only one checksum stored for its sources. If you want to distinguish a task by any of its input variables, you can add those variables as part of the task's label, and it will be considered a different task.

This is useful if you want to run a task once for each distinct set of inputs until the sources actually change. For example, if the sources depend on the value of a variable, or you if you want the task to rerun if some arguments change even if the source has not.

[madpipeline]

I see. I solved this by adding label: "build-maven-{{.PROJECT_DIR}}" to the build-maven task.

Thank you @trulede.