Repository navigation
Resource versions created with both SHA1 and tag, preventing tag_filter and tag_regex from working #353
Description
Activity
FWIW, I saw this with using
tag_filteras well.- name: mirrors_github_pinniped type: git icon: github tags: [ pinniped-ci-calatrava ] source: uri: git@gitlab.whatever.com:akeesler/fake-mirrors_github_pinniped.git # Workaround https://github.com/concourse/git-resource/issues/353. There seems to be an issue # with tag_regex, so use tag_filter as a workaround until the tag_regex goes away. Note that # this workaround will stop working once we release a v1 version upstream! tag_filter: v0.* # tag_regex: v[0-9]+\.[0-9]+\.[0-9]+ # e.g., v0.4.1 private_key: REDACTED
- changed the title
[-]Maybe a bug with tag_regex? Resource versions created with both SHA1 and tag[/-][+]Resource versions created with both SHA1 and tag, preventing tag_filter and tag_regex from working[/+]on Mar 9, 2021
What happened?
I see these resource versions:
Because of this, the next
vx.y.ztags that I pushed to the repo did not show up as a resource version because the latest resource version has arefof a SHA1 which filtered out all tags at this line:git-resource/assets/check
Line 161 in 30c1e23
What did I expect to happen?
refmatching mytag_regex.Notes