Hi,

I have the PR builder and notifier installed and I am experiencing some 
inconsistent behavior.

The instructions say that the first pipeline created will build a revision 
map so that any new pipeline will pick up any changes in existing PR or new 
PR created.

What I am experiencing is that the pipelines that have the builder 
pluggable SCM, is triggering on PRs that have already been merged to our 
main branch or even ones that have been closed.  I was thinking that this 
was happening in the beginning to build the revision map but its been over 
a month since Ive had the plugin configured and its still triggering 
pipelines on PRs that are 3 months old and have been closed for a long time.
Another scenario is where the pipeline doesnt build and notify on open PR's.

Also another Issue I am seeing is the notifier is not consistently being 
placed on the PR to let the person know that the status.

Is there also an update on the plugins (PR builder and notifier) not 
grouping commits together and running on a single PR but on all PR's 
individually and consistently placing a notification on every PR?  Wasnt 
sure if this was still an issue as I saw closed 
here https://github.com/gocd/gocd/pull/939

GoCD Server version: 22.10
PR builder version: 1.4.0-RC4
PR status notifier version: 1.7.0-129

Having these 2 plugins work consistently are key to CD.

Just a note, we used to use AWS codebuild for CD before moving to GoCD and 
we had web hooks that would trigger on every Pull request created, updated 
and reopened.I am seeking the same behavior in GoCD.


Any help would be greatly appreciated.


[image: Screen Shot 2022-06-16 at 9.17.10 AM.png]



[image: Screen Shot 2022-06-16 at 9.12.57 AM.png]

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/go-cd/39279acb-afeb-407d-a6f0-0b1e4d921ae2n%40googlegroups.com.

Reply via email to