[英]many scheduled pooling and indexing of many jobs after doing notify Commit
I have many multi-branch pipelines in my Jenkins environment after setting the post-receive hook to trigger the corresponding Jenkins build it seems that the curl command scheduled pooling and indexing for all jobs using the same bitbucket repo
curl "https://myJenkins.com/git/notifyCommit?url=https://myGitServer.com/MyGitRepository.git"
我还想过执行 curl 命令来触发指定的作业，但这效率不高，因为这会导致每次提交都进行许多构建。 因为如果几乎同时推送两个提交，则可以在同一个构建中进行，因此无需触发另一个构建
有没有一种有效的方法来进行有针对性的扫描并只构建相应的管道和分支
每次提交后进行推送比多次提交后进行推送有什么好处和成本？
[英]What are the benefits and cost of doing push after each commit than push after many commits
在两个分支上已经完成许多提交后，如何将分支的特定提交推送到其他分支
[英]How to push specific commit of branch to other branch after many commits are already done on both branches
在git add和git commit之后，即使我只更改了4行，仍然有很多插入和删除
[英]after git add and git commit, so many insertions and deletions even though i only changed 4 lines
声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.