[JIRA] (JENKINS-43290) PollSCM doesn't update the latest hash, so when running "Scan Repository"/"Branch Indexing" it repeats builds

[chai.ba...@gmail.com (JIRA)]

Title: Message Title

Chaitanya Bapat commented on JENKINS-43290   Re: PollSCM doesn't update the latest hash, so when running "Scan Repository"/"Branch Indexing" it repeats builds Hey Stephen since https://issues.jenkins-ci.org/browse/JENKINS-41072 hasn't been resolved yet. How else do you suggest can I use AWS Services for communication between Github and Jenkins? I have AWS Lambda function that GitHub WebHook points to. I filter Github events and only if specified comment is made on a PR, I want to trigger a build on Jenkins. However, after disabling the <jenkins-server>/github-webhook from Github, Jenkins doesn't discover new PR branches and as a result I have to manually scan the repo everytime for a new PR so as to be able to use the Lambda function to trigger a job (job fails if the branch isn't discovered). How else can I use Lambda function to trigger branch discovery on Jenkins? or how else should I solve the problem of triggering build on Jenkins based on AWS Lambda function? Add Comment   This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180420.1491209494000.2445.1583649840311%40Atlassian.JIRA.