gentoo.LinuxHowtos.org

Details of dev-util/buildbot:

Description: BuildBot build automation system
Homepage: https://buildbot.net/ https://github.com/buildbot/buildbot https://pypi.org/project/buildbot/

available versions:

releases	alpha	amd64	arm	hppa	ia64	mips	ppc	ppc64	ppc macos	s390	sh	sparc	x86	USE-Flags	dependencies	ebuild warnings
buildbot-9999	-	-	-	-	-	-	-	-	-	-	-	-	-	crypt docker examples irc test	show	Starting with buildbot-0.8.12-r2, more than one instance of buildmaster 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 buildmaster instance. In order to start the service running OpenRC-based systems need to link to the init file: ln --symbolic --relative /etc/init.d/buildmaster /etc/init.d/buildmaster.myinstance rc-update add buildmaster.myinstance default /etc/init.d/buildmaster.myinstance start Systems using systemd can do the following: systemctl enable buildmaster@myinstance.service systemctl enable buildmaster.target systemctl start buildmaster.target show
buildbot-3.11.1	-	+	-	-	-	-	-	-	-	-	-	-	-	crypt docker examples irc test	show	Starting with buildbot-0.8.12-r2, more than one instance of buildmaster 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 buildmaster instance. In order to start the service running OpenRC-based systems need to link to the init file: ln --symbolic --relative /etc/init.d/buildmaster /etc/init.d/buildmaster.myinstance rc-update add buildmaster.myinstance default /etc/init.d/buildmaster.myinstance start Systems using systemd can do the following: systemctl enable buildmaster@myinstance.service systemctl enable buildmaster.target systemctl start buildmaster.target show
buildbot-3.11.0	-	~	-	-	-	-	-	-	-	-	-	-	-	crypt docker examples irc test	show	Starting with buildbot-0.8.12-r2, more than one instance of buildmaster 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 buildmaster instance. In order to start the service running OpenRC-based systems need to link to the init file: ln --symbolic --relative /etc/init.d/buildmaster /etc/init.d/buildmaster.myinstance rc-update add buildmaster.myinstance default /etc/init.d/buildmaster.myinstance start Systems using systemd can do the following: systemctl enable buildmaster@myinstance.service systemctl enable buildmaster.target systemctl start buildmaster.target show

releases

alpha

amd64

arm

hppa

ia64

mips

ppc

ppc64

ppc macos

s390

sparc

x86

USE-Flags

dependencies

ebuild warnings

buildbot-9999

crypt
docker
examples
irc
test

Starting with buildbot-0.8.12-r2, more than one instance of buildmaster
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 buildmaster instance.
In order to start the service running OpenRC-based systems need to link to the init file:
    ln --symbolic --relative /etc/init.d/buildmaster /etc/init.d/buildmaster.myinstance
    rc-update add buildmaster.myinstance default
    /etc/init.d/buildmaster.myinstance start
Systems using systemd can do the following:
    systemctl enable buildmaster@myinstance.service
    systemctl enable buildmaster.target
    systemctl start buildmaster.target

show

buildbot-3.11.1

crypt
docker
examples
irc
test

Starting with buildbot-0.8.12-r2, more than one instance of buildmaster
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 buildmaster instance.
In order to start the service running OpenRC-based systems need to link to the init file:
    ln --symbolic --relative /etc/init.d/buildmaster /etc/init.d/buildmaster.myinstance
    rc-update add buildmaster.myinstance default
    /etc/init.d/buildmaster.myinstance start
Systems using systemd can do the following:
    systemctl enable buildmaster@myinstance.service
    systemctl enable buildmaster.target
    systemctl start buildmaster.target

show

buildbot-3.11.0

crypt
docker
examples
irc
test

Starting with buildbot-0.8.12-r2, more than one instance of buildmaster
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 buildmaster instance.
In order to start the service running OpenRC-based systems need to link to the init file:
    ln --symbolic --relative /etc/init.d/buildmaster /etc/init.d/buildmaster.myinstance
    rc-update add buildmaster.myinstance default
    /etc/init.d/buildmaster.myinstance start
Systems using systemd can do the following:
    systemctl enable buildmaster@myinstance.service
    systemctl enable buildmaster.target
    systemctl start buildmaster.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