Skip to content
This repository has been archived by the owner on Jul 31, 2022. It is now read-only.

AWS and Jenkins

Dylan Christopherson edited this page Aug 7, 2018 · 10 revisions

This is assuming you have Jenkins set up already and you have access to the web interface. These instructions are copied directly from the Jenkins configuration I'm using to launch Cfncluster.

Initial setup

-On the left side of the home page, select "New Item"

-Enter an item name and select "Freestyle project"

-Enter a description for the project

-Check mark "Discard old builds

-Under Strategy, select "Log Rotation"
-Days to keep builds "30"
-Max # of builds to keep "100"

-Check mark "Github project"

-Project url "https://github.com/open-mpi/aws-pmix-scale-testing/"  //Jenkins pulls code from here

Under "Build Environment"

-Check mark "Delete workspace before build starts"

-Check mark "Abort the build if it's stuck

-Time-out strategy "No Activity"

-timeout seconds "300"

-Time-out actions "Writing the build description"

    -Description "Aborted build: 5 minutes without output"

Under "Build" -In Execute shell, you'll want to put the following commands:

cd /path/to/here/aws-pmix-scale-testing/
/path/to/here/aws-pmix-scale-testing/launch.sh ${BUILD_NUMBER}  //BUILD_NUMBER is a Jenkins variable

The commands in the execute shell will be ran by Jenkins. These commands will run the launch.sh script and eventually the shutdown.sh script will run which will shut down the cluster.

Semi-important

If you are going to make changes to the launch scripts, if everything is integrated with Jenkins, the Jenkins user is the owner of those scripts. To make changes or even launch manually, switch to the Jenkins user:

sudo su - jenkins -s/bin/bash

Also make sure to sync with the s3 database

./sync.sh       //In the folder with the sync.sh file
Clone this wiki locally