Manifest commits should result a Jenkins job build which generates an artifact - CI blocked

[davidewatson]

The reason we built careen is that we have some packages which require patches. For these packages we should have manifests and artifacts should be generated when the manifest changes. Initially docker will be the only manifest we test.

There are a few options for triggering the JJB job:

1. Careen changes
2. A manifest or patch file changes
3. ?

We need to select one and implement a JJB job to build artifacts and upload them to a well known location (presumably S3).

[davidewatson]

Versioning is hard. I am considering naming docker artifacts like so, docker-1.11.2+1cfe95fb.tar.gz, where docker is the name of the package, and 1.11.2+1cfe95fb is a SEMVER compliant version number. In this case 1.11.2 is the git tag of the docker repo, and 1cfe95f is the git commit hash of the careen repository used to build the docker source from a repository and patches. The tag version is important to convey API compatibility between docker artifacts. The commit hash is necessary to determine how and what source was built. Two problems this will not solve: 1) a manifest may combine multiple repositories (e.g. docker and runc), in which case what should the version number be? and 2) the build environment is not specified and some packages (e.g. runc) are not containerized. The later issue is less of a problem since we already agreed that careen does not aim to be a complete artifact management system - just a reproducible way to construct a set of source files.

[davidewatson]

OBE