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:

releasesalphaamd64armhppaia64mipsppcppc64ppc macoss390shsparcx86USE-Flagsdependenciesebuild 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-4.1.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
buildbot-3.11.9 -~-----------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
Legend:
+ stable
~ testing
- not available
some ebuild warning depend on specific use-flags or architectures, all ebuild-warnings are shown.

Tutorials:
no tutorial found


back