-
Notifications
You must be signed in to change notification settings - Fork 288
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make resource aware of new release tags #144
Comments
We are making an uber issue for this. We have a lot of requests for tags, which doesn't work in the current flow of a git resource that watches a specific tree. I'd like to post the wants there, for now. |
@gdenn Did you find any good way to workaround the lack of that feature? I would be interested to learn about it as I'm dealing with the same problem. |
@prein I am currently working with the Github Release Resource https://github.com/concourse/github-release-resource. With this resource you can trigger upon latest Release version of the repo and receive the code as a tarball. You just have to extract the tarball and your ready to go. To have this feature in the git-resource would be very nice nevertheless. |
linked to #223 |
Feature Request
I am currently working on a pipeline that uses Concourse to update Cloud Foundry releases.
Each release has an official repository e.g. uaa https://github.com/cloudfoundry/uaa-release . When a new release is created they always tag it on github with a version name e.g.
v1.2.3
.My pipeline shall recognise new release versions by triggering the release update job when a new tag is created on the repository.
If i am not mistaken the current implementation of the git-resource only recognises changes on the commit head version. As git tags are not specific to a branch or change the head version of a branch at all, new tags can't be used to trigger jobs.
As a concourse user i would like to have a additional option/flag watch_tags which trigger jobs attached to the git-resource only if new tags are created on the git repository.
The text was updated successfully, but these errors were encountered: