When using tag_filter, the version reported by 'in' should be the tag name about git-resource HOT 4 CLOSED

Hi there!

We use Pivotal Tracker to provide visibility into what our team is working on. A story for this issue has been automatically created.

The current status is as follows:

• #117431593 When using tag_filter, the version reported by 'in' should be the tag name

This comment, as well as the labels on the issue, will be automatically updated as the status in Tracker changes.

from git-resource.

Without this patch, a pipeline like this:

which is triggered by tags, will use the tag as input of the first job and then the hash. The git resource will report these versions:

Where first is a tag, that is input of the first job, and then a hash that is the input of the next jobs.

from git-resource.

I've also seen this, but only intermittently:

The configuration for this resource is:

- name: broker-release-final
  type: git
  source:
    uri: [email protected]:CLASSIFIED/TOP-SECRET.git
    branch: master
    private_key: {{private_key}}
    tag_filter: "v*"

from git-resource.

@tomwhoiscontrary Yeah, it matches with my issue description. That is because the hash is generated when the resource is consumed by a task by using the get action.

In our case we trigger the pipeline with that git resource, so every commit triggers a job which calls get. In your case you probably consume that git resource in jobs triggered by other criteria.

You can see which job generated the "hash" version by using it as input by clicking in the version:

You can see that in our case, that version "inputs to"...

from git-resource.