Try to use Jenkins 2.0 CI environments to trigger jobs which running in openQA

Topic 1: Keep learning Jenkins CI jenkinsci

Topic 2: Learn the Oliver's hackweek topic

Topic 3: Monitor a repository once new image was included

Topic 4: Trigger the openQA jobs via Jenkins

Topic 5: ...etc.

Looking for hackers with the skills:

ci automation

This project is part of:

Hack Week 14

Activity

  • over 8 years ago: pgeorgiadis liked this project.
  • over 9 years ago: david_chang liked this project.
  • over 9 years ago: bchou added keyword "automation" to this project.
  • over 9 years ago: bchou added keyword "ci" to this project.
  • over 9 years ago: Jeffreycheung liked this project.
  • over 9 years ago: XGWang0 joined this project.
  • over 9 years ago: bchou started this project.
  • over 9 years ago: okurz liked this project.
  • over 9 years ago: evshmarnev liked this project.
  • over 9 years ago: bchou originated this project.

  • Comments

    • bchou
      over 9 years ago by bchou | Reply

      Refer to other topic:

      Windows 10 in openQA https://hackweek.suse.com/14/projects/1468

    • bchou
      over 9 years ago by bchou | Reply

      Thanks for helps :) Cowork with XGWang about Jenkins hacks and discuss the openQA questions with okurz and WeiJiang.

      Hackweek Result: (Target is achieved)

      • 1. use [ScriptTrigger] - Poll with a shell or batch script in Jenkins

      Monitor the repository in our office(http://$server-ipaddres/iso/) once a new image was included in the repo. Thanks XGWang to Re-write a buildmonitor.py to do this job.

      $python /home/john/buildmonitor.py -u http://$server-ipaddres/iso/SLE12-SP2/ -p SLE-12-SP2-Server

      • 2. use Build item(Execute shell) in Jenkins

      Run the openQA script here.

      ISO=cat ${WORKSPACE}/SLE-12-SP2-Server

      $/usr/share/openqa/script/client --apikey xxx --apisecret yyy isos post ISO=${ISO} DISTRI=sle VERSION=12-SP2 FLAVOR=Server-DVD ARCH=x8664 HDDSIZEGB=20 QEMUCOMPRESSQCOW2=1 TEST=sles12sp2image_make

    Similar Projects

    Bring to Cockpit + System Roles capabilities from YAST by miguelpc

    Bring to Cockpit + System Roles features from YAST

    Cockpit and System Roles have been added to SLES 16 There are several capabilities in YAST that are not yet present in Cockpit and System Roles We will follow the principle of "automate first, UI later" being System Roles the automation component and Cockpit the UI one.

    Goals

    The idea is to implement service configuration in System Roles and then add an UI to manage these in Cockpit. For some capabilities it will be required to have an specific Cockpit Module as they will interact with a reasource already configured.

    Resources

    A plan on capabilities missing and suggested implementation is available here: https://docs.google.com/spreadsheets/d/1ZhX-Ip9MKJNeKSYV3bSZG4Qc5giuY7XSV0U61Ecu9lo/edit

    Linux System Roles: https://linux-system-roles.github.io/