[JIRA] (JENKINS-55850) How to rebuild on PR source branch change?
Title: Message Title Liam Newman closed an issue as Not A Defect Jenkins / JENKINS-55850 How to rebuild on PR source branch change? Change By: Liam Newman Status: Open Closed Resolution: Not A Defect 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.197247.1548799352000.22366.1588721520629%40Atlassian.JIRA.
[JIRA] (JENKINS-55850) How to rebuild on PR source branch change?
Title: Message Title Liam Newman commented on JENKINS-55850 Re: How to rebuild on PR source branch change? You either need to poll for changes or make sure you have webhooks configured correctly. 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.197247.1548799352000.22364.1588721460221%40Atlassian.JIRA.
[JIRA] (JENKINS-55850) How to rebuild on PR source branch change?
Title: Message Title Andrew Goldis created an issue Jenkins / JENKINS-55850 How to rebuild on PR source branch change? Issue Type: Bug Assignee: Unassigned Components: github-branch-source-plugin Created: 2019-01-29 22:02 Environment: Linux Debian - 8.11 Jenkins 2.161 org.jenkins-ci.plugins:github-branch-source:2.4.2 Labels: user-experience Priority: Minor Reporter: Andrew Goldis It is a question. When I create a PR on Github, I can see that a new build is triggered correctly. However, when I push a new commit to the source branch of the PR, it does not generate a new build. The configuration used for Branch Sources: Discover branches: exclude branches that are also filled as PRs Discover PRs: The current pull request revision What should be the right configuration to trigger rebuilds when either branch or a PR is changed?
