Hyper.sh Slaves Plugin For Jenkins

This plugin allows to execute a jenkins job inside Hyper.sh container(s).

• Architecture
• Dependency
• About Image
• Usage
  • Config
    • Enable JNLP
    • hyper-commons-plugin Configuration
    • Job Configuration
  • Start Build
  • View Log
    • View Build Result
    • View Slave node log
    • View build container
  • Debug
    • Example

Architecture

Dependency

• maven 3.5+
• java sdk 8
• docker-slaves-plugin
• hyper-commons-plugin
• Hyper.sh credential (get from https://console.hyper.sh)
• Jenkins Server should have public ip

About Image

You can specify customized build image, but it should contain java and wget/curl

• java(required): run slave agent(slave.jar) to connect Jenkins master through JNLP.
• wget/curl(optional): download slave.jar from jenkins master. This ensures that slave agent version matched with the master. Download will be skipped when wget/curl is missing.

Several recommend base images:

• openjdk:8-jdk
• jenkinsci/slave
• hyperhq/jenkins-slave-golang

Usage

Config

Enable JNLP

Manage Jenkins -> Configure Global Security
  -> Enable security: checked
  -> TCP port for JNLP agents: Fixed 5000

hyper-commons-plugin Configuration

Manage Jenkins -> Configure System -> Hyper Config
  -> Access Key
  -> Secret Key

Manage Jenkins -> Configure System -> Hypercli Install
  -> Download Hypercli

Job Configuration

Select build image(Recommended Container Size: >=S2 )

Add build step

Start Build

Click Build Now

View Log

View Build Result

View Slave node log

View build container

Debug

If job failed, please check the following log:

• Check the “Console Output” in “Build history” of Job
• Check the Node log
• Check the Hyper.sh container log by execute “hyper logs <container_id>”

Example

Check the Consle Output

Then check the Node log(this will be deleted after job finished)

The cause maybe Hyper.sh container size is too small, or slave agent start failed.

You can check the Hyper.sh container log like this: