You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using this resource in our Concourse setup for pull requests on a very busy pipeline.
We have had issues that others have experienced, where some PRs get missed by the resource and never trigger a build, but recently, an even stranger thing started happening.
The resource will work for a while, perhaps 12 hours, and then suddenly stop working, i.e., no commits on any PR in the repo will get picked up during the check run. No amount of PR triggering (empty commits, amended commits w/ force push, minor changes, majors changes, etc.) seems to be able to cause it to resume working.
We have also tried replacing the resource with another, and then putting it back, or changing the name of the resource, and sometimes it works, but it takes more than an hour after such a change before it gets back into action, which is not an acceptable way of working through the problem. We have also tried clearing the resource cache and clearing the check history, but that does not appear to help.
Any idea why the resource would suddenly stop working? Is there a way to increase its verbosity, so we can see what's going on during a check and why it's not picking up new commits? Is there something in the worker or ATC logs that we can look for that would be an indication of the cause of the issue?
The text was updated successfully, but these errors were encountered:
On our Concourse installation at Gstack, that one is working fine. Could you give a try and provide feedback there?
(the new resource is a drop-in replacement; you only have to switch telia-ossto cfcommunity in in the resource_types: declaration, i.e. specify repository: cfcommunity/github-pr-resource)
We are using this resource in our Concourse setup for pull requests on a very busy pipeline.
We have had issues that others have experienced, where some PRs get missed by the resource and never trigger a build, but recently, an even stranger thing started happening.
The resource will work for a while, perhaps 12 hours, and then suddenly stop working, i.e., no commits on any PR in the repo will get picked up during the
check
run. No amount of PR triggering (empty commits, amended commits w/ force push, minor changes, majors changes, etc.) seems to be able to cause it to resume working.We have also tried replacing the resource with another, and then putting it back, or changing the name of the resource, and sometimes it works, but it takes more than an hour after such a change before it gets back into action, which is not an acceptable way of working through the problem. We have also tried clearing the resource cache and clearing the check history, but that does not appear to help.
Any idea why the resource would suddenly stop working? Is there a way to increase its verbosity, so we can see what's going on during a check and why it's not picking up new commits? Is there something in the worker or ATC logs that we can look for that would be an indication of the cause of the issue?
The text was updated successfully, but these errors were encountered: