我希望这篇文章对您有所帮助:如何在Git提交上触发Jenkins构建

这只是使用curl使用Git提供的Git钩子触发Jenkins作业的问题。

命令curl http://localhost:8080/job/someJob/build?delay=0sec可以运行Jenkins作业，其中someJob是Jenkins作业的名称。

在隐藏的。git文件夹中搜索“hooks”文件夹。重命名“post-commit”。样本文件，以“后提交”。用记事本打开它，删除“:Nothing”行，并将上面的命令粘贴进去。

就是这样。无论何时执行提交，Git都会触发文件中定义的提交后命令。

与Jenkins的持续集成，在代码从Git命令/ GUI推送到存储库后:

Create a job in Jenkins with only job name and select type of the project freestyle. Click OK. The next page doesn't add anything - just click Save. Go to the your local Git repository where you have the source code and navigate to the .git/hooks folder. The hooks folder contains the few files. Check for the "post-commit". If not present, create a file, "post-commit" without a file extension: C:\work\test\\.git\hooks\post-commit Edit the "post-commit" file with the below command. Make sure it is present in your local source code hooks folder. curl -u userName:apiToken -X POST http://localhost:8080/jenkins/job/jobName/build?token=apiToken Example: curl -u admin:f1c55b3a07bb2b69b9dd549e96898384 -X POST http://localhost:8080/jenkins/job/Gitcommittest/build?token=f1c55b3a07bb2b69b9dd549e96898384 5. userName: Jenkins user name jobName: Job name of the build apiToken: To get your API token, go to your Jenkins user page (top right in the interface). It is available in the "Configure" menu on the left of the page: "Show API token" Make changes in your source code and commit the code to repository. Your job, http://localhost:8080/jenkins/job/Gitcommittest/, should be building.

我希望这篇文章对您有所帮助:如何在Git提交上触发Jenkins构建

这只是使用curl使用Git提供的Git钩子触发Jenkins作业的问题。

命令curl http://localhost:8080/job/someJob/build?delay=0sec可以运行Jenkins作业，其中someJob是Jenkins作业的名称。

在隐藏的。git文件夹中搜索“hooks”文件夹。重命名“post-commit”。样本文件，以“后提交”。用记事本打开它，删除“:Nothing”行，并将上面的命令粘贴进去。

就是这样。无论何时执行提交，Git都会触发文件中定义的提交后命令。

以上答案是正确的，但我是针对他们谁是新手这里的简单

特别是为管道设置构建触发器:

假设你有两个Github分支:主人,2.开发, 和Jenkinsfile(编写管道脚本的地方)以及其他文件在每个分支上都可用

配置新的Pipeline项目(用于开发分支)

# # 1。基于git-plugin和cron的代码集成方法 前提条件git插件应该安装和配置它与您的姓名和电子邮件

General section.Check checkbox - 'This project is parameterized’ and add Name-SBRANCH Default Value-'refs/remotes/origin/dev' Build triggers section" Check checkbox - 'Poll SCM' and schedule as per need for checking commits e.g. '*/1 * * * *' to check every minute Pipeline definition section.Select - Pipeline script from SCM—> select git—> addRepository URL—>add git credentials—> choose advanced—> add Name- origin, RefSpec- '+refs/heads/dev:refs/remotes/origin/dev'(dev is github branch )—> Branches to build - ${SBRANCH} (Parameter name from ref 1st point)—> Script Path—> Jenkinsfile —> Uncheck Lightweightcheckout Apply—> save

# # 2。代码集成:github-plugin和webhook方法 前提条件安装了Github插件，配置了Github服务器，如果不考虑下面的配置，需要测试连接

配置Github插件与帐户詹金斯

GitHub section Add Github server if not present API URL: https://api.github.com Credentials: Add secret text (Click add button: select type secret text) with value Personal Access Token (Generate it from your Github accounts—> settings—> developer setting—> personal access token—> add token—> check scopes—> copy the token) Test Connection—> Check whether it is connected to your Github account or not Check checkbox with Manage Hooks In advance sub-section just select previous credential for 'shared secret'

添加webhook，如果没有添加到您的存储库

去Github存储库设置- >添加webhook - >添加URL http://Public_IP:Jenkins_PORT/github-webhook/ 如果没有Public_IP，请使用ngrok。安装，认证，从命令./ngrok获取公共IP http 80(使用你的jenkins_port)，然后添加webhook - >添加URL http://Ngrok_IP/github-webhook/ 通过从webhook页面传递有效载荷来测试它，并检查是否获得200状态。

如果你有Github拉请求插件配置它也与发布的Jenkins URL。

General section.Check checkbox - 'Github project' add project URL -(github link ending with '.git/') General section.Check checkbox - 'This project is parameterized' and add Name-SBRANCH Default Value-'refs/remotes/origin/dev' Build triggers.section.Check checkbox - 'GitHub hook trigger for GITScm polling' Pipeline def'n section: Select - Pipeline script from SCM—> select git—> addRepository URL—> add git credentials—>choose advanced —>add Name- origin, RefSpec- '+refs/heads/dev:refs/remotes/origin/dev' (dev is github branch ) —> Branches to build - ${SBRANCH} (Parameter name from ref 1.st point)—> Script Path—> Jenkinsfile—> Uncheck Lightweightcheckout Apply—> save

我对本地git服务器的解决方案: 转到本地git服务器钩子目录，忽略现有的更新。示例并创建一个名为“update”的新文件，例如:

gituser@me:~/project.git/hooks$ pwd
/home/gituser/project.git/hooks
gituser@me:~/project.git/hooks$ cat update
#!/bin/sh
echo "XXX from  update file"
curl -u admin:11f778f9f2c4d1e237d60f479974e3dae9 -X POST http://localhost:8080/job/job4_pullsrc_buildcontainer/build?token=11f778f9f2c4d1e237d60f479974e3dae9

exit 0
gituser@me:~/project.git/hooks$ 

echo语句将显示在你的git推送结果下，令牌可以从你的jenkins作业配置中获取，浏览找到它。如果没有调用文件“update”，请尝试其他具有相同名称但没有扩展名为“sample”的文件。

这就是你所需要的

对于GitLab，使用以下步骤:

转到项目的设置→Web钩子 从Jenkins项目中输入“Build Now”URL作为推送事件URL: 例如http://server.com/jenkins/job/project_name/build?delay=0sec 单击“添加Web钩子”，然后测试钩子

然后，每当你提交到存储库时，web钩子就会被触发，并创建一个构建。确保在每次构建之前将Jenkins工作区设置为删除工作区，以便获得新代码的新副本。