我在插件页面有一个问题,但这似乎是Jenkins支持的更活跃的地方。
当对任何分支进行推送更改时,作业将运行并合并到develop分支中,但大约20秒后,作业将注意到合并到develop并再次触发作业。这不应该发生,因为develop在要构建的分支中(具有相反的选择策略)。当更改被推送到主分支或发布分支时,也会发生这种情况,这也应该被排除。如果存在合并失败,则作业将开始永远循环尝试合并分支,直到手动解决冲突。
我还尝试将特定用户从触发构建中排除,但也没有效果。
我开始认为Github插件不尊重选择策略或其他git插件选项。
希望下面的信息足以帮助我理解这个问题。
GitHub Plugin => 1.5
GitHub API Plugin => 1.40
GitHub Pull Request Builder => 1.7
GitHub Authentication Plugin => 0.13.1
Jenkins GIT Plugin => 1.3.0
Jenkins GIT client Plugin => 1.0.5
来自构建的有趣配置选项
要构建的分支
master,**master,release,**release,develop,**develop
排除用户
jenkins
ConvergintJenkins
合并选项
✓ Merge before build
Branch to merge to
develop
禁用子模块处理 ✓
选择策略
Inverse
构建触发器
✓ Build when a change is pushed to github
✓ Poll SCM
Git 投票日志
Polling has not run yet.
GitHub Hook 日志
Started on Apr 30, 2013 3:53:14 PM
Using strategy: Inverse
[poll] Last Built Revision: Revision bde1981da849dbfb2fd93aac4de05fd5a832043b (origin/ach)
Fetching changes from the remote Git repositories
Fetching upstream changes from origin
Polling for changes in
Seen branch in repository origin/develop
Seen branch in repository origin/feature-228
Seen branch in repository origin/feature-249
Seen branch in repository origin/master
Seen branch in repository origin/release
Done. Took 1.4 sec
Changes found