Continuous testing / integration tool for the CubicWeb framework
Installation and configuration
On the web/data server host
- Install cubicweb and the cubicweb-apycot packages (more info in the cubicweb book). Notice that the apycot cube may be integrated with tracker based instances.
- Create TestConfig / TestConfigGroup entities through the web ui of your instance(s) to describe what to test. (See More documentation)
- Modify password for the apycotbot user for better security
On the bot host
Install apycotbot package.
edit /etc/apycotbot.ini (or use apycotbot –generate-rcfile > /etc/apycotbot.ini to generate one) to adjust the bot configuration.
If using different user/password for the apycot bot in cubicweb instances than default ones (higly recommanded), indicates connection information for each instance in a /etc/apycotbot-cw-sources.ini file. for instance
[cwo] user=apycotbot password=apycot [elo] user=apycotbot password=apycot
where each section is the pyro name of an instance. You should restrict read perms to this file agressivly.
for those running from source, apycotbot/bin/apycotclient should be in PATH
Beside low-level installation (described here), all the documentation to setup your continuous integration environment is available online through your instance at http://<your instance url>/doc/apycot
Feedbacks, bug reports
Comments and bug reports are welcome on the firstname.lastname@example.org mailing-list.
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
|Filename, size||File type||Python version||Upload date||Hashes|
|Filename, size cubicweb-apycot-1.10.0.tar.gz (76.7 kB)||File type Source||Python version None||Upload date||Hashes View hashes|