Skip to main content

Continuous testing / integration tool for the CubicWeb framework

Project description

README for apycot
=================

project home page: http://www.cubicweb.org/project/apycot
mercurial repository: http://www.logilab.org/src/cubes/apycot

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.

* Set pyro-server=yes in your instance's configuration file

* Create environment and test configuration entities through the web
ui of your instance(s) to describe what to test. (See `More
documentation`_)

* Modify password for the narval user for better security


On the bot host
---------------

* Install the narval-apycot package.

* edit /etc/narval.ini, or ~/etc/narval.ini when running
code from hg, to adjust the bot configuration. You can also generate
a stub configuration file using `narval rcfile > /etc/narval.ini`

* If using different user/password for the apycot bot in cubicweb
instances than default ones (higly recommended), indicate connection
information for each instance in a /etc/narval-cw-sources.ini file.
for instance ::

[cwo]
user=narval
password=apycot

[elo]
user=narval
password=apycot

where each section is the pyro name of an instance. You should
restrict read perms to this file aggressively.

* for those running from source, `narval/bin/narval` should be
in PATH

.. _`cubicweb book`: http://www.cubicweb.org/
.. _`tracker`: http://www.cubicweb.org/project/cubicweb-tracker

Once both sides are running, check both are properly registered in the
pyro name server by running

pyro-nsc listall

You should see your instance as 'cubicweb:...' and the bot as 'narval:...'.
or in /etc (narval from debian package). This
allows arbitrary password (it's recommended to change the default one), and
also have the nice effect that when your bot will be (re)started, it will connect
to each instance listed in this file to search for pending plans.



More documentation
``````````````````

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
python-projects@list.logilab.org mailing-list.

Project details


Release history Release notifications

History Node

3.4.2

History Node

3.4.1

History Node

3.4.0

History Node

3.3.0

History Node

3.2.2

History Node

3.2.1

History Node

3.2.0

History Node

3.0.1

History Node

3.0.0

This version
History Node

2.2.7

History Node

2.2.6

History Node

2.2.4

History Node

2.2.1

History Node

2.2.0

History Node

2.1.1

History Node

2.1.0

History Node

2.0.8

History Node

2.0.7

History Node

2.0.6

History Node

2.0.4

History Node

2.0.3

History Node

2.0.2

History Node

2.0.1

History Node

2.0.0

History Node

0.12.3

History Node

0.12.1

History Node

0.10.3

History Node

0.6.0

History Node

0.4.2

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Filename, size & hash SHA256 hash help File type Python version Upload date
apycot-2.2.7.tar.gz (118.3 kB) Copy SHA256 hash SHA256 Source None Jun 10, 2013

Supported by

Elastic Elastic Search Pingdom Pingdom Monitoring Google Google BigQuery Sentry Sentry Error logging CloudAMQP CloudAMQP RabbitMQ AWS AWS Cloud computing Fastly Fastly CDN DigiCert DigiCert EV certificate StatusPage StatusPage Status page