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!
This project is part of:
Hack Week 11
Activity
Comments
Similar Projects
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