Forge Home

ci_eye

Manage a CI-eye build radiator - http://netmelody.org/ci-eye/

10,069 downloads

9,772 latest version

1.8 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 0.1.0 (latest)
  • 0.0.2
  • 0.0.1
released Nov 4th 2014

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'KevinCorcoran-ci_eye', '0.1.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add KevinCorcoran-ci_eye
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install KevinCorcoran-ci_eye --version 0.1.0

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.

Download

Documentation

KevinCorcoran/ci_eye — version 0.1.0 Nov 4th 2014

ci_eye

Table of Contents

  1. Overview
  2. Module Description - What the module does and why it is useful
  3. Setup - The basics of getting started with ci_eye
  4. Usage - Configuration options and additional functionality
  5. Reference - An under-the-hood peek at what the module is doing and how
  6. Compatibility - OS compatibility, etc.

Overview

Manage a CI-eye server. CI-eye is a Continuous Integration build radiator.

Module Description

This module installs a CI-eye server. CI-eye is distributed as a single .jar file, so OS-level so there is no OS-level package/service, as such. However, this module uses the super-sweet java_service_wrapper module to manage CI-eye as a service.

Setup

What ci_eye affects

Service

  • ci_eye

Files

  • The CI-eye installation directory (default: /opt/ci-eye)
  • /root/.ci-eye/views.txt

Beginning with ci_eye

  • include ci_eye

Usage

You can configure the views displayed by CI-eye by setting a class parameter on the ci_eye class:

class { 'ci_eye' :
  views => [{ name => "Puppet Labs",
              projects => [{ type => 'JENKINS',
                             url => 'https://jenkins.puppetlabs.com',
                             name => 'Clojure Projects' },
                           { type => 'JENKINS',
                             url => 'https://jenkins.puppetlabs.com',
                             name => 'PuppetDB' }] },
            { name => 'Your awesome view',
              projects => [{ type => 'JENKINS',
                             url => 'http://your-jenkins-server.com',
                             url => 'http://teamcity.codebetter.com',
                             name => 'Amazing Code' }] }]
}

Images

This module does not (currently) manage any images displayed by CI-eye. CI-eye has good documentation on this. I've considered adding support for this, but it's not clear to me that it's useful.

Reference

Classes

  • ci_eye::params - defines the default parameter values
  • ci_eye::init
  • ci_eye::install - ensures that the CI-eye .jar is available on disk.
  • ci_eye::config - manages the CI-eye configuration
  • ci_eye::service - sets up the service wrapper and manages the CI-eye service.

Functions

  • build_ci_eye_config - constructs the contents of the views.txt file based on the $views class parameter.

Compatibility

It seems to work fine on CentOS 6, and I've yet to test it on anything else.