Skip to main content

Py-CI

Generic continuous integration server for interfacing with github and publishing results to a Media Wiki. The basic idea is that continuous integration just requires three things:

  • A repo to monitor for changes.

  • Unit tests to run.

  • A place to publish the results of the tests.

Py-CI interfaces with github using the pygithub API wrapper for interfacing with github’s API. It monitors the pull requests for a set of repos. When a new or untested pull request is found:

  • Create a local copy of the repo; merge the proposed changes from the pull request into a working branch.

  • Run all the unit tests specified in the repo.xml configuration file.

  • Post the results of running the unit tets to a media wiki.

Quickstart

If you already have a virtualenv installed as well as virtualenvwrapper, skip this next code block. However, be sure to add the VENV variable to the global configuration file.

pip install virtualenv
pip install virtualenvwrapper
mkvirtualenv ci

Next, copy the `global.xml <https://github.com/rosenbrockc/ci/wiki>`__ file and put it somewhere on you local disk (say ~/.ci.global.xml). Be sure to edit the values. Then:

export PYCI_XML="~/.ci.global.xml"
workon ci
pip install py-ci
sudo ci.py -setup

If you don’t see any errors, your server is ready to have repositories installed. This configures the server cron to run every minute. Use -cronfreq [int minutes] to change that frequency (see cron settings for details). You don’t need to use sudo for anything except setting the server up initially (or uninstalling it later with the -rollback switch). Next, create a `repo.xml <https://github.com/rosenbrockc/ci/wiki/Repository-Level-Settings>`__ file for repository you want to monitor. Suppose it exists at ~/repos/myrepo/ci.xml, then:

ci.py -install ~/repos/myrepo/ci.xml

Your repository will now be monitored for new pull requests forever untill you either -uninstall the repo.xml file or you -disable the CI server to temporarily suspend all requests. To understand the behavior of the CI server, read through the repository level settings page.

IMPORTANT: if your unit tests require environment variables to be set, they need to be added to a file called ~/.cron_profile that will be loaded by the CI server whenever the cron is run. See cron environment variables for more details.

Metadata

Release files for pyci 0.0.4

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for pyci 0.0.4
File Size Uploaded Provenance
pyci-0.0.4.tar.gz 29.6 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for pyci 0.0.4
File Interpreter ABI Platform
pyci-0.0.4-py2.py3-none-any.whl Python 3, Python 2 none any Details

Total release size: 70.6 kB

Release files / pyci-0.0.4.tar.gz

Download URL pyci-0.0.4.tar.gz
Size 29.6 kB
Tags Source
SHA-256 checksum
How to use checksums
1f3b67d01e47ac834081b1e32c0515a622a3248b6cfad5e583ea552ee1f7bb6a
BLAKE2b-256 checksum
How to use checksums
679dcc5beff1500c241a0b7ac8d4a634d57302991a6bfb2441b2eaba5ccc4e49
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Release files / pyci-0.0.4-py2.py3-none-any.whl

Download URL pyci-0.0.4-py2.py3-none-any.whl
Size 41.0 kB
Tags Python 2 Python 3
SHA-256 checksum
How to use checksums
a8fb744f5d3de419dc5d930c4773e8d55a9244218b4142550370c74f500af185
BLAKE2b-256 checksum
How to use checksums
fa6a323eb4817b0655811b54b89003a8d93cc30860f4e03f93b3cde3e48db773
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Security for pyci 0.0.4

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page