Replies: 1 comment 5 replies
-
You found the main problem with global resources! You are correct in that this only works because the git resource "ignores" any keys it doesn't know about. Your workaround works so hooray! That said, this might be an issue with how your pipeline is designed. You may want to think more about what it is you do or do not want triggering your pipeline. Maybe you don't actually want commits from this repo triggering this pipeline's jobs? |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I recently ran into an issue where I had a Git resource with
check_every: never
that was checking regularly.I found out that this was due to the fact that I had global resources enabled, and so another resource with the same
source
was triggering new versions of this one.To workaround this issue, I added a "dummy" parameter to the source, so that they were no longer treated as the same:
This works fine in this case, but it also depends on the way that the Git resource validates the
source
object, since in principle it could reject this invalid key.I was wondering if it made sense to add this key to the top-level resource configuration to say "don't share me with other resources"?
I don't want to disable global resource checking, as I think it's useful in other places, so it'd be nice to have a standardised way of handling this case.
Beta Was this translation helpful? Give feedback.
All reactions