# packages

pkgId: c710c6ec1e43357abaa66cb78e61860b431ea3c015d9ccae9a204293367d5eca
name: jenkins-job-builder
arch: noarch
version: 1.4.1.dev50
epoch: 0
release: 1.el7.centos.ovirt
summary: Manage Jenkins jobs with YAML
url: http://ci.openstack.org/jjb.html
rpm_license: Apache License, Version 2.0
rpm_vendor: OpenStack Infrastructure Team <openstack-infra@lists.openstack.org>
rpm_group: Development/Libraries
rpm_buildhost: copr-builder-830402804.novalocal
rpm_sourcerpm: jenkins-job-builder-1.4.1.dev50-1.el7.centos.ovirt.src.rpm
location_href: 00156324-jenkins-job-builder/jenkins-job-builder-1.4.1.dev50-1.el7.centos.ovirt.noarch.rpm
checksum_type: sha256
description:
  README
  ======

  Jenkins Job Builder takes simple descriptions of Jenkins_ jobs in YAML_ format,
  and uses them to configure Jenkins. You can keep your job descriptions in human
  readable text format in a version control system to make changes and auditing
  easier. It also has a flexible template system, so creating many similarly
  configured jobs is easy.

  To install::

      $ sudo python setup.py install

  Online documentation:

  * http://ci.openstack.org/jenkins-job-builder/

  Developers
  ----------
  Bug report:

  * https://storyboard.openstack.org/#!/project/723

  Repository:

  * https://git.openstack.org/cgit/openstack-infra/jenkins-job-builder

  Cloning::

      git clone https://git.openstack.org/openstack-infra/jenkins-job-builder

  Patches are submitted via Gerrit at:

  * https://review.openstack.org/

  Please do not submit GitHub pull requests, they will be automatically closed.

  More details on how you can contribute is available on our wiki at:

  * http://docs.openstack.org/infra/manual/developers.html

  Writing a patch
  ---------------

  We ask that all code submissions be pep8_ and pyflakes_ clean.  The
  easiest way to do that is to run tox_ before submitting code for
  review in Gerrit.  It will run ``pep8`` and ``pyflakes`` in the same
  manner as the automated test suite that will run on proposed
  patchsets.

  When creating new YAML components, please observe the following style
  conventions:

  * All YAML identifiers (including component names and arguments)
    should be lower-case and multiple word identifiers should use
    hyphens.  E.g., "build-trigger".
  * The Python functions that implement components should have the same
    name as the YAML keyword, but should use underscores instead of
    hyphens. E.g., "build_trigger".

  This consistency will help users avoid simple mistakes when writing
  YAML, as well as developers when matching YAML components to Python
  implementation.

  Installing without setup.py
  ---------------------------

  For YAML support, you will need libyaml_ installed.

  Mac OS X::

      $ brew install libyaml

  Then install the required python packages using pip_::

      $ sudo pip install PyYAML python-jenkins

  .. _Jenkins: http://jenkins-ci.org/
  .. _YAML: http://www.yaml.org/
  .. _pep8: https://pypi.python.org/pypi/pep8
  .. _pyflakes: https://pypi.python.org/pypi/pyflakes
  .. _tox: https://testrun.org/tox
  .. _libyaml: http://pyyaml.org/wiki/LibYAML
  .. _pip: https://pypi.python.org/pypi/pip


pkgId: 4039500ee3ab14071d0c6764d4d05c92f7b984e1a6cc20fa0b8b617711bc9824
name: python-pbr
arch: noarch
version: 0.11.1.dev5
epoch: 0
release: 4.el7.centos
summary: Python Build Reasonableness
url: http://pypi.python.org/pypi/pbr
rpm_license: UNKNOWN
rpm_vendor: OpenStack <openstack-dev@lists.openstack.org>
rpm_group: Development/Libraries
rpm_buildhost: i-0003bc82
rpm_sourcerpm: python-pbr-0.11.1.dev5-4.el7.centos.src.rpm
location_href: python-pbr-0.11.1.dev5-4.fc21/python-pbr-0.11.1.dev5-4.el7.centos.noarch.rpm
checksum_type: sha256
description:
  Introduction
  ============

  PBR is a library that injects some useful and sensible default behaviors
  into your setuptools run. It started off life as the chunks of code that
  were copied between all of the `OpenStack`_ projects. Around the time that
  OpenStack hit 18 different projects each with at least 3 active branches,
  it seemed like a good time to make that code into a proper reusable library.

  PBR is only mildly configurable. The basic idea is that there's a decent
  way to run things and if you do, you should reap the rewards, because then
  it's simple and repeatable. If you want to do things differently, cool! But
  you've already got the power of Python at your fingertips, so you don't
  really need PBR.

  PBR builds on top of the work that `d2to1`_ started to provide for declarative
  configuration. `d2to1`_ is itself an implementation of the ideas behind
  `distutils2`_. Although `distutils2`_ is now abandoned in favor of work towards
  `PEP 426`_ and Metadata 2.0, declarative config is still a great idea and
  specifically important in trying to distribute setup code as a library
  when that library itself will alter how the setup is processed. As Metadata
  2.0 and other modern Python packaging PEPs come out, PBR aims to support
  them as quickly as possible.

  You can read more in `the documentation`_.

  Running Tests
  =============
  The testing system is based on a combination of `tox`_ and `testr`_. The canonical
  approach to running tests is to simply run the command ``tox``. This will
  create virtual environments, populate them with dependencies and run all of
  the tests that OpenStack CI systems run. Behind the scenes, tox is running
  ``testr run --parallel``, but is set up such that you can supply any additional
  testr arguments that are needed to tox. For example, you can run:
  ``tox -- --analyze-isolation`` to cause tox to tell testr to add
  ``--analyze-isolation`` to its argument list.

  It is also possible to run the tests inside of a virtual environment
  you have created, or it is possible that you have all of the dependencies
  installed locally already. If you'd like to go this route, the requirements
  are listed in ``requirements.txt`` and the requirements for testing are in
  ``test-requirements.txt``. Installing them via pip, for instance, is simply::

    pip install -r requirements.txt -r test-requirements.txt

  In you go this route, you can interact with the testr command directly.
  Running ``testr run`` will run the entire test suite. ``testr run --parallel``
  will run it in parallel (this is the default incantation tox uses). More
  information about testr can be found at: http://wiki.openstack.org/testr

  .. _OpenStack: https://www.openstack.org/
  .. _`the documentation`: http://docs.openstack.org/developer/pbr/
  .. _tox: http://tox.testrun.org/
  .. _d2to1: https://pypi.python.org/pypi/d2to1
  .. _distutils2: https://pypi.python.org/pypi/Distutils2
  .. _PEP 426: http://legacy.python.org/dev/peps/pep-0426/
  .. _testr: https://wiki.openstack.org/wiki/Testr


