Updated
over 1 year
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/pull_requests_reminder @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
-
over 8 years ago by locilka | Reply
Bugzilla checker lives at: https://github.com/kobliha/bugzilla-tools
-
Similar Projects
Simple time scale for active record models by digitaltomm
[comment]: # (Please use the project descriptio...
Uyuni test suite improvements by dgedon
Project Description
Uyuni is the upstream...
Testing and adding GNU/Linux distributions on Uyuni by juliogonzalezgil
Join the Gitter channel! [https://gitter.im/uy...
obs_scm_demo by smithfarm
Project Description
For a long time, I ha...
Expanding e2e tests on Windows self-hosted runners via CI by iguimaraes
Achievements:
- Documented all necessary s...
OSSelot collaboration on legal reviews of community packages by lkocman
[comment]: # (Please use the project descriptio...