gentoo.LinuxHowtos.org

Details of dev-util/buildbot-worker:

Description: BuildBot Worker (slave) Daemon
Homepage: https://buildbot.net/ https://github.com/buildbot/buildbot https://pypi.org/project/buildbot-worker/

available versions:

releases	alpha	amd64	arm	hppa	ia64	mips	ppc	ppc64	ppc macos	s390	sh	sparc	x86	USE-Flags	dependencies	ebuild warnings
buildbot-worker-9999	-	-	-	-	-	-	-	-	-	-	-	-	-	test	show	More than one instance of a buildbot_worker can be run simultaneously. Note that \ is now the common base directory for all instances. If you are migrating from an older version, make sure that you copy the current contents of \ The name of the subdirectory corresponds to the name of the buildbot_worker instance. In order to start the service running OpenRC-based systems need to link to the init file: ln --symbolic --relative /etc/init.d/buildbot_worker /etc/init.d/buildbot_worker.myinstance rc-update add buildbot_worker.myinstance default /etc/init.d/buildbot_worker.myinstance start Systems using systemd can do the following: systemctl enable buildbot_worker@myinstance.service systemctl enable buildbot_worker.target systemctl start buildbot_worker.target show
buildbot-worker-3.11.1	-	+	-	-	-	-	-	-	-	-	-	~	-	test	show	More than one instance of a buildbot_worker can be run simultaneously. Note that \ is now the common base directory for all instances. If you are migrating from an older version, make sure that you copy the current contents of \ The name of the subdirectory corresponds to the name of the buildbot_worker instance. In order to start the service running OpenRC-based systems need to link to the init file: ln --symbolic --relative /etc/init.d/buildbot_worker /etc/init.d/buildbot_worker.myinstance rc-update add buildbot_worker.myinstance default /etc/init.d/buildbot_worker.myinstance start Systems using systemd can do the following: systemctl enable buildbot_worker@myinstance.service systemctl enable buildbot_worker.target systemctl start buildbot_worker.target show
buildbot-worker-3.11.0	-	+	-	-	-	-	-	-	-	-	-	~	-	test	show	More than one instance of a buildbot_worker can be run simultaneously. Note that \ is now the common base directory for all instances. If you are migrating from an older version, make sure that you copy the current contents of \ The name of the subdirectory corresponds to the name of the buildbot_worker instance. In order to start the service running OpenRC-based systems need to link to the init file: ln --symbolic --relative /etc/init.d/buildbot_worker /etc/init.d/buildbot_worker.myinstance rc-update add buildbot_worker.myinstance default /etc/init.d/buildbot_worker.myinstance start Systems using systemd can do the following: systemctl enable buildbot_worker@myinstance.service systemctl enable buildbot_worker.target systemctl start buildbot_worker.target show

releases

alpha

amd64

arm

hppa

ia64

mips

ppc

ppc64

ppc macos

s390

sparc

x86

USE-Flags

dependencies

ebuild warnings

buildbot-worker-9999

test

More than one instance of a buildbot_worker can be run simultaneously.
 Note that \
is now the common base directory for all instances. If you are migrating from an older
version, make sure that you copy the current contents of \
The name of the subdirectory corresponds to the name of the buildbot_worker instance.
In order to start the service running OpenRC-based systems need to link to the init file:
    ln --symbolic --relative /etc/init.d/buildbot_worker /etc/init.d/buildbot_worker.myinstance
    rc-update add buildbot_worker.myinstance default
    /etc/init.d/buildbot_worker.myinstance start
Systems using systemd can do the following:
    systemctl enable buildbot_worker@myinstance.service
    systemctl enable buildbot_worker.target
    systemctl start buildbot_worker.target

show

buildbot-worker-3.11.1

test

More than one instance of a buildbot_worker can be run simultaneously.
 Note that \
is now the common base directory for all instances. If you are migrating from an older
version, make sure that you copy the current contents of \
The name of the subdirectory corresponds to the name of the buildbot_worker instance.
In order to start the service running OpenRC-based systems need to link to the init file:
    ln --symbolic --relative /etc/init.d/buildbot_worker /etc/init.d/buildbot_worker.myinstance
    rc-update add buildbot_worker.myinstance default
    /etc/init.d/buildbot_worker.myinstance start
Systems using systemd can do the following:
    systemctl enable buildbot_worker@myinstance.service
    systemctl enable buildbot_worker.target
    systemctl start buildbot_worker.target

show

buildbot-worker-3.11.0

test

More than one instance of a buildbot_worker can be run simultaneously.
 Note that \
is now the common base directory for all instances. If you are migrating from an older
version, make sure that you copy the current contents of \
The name of the subdirectory corresponds to the name of the buildbot_worker instance.
In order to start the service running OpenRC-based systems need to link to the init file:
    ln --symbolic --relative /etc/init.d/buildbot_worker /etc/init.d/buildbot_worker.myinstance
    rc-update add buildbot_worker.myinstance default
    /etc/init.d/buildbot_worker.myinstance start
Systems using systemd can do the following:
    systemctl enable buildbot_worker@myinstance.service
    systemctl enable buildbot_worker.target
    systemctl start buildbot_worker.target

show

Legend:
+ stable
~ testing
- not available
some ebuild warning depend on specific use-flags or architectures, all ebuild-warnings are shown.

Tutorials:
no tutorial found