key/values not propogating into downstream tasks

[warroyo]

I am seeing that when i have 2+ tasks in a job the key values are not being passed to the next task. both tasks have inputs and outputs for the key/values

[regevbr]

@ezraroi can you please check your pipeline cf file and see how we handle this scenario?

[ezraroi]

It is working fine.. Example of a job:

[regevbr]

@ezraroi are you sure that changes in the first task propagate to the second task? I remember it does but can you see it in the ui?

[warroyo]

@ezraroi what does your task.yml file look like?

[ezraroi]

platform: linux

image_resource:
  type: docker-image
  source:
    repository: hub.docker.intel.com/swce-docker/pipeline-base

inputs:
  - name: tools
  - name: repo
  - name: keyval

outputs:
  - name: out
  - name: keyvalout

caches:
  - path: gradle
  - path: maven
  - path: npm

run:
  path: tools/tasks/task.sh

[ezraroi]

@regevbr we don not change values between steps...

[regevbr]

Bummer, i think that is why we have so many jobs cause i couldn't get the changes to pass between tasks...

[pk0024703]

is this resource working between jobs, has anyone been successful in getting it configured?