Jenkins目前是手动进行项目构建的，如何才能做到Github并持续集成呢？
配置前要求：
1.Jenkins已经安装Github插件
2.Jenkins服务器已经拥有一个公网IP地址
第一步：配置Jenkins全局
尽管Jenkins已经配置与Github代码库进行通信，但我们需从Jenkins手动启动构建，如需启动自动构建，Jenkins需要在Hook URL中监听Github的Post请求，才会进行自动构建
要获取Jenkins的Hook URL，打开Jenkins首页控制台--》系统管理
在Github插件的配置中，点击“高级”按钮
启用Hook URL，并将Hook URL复制出来，并保存刚才的设置
第二步：配置Github项目仓库
还需要配置Github项目仓库，因为Github经常有代码处理动作，需要配置Github项目仓库在处理这些动作的同时会发送信号至Jenkins，才使用Jenkins自动构建
在"Webhooks"选项卡中，点击"Add webhook"
将在Jenkins生成的Hook URL填入至Payload URL中，另外，选择自主事件
以Push为例，并保存，即当Github收到了客户端有Push动作时，会触发一个Hook
保存WebHook之后
第三步：配置Jenkins项目
最后需要配置Jenkins项目触发的条件，到此刻，Github遇到Push事件时，Jenkins会收到通知，但Jenkins应该做什么呢？此步骤就是做最后的构建的动作。
选择构建触发器，并且选择Github Hook触发
第四步，在本地代码库做一些修改，并Push至Github后，查看Jenkins构建效果
本例虽然第三次构建出现错误，但Github Hook的路是通的
参考地址：//configuring-jenkins-to-run-a-build-automatically-on-code-push/
Youtube:/watch?v=ke3f3rcRSc8
阅读(...) 评论()原创作品，允许转载，转载时请务必以超链接形式标明文章 原始出处 、作者信息和本声明。否则将追究法律责任。http://dgd2/1735106
前文讲述了《通过Git WebHooks+脚本实现自动更新发布代码》，里面提供了一种自动更新发布代码的脚本编写思路。
前文讲述了《》，里面提供了一种自动更新发布代码的脚本编写思路。本文的脚本与前文中的思路（前文思路的实现请参考《》）不太不同。本脚本以中的一些思想和理念为依据，用简单好理解的shell脚本实现capistrano原本实现的自动化部署部分。
脚本的一些特点和功能：
解决脚本的符号链接问题，准确获取脚本工作目录（从tomcat脚本中学到）；
颜色显示，不同级别的信息用不同的颜色显示（共两种方案，前一种从一位不知名的国外工程师处得到，后一种从lnmp1.2脚本中得到）；
生成capistrano目录结构；
清除过期目录和文件；
检查部署要求是否满足，如磁盘空间的需求等，其他的要求检查有待于添加；
部署失败后归滚；
项目废弃后删除项目；
脚本里面尽可能的考虑容错（异常判断）和部分细节；
脚本存在的已知的问题：
（1）脚本中有几个TODO，有待于改善；
（2）repository目录暂时没有用到；
（3）获取git的版本号问题；
（4）部署后生成的日志有待于优化；
（5）脚本基本使用英文（Chinglish）作为注释，部分注释可能不全；
（6）可能存在的其他问题；
为了后期的改进和部分需求变更，也为了便于获取该脚本，此脚本可以从github上获取，欢迎和接受提交任何bug、issue以及任何improvement。
github地址是：
脚本内容如下：
#!/bin/bash
while [ -h "$PRG" ]; do
ls=`ls -ld "$PRG"`
link=`expr "$ls" : '.*-& \(.*\)$'`
if expr "$link" : '/.*' & /dev/null; then
PRG="$link"
PRG=`dirname "$PRG"`/"$link"
PRGDIR=`dirname "$PRG"`
function cecho {
while [ "$1" ]; do
case "$1" in
color="\033[00m" ;;
color="\033[31;01m" ;;
color="\033[32;01m" ;;
color="\033[33;01m" ;;
color="\033[34;01m" ;;
color="\033[37;01m" ;;
one_line=1;
shift ; continue ;;
echo -n "$1"; shift ; continue ;;
echo -en "$color"
echo -en "$1"
echo -en "\033[00m"
if [ ! $one_line ]; then
function echo_r () {
echo -e "\033[31m$1\033[0m"
function echo_g () {
echo -e "\033[32m$1\033[0m"
function echo_y () {
echo -e "\033[33m$1\033[0m"
function echo_b () {\
echo -e "\033[34m$1\033[0m"
WORKDIR=$PRGDIR
SOURCEURL=https://github.com/DingGuodong/GitOSCAutoDeploy.git
save_old_releases_for_days=10
function setDirectoryStructure() {
if [ -f $WORKDIR/.lock ];then
echo_g "Set directory structure has been done, skipping. "
echo_b "Setting directory structure."
[ ! -d $WORKDIR/release ] && mkdir $WORKDIR/release
[ ! -d $WORKDIR/repository ] && mkdir $WORKDIR/repository
[ ! -d $WORKDIR/share ] && mkdir $WORKDIR/share
touch $WORKDIR/.lock
echo_g "Set directory structure successfully! "
function checkDependencies() {
echo_b "Checking dependencies for deploy procedure. "
if [[ -z $SOURCEURL ]]; then
echo_r "Error: SOURCEURL is undefined! "
DISKSPACE=`df $WORKDIR | tail -n1 | awk '{print $(NF -2)}'`
if [[ $DISKSPACE -lt 2097152 ]]; then
echo_y "Warning: Disk space of $WORKDIR is smaller than 2GB"
echo_g "All required dependencies check pass! "
function cleanOldReleases(){
save_days=${save_old_releases_for_days:-10}
if [ ! -d $WORKDIR/release ]; then
echo_b "Can NOT find release directory, skipping . "
need_clean=$(find $WORKDIR/release -mtime +$save_days -exec ls {} \;)
if [ ! -z $need_clean ]; then
echo_g "Expired releases found and will be removed from project! "
find $WORKDIR/release -mtime +$save_days -exec rm -rf {} \;
if [ $? -eq 0 ]; then
echo_g "Expired releases have removed from project! "
echo_r "Can NOT remove expired releases, please alter to Admin users. "
echo_g "All releases are not expired, skipping. "
function deploy() {
if [[ ! -f $WORKDIR/.lock ]]; then
setDirectoryStructure
cleanOldReleases
checkDependencies
SOURCEDIR="$WORKDIR/release/$(date +%Y%m%d%H%M%S)"
[ ! -d $SOURCEDIR ] && mkdir $SOURCEDIR
git clone $SOURCEURL $SOURCEDIR
[ -d $SOURCEDIR/.git ] && rm -rf $SOURCEDIR/.git
[ -d $SOURCEDIR/.svn ] && rm -rf $SOURCEDIR/.svn
( [ -f $WORKDIR/current ] || [ -d $WORKDIR/current ] ) && rm -rf $WORKDIR/current
ln -s $SOURCEDIR $WORKDIR/current
[ -d $WORKDIR/release/conf ] && mv $WORKDIR/release/conf $WORKDIR/share/conf
[ -d $WORKDIR/release/logs ] && mv $WORKDIR/release/logs $WORKDIR/share/logs
[ -d $WORKDIR/share/conf ] && ln -s $WORKDIR/share/conf $WORKDIR/current/conf
[ -d $WORKDIR/share/logs ] && ln -s $WORKDIR/share/logs $WORKDIR/current/logs
if [[ -e $WORKDIR/current/bin/startup.sh ]]; then
$WORKDIR/current/bin/startup.sh start
if [[ $RETVAL -eq 0 ]]; then
cat &$WORKDIR/share/workable_program.log &&eof
$SOURCEDIR
echo_g "Deploy successfully! "
echo_g "current workable version is $(cat $WORKDIR/share/workable_program.log)"
ls --color=auto -l $WORKDIR/current
echo_r "Error: Deploy failed! "
$0 rollback
function rollback() {
WORKABLE_PROGRAM=`cat $WORKDIR/share/workable_program.log`
if [[ -z WORKABLE_PROGRAM ]]; then
echo_r "Error: Can NOT find workable release version! Please check if it is first deployment! "
if [[ -e $WORKDIR/current/bin/startup.sh ]]; then
$WORKDIR/current/bin/startup.sh stop
rm -rf $WORKDIR/current
ln -s $WORKABLE_PROGRAM $WORKDIR/current
[ -d $WORKDIR/share/conf ] && ln -s $WORKDIR/share/conf $WORKDIR/current
[ -d $WORKDIR/share/logs ] && ln -s $WORKDIR/share/logs $WORKDIR/current
if [[ -e $WORKDIR/current/bin/startup.sh ]]; then
$WORKDIR/current/bin/startup.sh start
if [[ $RETVAL -eq 0 ]]; then
echo_g "Rollback successfully! "
echo_g "current workable version is $WORKABLE_PROGRAM"
ls --color=auto -l $WORKDIR/current
function destroy() {
echo_y "Warning: This action will destroy all this project, and this is unrecoverable! "
answer="n"
echo_y "Do you want to destroy this project? "
read -p "(Default no,if you want please input: y ,if not please press the enter button):" answer
case "$answer" in
y|Y|Yes|YES|yes|yES|yEs|YeS|yeS )
find -L $WORKDIR -maxdepth 1 ! -name "$(basename $0)" ! -wholename "$WORKDIR"
-exec rm -rf {} \;
if [ $? -eq 0 ];then
echo_g "Destory this project successfully! Now will exit with status 0. "
echo_r "Error: something go wrong! Please check or alter to Admin user! "
n|N|No|NO|no|nO)
echo_g "destroy action is cancel"
echo_r "Are you kidding me? You are a bad kid! "
case $1 in
echo "Usage: $0 {deploy|rollback|destroy} with $0 itself"
tag:自动化部署脚本,Shell部署脚本,capistrano的shell脚本实现,脚本实现自动更新和回滚,自动化部署shell脚本实例
本文出自 “” 博客，请务必保留此出处
如果您发现本社区中有涉嫌抄袭的内容，欢迎发送邮件至：yqgroup@ 进行举报，并提供相关证据，一经查实，本社区将立刻删除涉嫌侵权内容。
用云栖社区APP，舒服~
【云栖快讯】首届阿里巴巴中间件技术峰会，揭秘阿里10年分布式技术沉淀！阿里高可用体系核心缔造者、全链路压测创始人，DRDS与TDDL负责人等大咖出场，干货分享，不可错过！&&
业内领先的面向企业的一站式研发提效平台，通过项目流程管理和专项自动化提效工具，能够很好地支持互联网敏捷项目的快速...
基于云安全大数据能力实现，通过防御SQL注入、XSS跨站脚本、常见Web服务器插件漏洞、木马上传、非授权核心资源...
基于阿里聚安全的核心技术，为移动应用（APP）提供全生命周期的安全服务，其能够准确发现应用的安全漏洞，恶意代码，...
为您提供简单高效、处理能力可弹性伸缩的计算服务，帮助您快速构建更稳定、安全的应用，提升运维效率，降低 IT 成本...
2017杭州云栖大会火热抢票
Loading...Jenkins+Github持续集成 - 简书
Jenkins+Github持续集成
由于最近团队代码库从coding迁移到github，在CI工具的选型上尝试了和，最后决定自己搭建CI服务器，而我也有幸认领了这个任务的调研，因此有了这篇文章。
之前写过一篇文章，那真的是浅谈，Jenkins包含的东西实在太多了，作为从hudson分支出来的开源免费的版本，插件与hudson通用，有更快的迭代速度和稳定性。
为什么选择Jenkins
答案简单：因为免费，学习资料多。
安装配置这里就不赘述了，移步
因为要与Github通信，所以需要准备一台服务器，该服务器能访问到Github，Github能访问到它。为了这个测试，我特地在买了服务器，顺便介绍一下这个高性价比的vps供应商，$2.99约合人民币18元每个月，可一键搭建shadowsocks。但是记得有个坑就是购买的时候一定要选好机房，之前买过洛杉矶的卡的要死，打条命令之后要等好久才显示，对它失去信心不想用它了，后来听一个朋友说亚利桑那州（Arizona）的机房挺稳定的，再给它一次机会，这次买了Arizona机房的果然速度挺快的?
直接安装Github Plugin, jenkins会自动帮你解决其他插件的依赖，直接安装该插件Jenkins会自动帮你安装 、 、
安装GitHub plugin.png
2. 配置Github插件
系统管理 && 系统设置 && GitHub Plugin Configuration
首先点击到github上也就是github上用户Settings && personal access tokens
勾选给Jenkins的访问权限，Github plugin的帮助信息里说要admin:repo_hook、repo和repo:status权限，其实repo:status是包含在repo里的，详见。 点击Generate token创建一个token
复制这个token，回到Jenkins点击Add按钮
选择Secret text，粘贴token，添加描述，点击添加。点击Verify credentials测试token，显示Credentials verified for user xxx, rate limit: xxxx，说明配置完成了，这样你的Jenkins就具有访问你的github的权限了。
3. 创建一个freestyle任务
填写GitHub project URL???, 也就是你的项目主页eg.
配置源码管理
填写项目的git地址, eg.
添加github用户和密码
选择githubweb源码库浏览器，并填上你的项目URL，这样每次构建都会生成对应的changes，可直接链到github上看变更详情
构建触发器勾选Build when a change is pushed to GitHub，这样该仓库的每一次push或者pull request都会触发build
配置构建步骤随后配置构建环境、构建步骤和构建后步骤安装了Github Plugin之后在构建步骤和构建后操作会多两个设置，用于在构建时和构建后同步构建状态到Github的，后面有效果图
4. 配置Github仓库的Webhook
仓库的创建人在仓库的Settings && Webhooos & services添加我们只需要push事件触发就可以了，选中Just the push event点击Add webhookyes，与github集成的Jenkins CI环境就配置好了
每次push都会触发一次build，pull request的话还会在该界面直接显示build结果
整个环境终于搭好了，中间遇到了蛮多大坑小坑的，有些记录了下来，后续整理好再发上来。这段时间学习Jenkins收获蛮多的，只是到现在也只学了些皮毛，写出来的东西也颇有些晦涩。接下来要做的实验是通过Jenkins实现自动远程部署。Setting up a GitHub webhook in Jenkins
This post will detail the steps to have Jenkins automatically create a build if it detects changes to
a GitHub repository.
This can be a very useful improvement to your continuous integration setup with Jenkins because this method is only telling Jenkins to attempt a new build when a change is detected rather than polling on an interval, which can be a little bit inefficient.
There are a few steps necessary to get this process working correctly that I would like to highlight in case I have to do this again or if anybody else would like to set this up.
Most of the guides that I found were very out of date so their instructions were a little bit unclear and misleading.
The first step is to configure Jenkins to talk to GitHub.
You will need to download and install the GitHub plugin (I am using version 1.8 as of this writing).
Manage Jenkins -& Manage Plugins -& Available -& GitHub plugin
After this is installed you can either create a new build or configure an existing build job.
Since I already have one set up I will just modify it to use the GitHub hook.
There are a few things that need to be changed.
First, you will need to add your github repo:
Then you will then have to tick the box indicated below – “Build when a change is pushed to GitHub”
Also note that Jenkins should have an SSH key already associated with the desired GitHub project.
You’re pretty close to being done.
The final step is to head over to GitHub and adjust the settings for the project by creating a webhook for your Jenkins server.
Select the repo you’re interested in and click Settings.
If you aren’t an admin of the repo you will not be able to modify the settings, so talk to an owner to either finish this step for you or have them grant you admin to make the change yourself.
The GitHub steps are pretty straight forward.
Open the “Webhooks & Services” tab -& choose “Configure Services” -& find the Jenkins (GitHub plugin option) and fill it in with a similar URL to the following:
http://&Name of Jenkins server&:8080/github-webhook/
Make sure to tick the active box and ensure it works by running the “Test Hook”.
If it comes back with a payload deployed message you should be good to go.
I found an issue that was causing us issues.
There is a check box near the bottom of the authentication section labeled “Prevent Cross Site Request Forgery exploits” that needs to be unchecked in order for this particular method to work.
Let me know if you have any issues, I haven’t found a good way to debug or test outside of the message returned from the GitHub configuration page.
I did find another alternative method that may work but didn’t need to use it so I can update this if necessary.
If you want more details about web hooks you can check out these resources:
You can also check out the GitHub Jenkins plugin .
And another .
Related Posts
Liked it? Support me on Patreon
Josh is the creator of this blog, a system administrator and a contributor to other technology communities such as
You can also find him on
Get Connected
Popular Posts
Recent Posts
Select Month
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
April 2016
March 2016
February 2016
January 2016
December 2015
October 2015
September 2015
August 2015
April 2015
March 2015
February 2015
December 2014
November 2014
October 2014
September 2014
August 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
April 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011