Documents about integration of Hyper_ and Jenkins

• Introduction
• Comparison
• Usage
  • Prerequisites
  • Run Jenkins Server in Hyper_ Cloud
  • Use customized image
• User Cases

Introduction

Hyper_ Slaves Plugin allows to execute a jenkins job inside Hyper_ container.

When Jenkins Master build a Jenkins job, it will start a Hyper_ container as a Jenkins Slave node, The Slave agent connects to Jenkins Master via JNLP.

The Hyper_ container will be destroyed after Jenkins job is finished.

Comparison

Compare Hyper_ Slaves Plugin with Amazon EC2 Plugin and DigitalOcean Plugin.

Hyper_ Slaves Plugin can optimize performance and cost:

• Startup Slave Node faster: 3~10 seconds
• Cheaper to run Hyper_ container: per second billing

To view the detail, please click here.

Usage

Prerequisites

1. Jenkins Server 2.7.x LTS:

• install tool: hyper client
• install plugin: Hyper_ Slaves Plugin
• assign IP Address: Jenkins Server requires a public IP, so Jenkins Agent can connect to it.

2. Hyper_ Credential: Generate API Credential
3. Docker image: (build environment)

• jenkinsci/slave
• oracle/openjdk:8
• openjdk:8-jdk

Run Jenkins Server in Hyper_ Cloud

hyperhq/hyperkins is a pre-built docker image,

It's based on jenkins:2.7.4, the following contents has been installed:

• hyper client
• Hyper_ Slaves Plugin

To Run Jenkins Server in Hyper_ Cloud, please click here.

Use customized image

Here are some examples:

• hyperhq/jenkins-slave-centos
  • based on centos:7.2.1511, Dockerfile
• hyperhq/jenkins-slave-golang
  • for build golang project Dockerfile
• jenkins-slave-python
  • for build python project Dockerfile
• jenkins-slave-php
  • for build php project Dockerfile

To find all example images, please see this

User Cases

• Build Github Pull Request
• Call Remote Access API to trigger build