Skip to content
This repository has been archived by the owner on Sep 18, 2021. It is now read-only.

Home

Jump to bottom
Jeremy Poulin edited this page Feb 9, 2018 · 14 revisions

Getting Started

The only current Jenkins instance equipped with the tools and configuration capable of running this test template is internal to RedHat. This guide assumes that you have admin access to this enviroment, or have been able to set up an equivalent environment with the Multi-Arch CI Provisioner installed.

Getting Access to a Testing Environment

  1. If you are a RedHat employee, you can file a ticket to get access to the Multi-Arch QE Jenkins environment.
  2. If you are trying to set up your own multi-arch capable testing system, you'll want to start by following the instructions to set up or integrate into your environment the Multi-Arch QE Provisioner.

Forking the Template

  1. In the github UI, fork this project. Forking on Github

Creating Your Own Jenkins Job

  1. Log in to Multi-Arch QE Jenkins. Logging in to Jenkins

  2. Navigate to your teams directory. You may need a create a directory for your team if one does not already exist. Navigating to Team's Directory

  3. Select new item. Creating a New Item

  4. Name your test. I recommend keeping the name lowercase and using dashes as delimiters between words, since the test name will be used as a directory name when it is run, and special characters have been known to cause problems because of this. Naming Your Test

  5. For pipeline type, select Multi-Branch Pipeline. Multi-Branch Pipeline

  6. Select OK at the bottom of the page.

  7. Under Branch Sources select Add source->Github. Adding Github Branch Source

  8. In the new Branch Sources->Git section, fill in the Project Repository filed with the Github URL of your fork of this project. Jenkinsfile Configuration

  9. Hit Save. This should scan the repo for branches and kickoff builds for each branch. Since you cloned the template, the only branch should be master. Expected Auto-Run Output

  10. The test will be run automatically with the default build parameters, so just by waiting for the test to complete you should see the results of the first build just by browsing to the job. The easiest way to visualize the progress of your builds is to select Blue Ocean. From here, you can navigate down to your branches and see the result for each arch. Once completed, you can also retrieve the build artifacts from this view. Visualizing with Blue Ocean Blue Ocean Branch View Blue Ocean Build View

Running the Test

  1. To run a the test manually, start by logging in to Multi-Arch QE Jenkins. Logging in to Jenkins
  2. Navigate to the test you want to run. Navigating to Team's Directory Selecting Your Job Selecting Your Branch
  3. In the left panel, select Build with Parameters. Build With Parameters
  4. Specify the ARCHES you want to build on. This parameter takes a list of arches delimited by ,. The supported arches are x86_64, ppc64le, aarch64, and s390x.
  5. Specify the node to run the test from. This defaults to master, but could be a static slave.
  6. Click Build.
Clone this wiki locally