We have continuous integration via [Jenkins](https://jenkins.io/) running at https://ci.lubuntu.me. This results in four PPAs that are available through the [~lubuntu-ci](https://launchpad.net/~lubuntu-ci) team on Launchpad.
Two branches are available:
1. **[Stable](https://launchpad.net/~lubuntu-ci/+archive/ubuntu/stable-ci)** builds the latest upstream release as defined in the packaging.
1. **[Unstable](https://launchpad.net/~lubuntu-ci/+archive/ubuntu/unstable-ci)** builds from the tip of upstream git, usually the `master` branch.
## How it works
Builds are triggered on Jenkins using the [CI Tooling](https://phab.lubuntu.me/source/ci-tooling/) and [CI Metadata](https://phab.lubuntu.me/source/ci-metadata/). These are published through the proposed PPAs which are not meant to be used. Then they run through [ppa-britney](https://phab.lubuntu.me/source/ppa-britney/) to essentially do the same [tests that Ubuntu does on proposed packages](https://wiki.ubuntu.com/ProposedMigration) before they are suitable for inclusion in the archive and are published to the release PPAs.
## When it happens
Stable builds happen when there are new pushes to Phabricator repos.
Unstable builds happen every day at 0500 UTC.
ppa-britney runs 6 times a day: 0100, 0500, 0900, 1300, 1700, and 2100 UTC.
## How it might be useful
* Keep a VM running with the unstable PPA and you'll essentially have a capture of upstream. This is great when filing upstream issues as our packages often lag behind.
* If there's a big round of packaging (say, a whole new LXQt release), the process necessarily will reveal any issues that might occur in Britney and it will allow for further testing.
* Pushing to Phabricator doesn't necessarily trigger an upload to the archive. If testing hadn't been done previously, it can be done at this time and makes for a nice alternative to publishing to a PPA.