-
Bug
-
Resolution: Fixed
-
Major
-
None
-
OS: 16.04.6 LTS 4.4.0-1081-aws
OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_212-b03)
OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.212-b03, mixed mode)
Jenkins ver. 2.150.2
GitHub plugin 1.29.4
GitHub Branch Source Plugin 2.5.1
Jenkins is accessed through reverse proxy (nginx via proxy_pass).OS: 16.04.6 LTS 4.4.0-1081-aws OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_212-b03) OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.212-b03, mixed mode) Jenkins ver. 2.150.2 GitHub plugin 1.29.4 GitHub Branch Source Plugin 2.5.1 Jenkins is accessed through reverse proxy (nginx via proxy_pass).
-
-
branch-api-plugin-2.6.0
Occasionally, a push to a branch triggers two builds on the corresponding branch in a multibranch pipeline. We are using the GitHub as branch source, and have added a organization wide GitHub webhook on push only. I am not sure about the relationship between the GitHub plugin and the GitHub branch source plugin.
On normal builds we see the following two lines:
Started by GitHub push by (author)
Push event to branch master at 9:31:27 AM on May 2, 2019
Each of the builds that are triggered twice has just one of the above lines, i.e.
Started by GitHub push by (author)
and
Push event to branch master at 9:31:27 AM on May 2, 2019
respectively.
Can anyone shed light on what these two lines mean?
The Jenkinsfile has this property:
properties([
pipelineTriggers([githubPush()]),
])
Removing it does not seem to have any noticable effect though.
- is related to
-
JENKINS-54610 Race condition when polling for changes triggered by web hook
- Resolved
-
JENKINS-54052 MultibranchProject ignores quietPeriod
- Closed