python持续集成_python有什么好用的持续集成工具么？

python的有比较强悍&＃xff0c;google等公司在用的构建框架buidbot。另外python也有jenkins API。

python相关的库参考下&＃xff1a;

buildbot - google等公司使用的持续集成框架&＃xff0c;上手比Jenkins难&＃xff0c;功能和性能远比Jenkins强大。 链接 python库介绍-buildbot教程

BitBake – 嵌入式Linux上类似make工具。链接

buildout – 用于从多个部分创建&＃xff0c;组装和部署应用程序的构建系统。链接

PlatformIO – 在不同的开发平台的控制台构建工具。链接

PyBuilder – 纯Python编写的持续构建工具。链接

SCons – 软件构建工具。链接

jenkinsapi – Hudson & Jenkins python API。链接

另外我个人觉得python一个强悍的地方在于很容易自行开发出构建工具&＃xff0c; 参见 china-testing/python-api-tesing以下python库在自行开发构建工具时比较常用。

DevOps工具(DevOps Tools)DevOps的软件和库。*

Ansible - 极其简单的IT自动化平台。 --推荐

Cloud-Init - 处理云实例的早期初始化的多分发包。

cuisine - 为 Fabric 提供一系列高级函数。

Fabric - 简单的Pythonic远程执行和部署工具。 --推荐

Fabtools - 编写真棒Fabric文件的工具。

nova - OpenStack计算。 --推荐

swift - OpenStack存储。 --推荐

pexpect - 在像GNU expect这样的伪终端中控制交互式程序。 --强烈推荐

psutil - 跨平台的进行和系统实用程序模块。 --推荐

SaltStack - 基础设施自动化和管理系统。 --推荐

supervisor - 用于UNIX的Supervisor进程控制系统。

gitapi&＃xff1a;Git 的纯 Python API。官网

hgapi&＃xff1a;Mercurial 的纯 Python API。官网

honcho&＃xff1a;Foreman 的 Python 克隆版&＃xff0c;用来管理基于 Procfile 的应用。官网

全栈 Web 框架。Django&＃xff1a;Python 界最流行的 web 框架。链接 wesome-django系列 链接 --强烈推荐

Flask&＃xff1a;Python 微型框架。链接 awesome-flask系列 链接 --强烈推荐 python web框架第一名

pyramid&＃xff1a;一个小巧&＃xff0c;快速&＃xff0c;接地气的开源Python web 框架。链接 awesome-pyramid系列 链接

Bottle&＃xff1a;一个快速小巧&＃xff0c;轻量级的 WSGI 微型 web 框架。链接 --推荐

CherryPy&＃xff1a;一个极简的 Python web 框架&＃xff0c;支持HTTP/1.1 协议且具有WSGI 线程池。链接

sanic&＃xff1a;python3 快速的web服务器&＃xff0c;类似flask。链接 --推荐

web.py&＃xff1a;既简单&＃xff0c;又强大的web 框架。链接

TurboGears&＃xff1a;易于扩展的全栈微框架。链接

web2py&＃xff1a;全栈 web 框架和平台&＃xff0c;用于安全数据库访问的web用。链接

Tornado - web 框架和异步网络库. 链接人工智能医药中医&＃xff1a;python库介绍-buildbot教程​zhuanlan.zhihu.com

Buildbot是python实现的开源持续构建和持续交付工具&＃xff0c;为Python, Mozilla, Chromium, WebKit等知名项目使用。

与Jenkins相比&＃xff0c;Buildbot在大陆使用者较少。原因在于Jenkins的界面相对较美观&＃xff0c;更容易上手&＃xff1b;Jenkins的中文文档比较丰富。但是Jenkins因为资源消耗庞大、不太方便定制而不受一些有实力的公司欢迎。这些不少把目光聚焦在Buildbot。

究竟Buildbot有哪些优点让这些公司青睐呢&＃xff1f;Buildbot基于python网络框架Twisted&＃xff0c;分布式做得好。Buildbot可以直接使用python包&＃xff0c;轻松拥有上万库&＃xff0c;具备强大的扩展能力。如果你觉得Jenkins已经轻松地满足你的需求&＃xff0c;你不需要Buildbot。如果你在Jenkins时觉得效率低下、扩展困难、一些用python等脚本可以实现的动作在Jenkins困难重重&＃xff0c;那么可以看看Buildbot。

Buildbot是开源的自动化软件构建&＃xff0c;测试&＃xff0c;发布流程的框架。

Buildbot支持跨平台&＃xff0c;分布式&＃xff0c;并行执行jobs&＃xff0c;与版本控制系统的灵活集成&＃xff0c;丰富的状态报告等等。

Buildbot是一个作业调度系统&＃xff1a;它会对作业进行排队&＃xff0c;在所需要的资源可用时执行任务&＃xff0c;并报告结果。

Buildbot有一个或多个主机和从机。主机监控源代码库的变化&＃xff0c;调配从机&＃xff0c;并给用户和开发者报告结果。从机可在多种操作系统上运行。

可以配置Python脚本到主机。这个脚本可以简单到只配置内置组件&＃xff0c;也可以充分发挥python所长&＃xff0c;可以动态生成的配置&＃xff0c;定制的组件及其他任何你能想到的。

该框架基于Twisted实现&＃xff0c;并与所有主要的操作系统兼容。

Buildbot支持持续集成&＃xff0c;持续部署&＃xff0c;发布管理等的。Buildbot支持持续集成测试&＃xff0c;自动化复杂的编译系统&＃xff0c;应用程序部署和复杂的软件发布流程管理。比CruiseControl或Jenkins更适合混合语言的环境。在 Chromium,WebKit, Firefox, Python和Twisted等有广泛的使用。

缺点&＃xff1a;buildbot对多项目支持并不好。参考资料&＃xff1a;

安装

目的

本教程从零开始&＃xff0c;尽可能快地运行您的第一个buildbot master和worker&＃xff0c;而不会更改默认配置。

本教程假设您正在运行Linux&＃xff0c;但可能适用于Windows。

准备

#!python

pip3 install buildbot

pip3 install buildbot-www

pip3 install buildbot-grid-view

pip3 install buildbot-console_view

pip3 install buildbot-worker

pip3 install setuptools-trial

创建master

#!python

$ buildbot create-master master

mkdir /opt/master

creating /opt/master/master.cfg.sample

creating database (sqlite:///state.sqlite)

buildmaster configured in /opt/master

$ mv master/master.cfg.sample master/master.cfg

$ buildbot start master

Following twistd.log until startup finished..

The buildmaster appears to have (re)started correctly.

日志在master/twistd.log

此时访问　http://localhost:8010/

创建worker

#!python

$ buildbot-worker create-worker worker localhost example-worker pass

mkdir /opt/worker

mkdir /opt/worker/info

Creating info/admin, you need to edit it appropriately.

Creating info/host, you need to edit it appropriately.

Not creating info/access_uri - add it if you wish

Please edit the files in /opt/worker/info appropriately.

worker configured in /opt/worker

$ buildbot-worker start worker

Following twistd.log until startup finished..

The buildbot-worker appears to have (re)started correctly.

日志在worker/twistd.log

快速入门

本章从china-testing拉取代码&＃xff0c;调用&＃xff50;&＃xff59;&＃xff54;&＃xff45;&＃xff53;&＃xff54;执行buildbot/hello-world/hello下的单元测试。

配置项目名和URL

#!python

$ vi master/master.cfg

# -*- python -*-

# ex: set filetype&＃61;python:

from buildbot.plugins import *

# This is a sample buildmaster config file. It must be installed as

# &＃39;master.cfg&＃39; in your buildmaster&＃39;s base directory.

# This is the dictionary that the buildmaster pays attention to. We also use

# a shorter alias to save typing.

c &＃61; BuildmasterConfig &＃61; {}

####### WORKERS

# The &＃39;workers&＃39; list defines the set of recognized workers. Each element is

# a Worker object, specifying a unique worker name and password. The same

# worker name and password must be configured on the worker.

c[&＃39;workers&＃39;] &＃61; [worker.Worker("example-worker", "pass")]

# &＃39;protocols&＃39; contains information about protocols which master will use for

# communicating with workers. You must define at least &＃39;port&＃39; option that workers

# could connect to your master with this protocol.

# &＃39;port&＃39; must match the value configured into the workers (with their

# --master option)

c[&＃39;protocols&＃39;] &＃61; {&＃39;pb&＃39;: {&＃39;port&＃39;: 9989}}

####### CHANGESOURCES

# the &＃39;change_source&＃39; setting tells the buildmaster how it should find out

# about source code changes. Here we point to the buildbot version of a python hello-world project.

c[&＃39;change_source&＃39;] &＃61; []

c[&＃39;change_source&＃39;].append(changes.GitPoller(

&＃39;git://github.com/china-testing/python-api-tesing.git&＃39;,

workdir&＃61;&＃39;gitpoller-workdir&＃39;, branch&＃61;&＃39;master&＃39;,

pollinterval&＃61;300))

####### SCHEDULERS

# Configure the Schedulers, which decide how to react to incoming changes. In this

# case, just kick off a &＃39;runtests&＃39; build

c[&＃39;schedulers&＃39;] &＃61; []

c[&＃39;schedulers&＃39;].append(schedulers.SingleBranchScheduler(

name&＃61;"all",

change_filter&＃61;util.ChangeFilter(branch&＃61;&＃39;master&＃39;),

treeStableTimer&＃61;None,

builderNames&＃61;["runtests"]))

c[&＃39;schedulers&＃39;].append(schedulers.ForceScheduler(

name&＃61;"force",

builderNames&＃61;["runtests"]))

####### BUILDERS

# The &＃39;builders&＃39; list defines the Builders, which tell Buildbot how to perform a build:

# what steps, and which workers can execute them. Note that any particular build will

# only take place on one worker.

factory &＃61; util.BuildFactory()

# check out the source

factory.addStep(steps.Git(repourl&＃61;&＃39;git://github.com/china-testing/python-api-tesing.git&＃39;, mode&＃61;&＃39;incremental&＃39;))

# run the tests (note that this will require that &＃39;trial&＃39; is installed)

factory.addStep(steps.ShellCommand(command&＃61;["pytest", "buildbot/hello-world/hello"]))

c[&＃39;builders&＃39;] &＃61; []

c[&＃39;builders&＃39;].append(

util.BuilderConfig(name&＃61;"runtests",

workernames&＃61;["example-worker"],

factory&＃61;factory))

####### BUILDBOT SERVICES

# &＃39;services&＃39; is a list of BuildbotService items like reporter targets. The

# status of each build will be pushed to these targets. buildbot/reporters/*.py

# has a variety to choose from, like IRC bots.

c[&＃39;services&＃39;] &＃61; []

####### PROJECT IDENTITY

# the &＃39;title&＃39; string will appear at the top of this buildbot installation&＃39;s

# home pages (linked to the &＃39;titleURL&＃39;).

c[&＃39;title&＃39;] &＃61; "Hello World CI"

c[&＃39;titleURL&＃39;] &＃61; "https://github.com/china-testing/python-api-tesing"

# the &＃39;buildbotURL&＃39; string should point to the location where the buildbot&＃39;s

# internal web server is visible. This typically uses the port number set in

# the &＃39;www&＃39; entry below, but with an externally-visible host name which the

# buildbot cannot figure out without some help.

c[&＃39;buildbotURL&＃39;] &＃61; "http://localhost:8010/"

# minimalistic config to activate new web UI

c[&＃39;www&＃39;] &＃61; dict(port&＃61;8010,

plugins&＃61;dict(waterfall_view&＃61;{}, console_view&＃61;{}, grid_view&＃61;{}))

####### DB URL

c[&＃39;db&＃39;] &＃61; {

# This specifies what database buildbot uses to store its state. You can leave

# this at its default for all but the largest installations.

&＃39;db_url&＃39; : "sqlite:///state.sqlite",

}

$ $ buildbot reconfig master

sending SIGHUP to process 4194

b&＃39;2018-01-24 15:13:07&＃43;0800 [-] beginning configuration update&＃39;

b"2018-01-24 15:13:07&＃43;0800 [-] Loading configuration from &＃39;/opt/master/master.cfg&＃39;"

b&＃39;2018-01-24 15:13:07&＃43;0800 [-] /usr/local/lib/python3.5/dist-packages/buildbot/config.py:102: buildbot.config.ConfigWarning: [0.9.0 and later] &＃96;buildbotNetUsageData&＃96; is not configured and defaults to basic.&＃39;

b&＃39;\tThis parameter helps the buildbot development team to understand the installation base.&＃39;

b&＃39;\tNo personal information is collected.&＃39;

b&＃39;\tOnly installation software version info and plugin usage is sent.&＃39;

b&＃39;\tYou can &＃96;opt-out&＃96; by setting this variable to None.&＃39;

b&＃39;\tOr &＃96;opt-in&＃96; for more information by setting it to "full".&＃39;

b&＃39;\t&＃39;

b"2018-01-24 15:13:07&＃43;0800 [-] gitpoller: using workdir &＃39;/opt/master/gitpoller-workdir&＃39;"

b"2018-01-24 15:13:08&＃43;0800 [-] initializing www plugin &＃39;waterfall_view&＃39;"

b"2018-01-24 15:13:08&＃43;0800 [-] initializing www plugin &＃39;console_view&＃39;"

b"2018-01-24 15:13:08&＃43;0800 [-] initializing www plugin &＃39;grid_view&＃39;"

b&＃39;2018-01-24 15:13:08&＃43;0800 [-] configuration update complete&＃39;

Reconfiguration appears to have completed successfully

首次构建

打开&＃xff1a;http://localhost:8010/#/builders

点击右上角的force&＃xff0c;表单可以什么都不填&＃xff0c;点击“Start Build”就会开始构建。

很快可以看到输出&＃xff1a;

#!python

SESSION&＃61;ubuntu

SESSIONTYPE&＃61;gnome-session

SESSION_MANAGER&＃61;local/andrew-MS-7A71:&＃64;/tmp/.ICE-unix/2824,unix/andrew-MS-7A71:/tmp/.ICE-unix/2824

SHELL&＃61;/bin/bash

SHLVL&＃61;1

SSH_AUTH_SOCK&＃61;/run/user/1000/keyring/ssh

TERM&＃61;xterm

TMDB_API_KEY&＃61;ee6623075bcc5519ef16be16e1f139e7

UPSTART_EVENTS&＃61;xsession started

UPSTART_INSTANCE&＃61;

UPSTART_JOB&＃61;unity7

UPSTART_SESSION&＃61;unix:abstract&＃61;/com/ubuntu/upstart-session/1000/2570

USER&＃61;andrew

XAUTHORITY&＃61;/home/andrew/.Xauthority

XDG_CONFIG_DIRS&＃61;/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg

XDG_CURRENT_DESKTOP&＃61;Unity

XDG_DATA_DIRS&＃61;/usr/share/ubuntu:/usr/share/gnome:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop

XDG_GREETER_DATA_DIR&＃61;/var/lib/lightdm-data/andrew

XDG_MENU_PREFIX&＃61;gnome-

XDG_RUNTIME_DIR&＃61;/run/user/1000

XDG_SEAT&＃61;seat0

XDG_SEAT_PATH&＃61;/org/freedesktop/DisplayManager/Seat0

XDG_SESSION_DESKTOP&＃61;ubuntu

XDG_SESSION_ID&＃61;c2

XDG_SESSION_PATH&＃61;/org/freedesktop/DisplayManager/Session0

XDG_SESSION_TYPE&＃61;x11

XDG_VTNR&＃61;7

XMODIFIERS&＃61;&＃64;im&＃61;fcitx

_&＃61;/usr/local/bin/buildbot-worker

using PTY: False

&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61; test session starts &＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;

platform linux2 -- Python 2.7.12, pytest-2.8.7, py-1.4.31, pluggy-0.3.1

rootdir: /opt/worker/runtests/build/buildbot/hello-world, inifile:

collected 2 items

buildbot/hello-world/hello/test_hello.py ..

&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61; 2 passed in 0.01 seconds &＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;&＃61;

program finished with exit code 0

elapsedTime&＃61;0.168047

欢迎 关注 点赞&＃xff0c;谢谢&＃xff01;

zhouaimei1​www.zhihu.com