- android - RelativeLayout 背景可绘制重叠内容
- android - 如何链接 cpufeatures lib 以获取 native android 库?
- java - OnItemClickListener 不起作用,但 OnLongItemClickListener 在自定义 ListView 中起作用
- java - Android 文件转字符串
我正在尝试从我计算机上的 docker-compose 文件运行 Buildbot,使用 Buildbot 提供的 buildmaster 和 worker 的图像。我将buildmaster端口定义为9989,并且在我的master.cfg中我定义了一个监听9989端口的PBChangeSource。但是,似乎在我运行docker-compose up
之后,没有进程监听在端口 9989(运行 lsof -nP -iTCP:9989 | grep LISTEN
之后)。这似乎得到了以下事实的进一步支持:当我运行 buildbot sendchange -m my.0.0.ip:9989 -a Jimmy:secret -W buildbot
时,扭曲的服务器超时,就像它一样如果我使用不同的端口运行相同的命令,例如buildbot sendchange -m my.0.0.ip:5000 -a Jimmy:secret -W buildbot
。有谁知道如何让 PB 监听变化?谢谢!
这是我的 master.cfg:
# -*- python -*-
# ex: set filetype=python:
import os
from buildbot.plugins import *
# This is a sample buildmaster config file. It must be installed as
# 'master.cfg' in your buildmaster's base directory.
# This is the dictionary that the buildmaster pays attention to. We also use
# a shorter alias to save typing.
c = BuildmasterConfig = {}
####### WORKERS
# The 'workers' 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['workers'] = [worker.Worker("example-worker", 'pass')]
if 'BUILDBOT_MQ_URL' in os.environ:
c['mq'] = {
'type' : 'wamp',
'router_url': os.environ['BUILDBOT_MQ_URL'],
'realm': os.environ.get('BUILDBOT_MQ_REALM', 'buildbot').decode('utf-8'),
'debug' : 'BUILDBOT_MQ_DEBUG' in os.environ,
'debug_websockets' : 'BUILDBOT_MQ_DEBUG' in os.environ,
'debug_lowlevel' : 'BUILDBOT_MQ_DEBUG' in os.environ,
}
# 'protocols' contains information about protocols which master will use for
# communicating with workers. You must define at least 'port' option that workers
# could connect to your master with this protocol.
# 'port' must match the value configured into the workers (with their
# --master option)
c['protocols'] = {'pb': {'port': os.environ.get("BUILDBOT_WORKER_PORT",9989)}}
####### CHANGESOURCES
# the 'change_source' setting tells the buildmaster how it should find out
# about source code changes. Here we point to the buildbot clone of pyflakes.
c['change_source'] = changes.PBChangeSource(port=9989 , user = 'Jimmy' , passwd = 'secret')
####### SCHEDULERS
# Configure the Schedulers, which decide how to react to incoming changes. In this
# case, just kick off a 'runtests' build
c['schedulers'] = []
c['schedulers'].append(schedulers.SingleBranchScheduler(
name="all",
change_filter=util.ChangeFilter(branch='master'),
treeStableTimer=None,
builderNames=["runtests"]))
c['schedulers'].append(schedulers.ForceScheduler(
name="force",
builderNames=["runtests"]))
####### BUILDERS
# The 'builders' 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 = util.BuildFactory()
# check out the source
# run the tests (note that this will require that 'trial' is installed)
factory.addStep(steps.ShellCommand(command=["ls" , ".."]))
c['builders'] = []
c['builders'].append(
util.BuilderConfig(name="runtests",
workernames=["example-worker"],
factory=factory))
####### STATUS TARGETS
# 'status' is a list of Status Targets. The results of each build will be
# pushed to these targets. buildbot/status/*.py has a variety to choose from,
# like IRC bots.
c['status'] = []
####### PROJECT IDENTITY
# the 'title' string will appear at the top of this buildbot installation's
# home pages (linked to the 'titleURL').
c['title'] = "dummy"
c['titleURL'] = "https://github.com/jimmykim1/dummy"
# the 'buildbotURL' string should point to the location where the buildbot's
# internal web server is visible. This typically uses the port number set in
# the 'www' entry below, but with an externally-visible host name which the
# buildbot cannot figure out without some help.
c['buildbotURL'] = os.environ.get("BUILDBOT_WEB_URL", "http://localhost:8010/")
# minimalistic config to activate new web UI
c['www'] = dict(port=os.environ.get("BUILDBOT_WEB_PORT", 8010),
plugins=dict(waterfall_view={}, console_view={}))
c['www']['change_hook_dialects'] = {
'github' : {
'secret' : 'himitsu',
'strict' : False,
}
}
####### DB URL
c['db'] = {
# This specifies what database buildbot uses to store its state. You can leave
# this at its default for all but the largest installations.
'db_url' : os.environ.get("BUILDBOT_DB_URL", "sqlite://").format(**os.environ),
}
最佳答案
问题与我的 docker-compose.yml 的配置有关。我必须在 ports
下为我的 buildmaster 列出“9989:9989”。现在建筑大师正在倾听。
关于docker - Buildmaster 不监听端口,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/51506073/
我正在尝试从我计算机上的 docker-compose 文件运行 Buildbot,使用 Buildbot 提供的 buildmaster 和 worker 的图像。我将buildmaster端口定义
我正在尝试使用 BuildMaster 部署我的一个网站,这个特定网站有数千个文件。当我需要部署到我的生产服务器时,有时只需要更改 1 或 2 个文件。有没有一种方法可以设置我的部署计划,以便它只将自
我有 2 个构建机器人,并且想在它们之间共享一个构建从站。构建机器人/主机都有不同的存储库。 有没有办法在多个构建机器人之间共享构建从站? 最佳答案 目前没有任何方法可以将单个 buildslave
我们正在使用 Jenkins Dependency-Track它报告说我们有易受攻击的依赖项。其中许多来 self 们包的深层子依赖性,因此我们没有直接升级包的选项。似乎这里正确的解决方案是使用 Ya
在我们的项目中,我们使用 Microsoft 规定的技术为每个环境提供了多个配置文件,如下所述: http://msdn.microsoft.com/en-us/library/dd465326.as
我是一名优秀的程序员,十分优秀!