A project with Jenkins integration has selected option: Build when a change is pushed to BitBucket. Everything works as expected until some other branch is merged to master. In this case Jenkins triggers two builds. Has anyone experienced this issue?
相关问题
- Jenkins - cmd is not recognized
- When using Nokogiri, how do you suppress the inser
- Where Jenkins stores plugin configuration
- Multi-branch configuration with externally-defined
- X-I.: command not found, and failed to build certa
相关文章
- dotnet restore还原nuget包时无法加载 https://api.nuget.org/
- jenkins在window集群环境中如何部署自动化发布?
- jenkins + Publish over FTP 自动部署前端React项目
- jenkins自定打包部署React前端项目遇到的问题。
- Handling ffmpeg library interface change when upgr
- Best way to manage docker containers with supervis
- Access BitBucket payload data in Jenkins pipeline
- Build errors of missing packages in Visual Studio
I have experienced the same issue only for master branch, like you. The solution that worked was to update
Build Triggers
configuration of the job that was triggered twice by leavingPoll SCM -> Schedule
text box empty (no Cron expression entered). So the proper configuration is to only mark the two trigger options:[✓]
Build when a change is pushed to BitBucket[✓]
Poll SCM (leave the Schedule text box empty)In case Jenkins Job DSL plugin is used for generating the build job, it should contain proper
triggers
block (which corresponds to the above screen):