Difference between revisions of "Deployed to a repository"
(Created page with "== Release Deployments ==") |
(→Release Deployments) |
||
| Line 1: | Line 1: | ||
| + | |||
| + | This documents how we deploy our builds. | ||
| + | |||
| + | == CI Build Deployments == | ||
| + | |||
| + | When CI builds are created it usually gets deployed to [http://tarballs.openstack.org tarballs] file server. | ||
| + | |||
== Release Deployments == | == Release Deployments == | ||
| + | |||
| + | When tags are created the tagged build gets deployed to an appropriate repository depending on the type of project that is built. Here is a list of some of the repositories: | ||
| + | #. Python projects are deployed to [http://www.pypi.org pypi] | ||
| + | #. General Java projects are deployed to [http://oss.sonatype.org maven central] | ||
| + | #. Jenkins plugins are deployed to [http://repo.jenkins-ci.org jenkins repo] | ||
Revision as of 18:33, 2 December 2013
This documents how we deploy our builds.
CI Build Deployments
When CI builds are created it usually gets deployed to tarballs file server.
Release Deployments
When tags are created the tagged build gets deployed to an appropriate repository depending on the type of project that is built. Here is a list of some of the repositories:
- . Python projects are deployed to pypi
- . General Java projects are deployed to maven central
- . Jenkins plugins are deployed to jenkins repo
