Automate to save time for hacking
a project by locilka
Updated over 3 years ago. 4 hacker ♥️.

Yast team has a great experience in automating tasks that can be done by machines in order to save time that can be used better. We usually use Jenkins for running these jobs.

Why to use automation?

  • It's error-prone
  • It runs 24 hours a day, even on weekends
  • It's much faster than humans
  • It can do all the boring stuff and never complains

Examples of automation

  • Open pull-requests reminder https://github.com/jreidinger/pullrequestsreminder @Jenkins
  • Auto-testing and auto submission to OBS/IBS for all now code via Packaging Tasks, e.g., @Jenkins

Ideas what can be automated further

  • Bugzilla is now able to set several NEEDINFO flags, one can be lost is so many e-mails and this simple tool would daily check for NEEDINFO pending (per user, per team, ...)
  • Even better are e-mails from FATE - this tool should, again, check for NEEDINFO flags and report them to you
  • Automatic generator of translations and auto-submitter to openSUSE
  • Any more ideas are welcome!

Join this project

Looking for hackers with the skills:

automation ruby bash github bugzilla fate

This project is part of:

Hack Week 11

Activity

  • over 9 years ago: evshmarnev liked this project.
  • about 11 years ago: mvidner liked this project.
  • about 11 years ago: schillingf liked this project.
  • about 11 years ago: locilka liked this project.
  • about 11 years ago: locilka added keyword "automation" to this project.
  • about 11 years ago: locilka added keyword "ruby" to this project.
  • about 11 years ago: locilka added keyword "bash" to this project.
  • about 11 years ago: locilka added keyword "github" to this project.
  • about 11 years ago: locilka added keyword "bugzilla" to this project.
  • about 11 years ago: locilka added keyword "fate" to this project.
  • about 11 years ago: locilka started this project.
  • about 11 years ago: locilka originated this project.


    • Comments

    • locilka
      about 11 years ago by locilka | Reply

      Bugzilla checker lives at: https://github.com/kobliha/bugzilla-tools

    • locilka
      almost 11 years ago by locilka | Reply

      And FATE checker has been added there as well

    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/

    Recipes catalog and calculator in Rails 8 by gfilippetti

    My wife needs a website to catalog and sell the products of her upcoming bakery, and I need to learn and practice modern Rails. So I'm using this Hack Week to build a modern store using the latest Ruby on Rails best practices, ideally up to the deployment.

    TO DO

    • Index page
    • Product page
    • Admin area -- Supplies calculator based on orders -- Orders notification
    • Authentication
    • Payment
    • Deployment

    Day 1

    As my Rails knowledge was pretty outdated and I had 0 experience with Turbo (wich I want to use in the app), I started following a turbo-rails course. I completed 5 of 11 chapters.

    Day 2

    Continued the course until chapter 8 and added live updates & an empty state to the app. I should finish the course on day 3 and start my own project with the knowledge from it.

    Hackweek 24

    For this Hackweek I'll continue this project, focusing on a Catalog/Calculator for my wife's recipes so she can use for her Café.

    Day 1

    OS self documentation, health check and troubleshooting by roseswe

    Project Description

    The aim of this hackweek project is to improve the utility "cfg2html" so that it is even more usable under SLES and perhaps also under Rancher.

    cfg2html (see also https://github.com/cfg2html/cfg2html) itself is a very mature utility for collecting and documenting information of an operating system like Linux, AIX, HP-UX and others.

    Goal for this Hackweek

    The aim is to extend cfg2html

    • for SLES and SLES-for-SAP apps, high availability
    • Improve code for MicroOS 5.x, SUMA, Edge and k8s environments
    • fix shellbeauity warnings
    • possibly add more plugins
    • SUMA/Salt integration to collect.

    Resources

    Required skills: Bash, shell script and the SUSE products mentioned.

    https://github.com/cfg2html/cfg2html

    https://www.cfg2html.com/

    SUSE Health Check Tools by roseswe

    SUSE HC Tools Overview

    A collection of tools written in Bash or Go 1.24++ to make life easier with handling of a bunch of tar.xz balls created by supportconfig.

    Background: For SUSE HC we receive a bunch of supportconfig tar balls to check them for misconfiguration, areas for improvement or future changes.

    Main focus on these HC are High Availability (pacemaker), SLES itself and SAP workloads, esp. around the SUSE best practices.

    Goals

    • Overall improvement of the tools
    • Adding new collectors
    • Add support for SLES16

    Resources

    csv2xls* example.sh go.mod listprodids.txt sumtext* trails.go README.md csv2xls.go exceltest.go go.sum m.sh* sumtext.go vercheck.py* config.ini csvfiles/ getrpm* listprodids* rpmdate.sh* sumxls* verdriver* credtest.go example.py getrpm.go listprodids.go sccfixer.sh* sumxls.go verdriver.go

    docollall.sh* extracthtml.go gethostnamectl* go.sum numastat.go cpuvul* extractcluster.go firmwarebug* gethostnamectl.go m.sh* numastattest.go cpuvul.go extracthtml* firmwarebug.go go.mod numastat* xtr_cib.sh*