Plugin not working - no errors - how do i debug?

[arenstar]

im using Go Version: 16.12.0 and gocd-build-github-pull-requests version v1.3.0-RC2 ( stash-pr-poller-1.3.0-RC2.jar )

Plugin is available in go/admin/plugins -> ( Stash Pull Requests Builder 1.3.0-RC2 [stash.pr] ) I set up a new pipeline, creating a material using the Stash plugin it is a private registry - yet i have already setup a .netrc file i save the pipeline.. It builds the first time

I create new branches and pull requests - expecting something to happen.. ... nothing :(

the log is empty.. /var/log/go-server/plugin-stash.pr.log

This is a very easy configuration - am i missing something? I suspect there are larger issues at play here

[ashwanthkumar]

@arenstar Sorry for responding late. Are you still facing this issue? Is there a way you can check the gocd-server.log, during the same time and share any relevant stack traces or errors?

[dzschille]

i jump in because i have exactly the same issue. I use Go Version: 18.3.0 and stash-pr-poller-1.3.4.jar. It makes a first build after saving the new stash material. Thank nothing ever happens. I tried creating new PR and new commits to existing PR. But no reaction, also in the logs no activity is showing up. I am watching this logs:

tail -f /var/log/go-server/go-server.log /var/log/go-server/plugin-stash.pr.log /var/log/go-server/plugin-stash.pr.status.log /var/log/go-server/web-requests.log /var/lib/go-agent/logs/go-agent.log /var/lib/go-agent/logs/plugin-stash.pr.log

When i manually trigger the pipeline i see in the GoCD console output that GO_SCM_BITBUCKET_PR_LABEL is an commit id that isn't the latest commit in any of our branches or PR. How does it come that it is always checking out an older commit?

I have already deleted /var/lib/go-server/pipelines/flyweight.

[dzschille]

Is it possible that this behavior has to do with #71? I think it's possible because the older commit it is always building is a merge commit into master.