GitHub Actions Github has recently included the ability to define ‘actions’ or ‘workflows’ to execute on the repositories. The pros: It’s defined in a yaml inside the repository Allows defining secrets via the web UI for tokens, etc Extensive marketplace of actions and easily extensible Risu and GHA We’ve moved some of the CI in the repository from Travis to GHA to take advantage of this approach so now (check .

Time flies! Risu has been now around for three years! On June 11th 2017 I have created this project for automating manual checks that I had to perform over and over again. It was very simple shell script that iterated over directories and executed shell scripts in them. Soon after that, friends, colleagues started to use the program as well and provided feedback. We have reached out for help to one of our colleague Lars and asked if he had any ideas he could share with us to improve the program.

What’s new? Other posts in this category: What’s new General Extra plugin tree support: allows to specify alternate plugin tree (in addition to internal one) so that Risu can be integrated more easily with other solutions (for example, excluding Risuclient plugins and just listing the ones in the additional folder) Some minor fixes in documentation and plugins New logo!

What’s new? Other posts in this category: What’s new General Pie charts are now shown for profile reports, showing one ‘piece’ for each status of plugins reported, check www preview for a sample.

What’s new? Other posts in this category: What’s new General Improve handling of dates forcing LC_ALL Create a new function (thanks Mikel) to take from an ordered list of files the first_file_available and exits (because sometimes, depending on sosreport version it might have one file or another). Patternfly was updated to latest minor Other changes made to is_active and is_enabled Functions that were later enhanced to use first_file_available Test to detect issues with LEAPP in-place upgrade for EL7->EL8 if / and /var are on different device.

Time flies! Today, Risu makes the two years milestone. Last year we got this article on it. This year not a lot of changes happened compared to the last one: The amount of plugins have increased to 874 (counting internal ones) Updates to some plugins like lifecycle of new releases Our first Katacoda scenario on how to install and use it: How to use Risu Presentation on meetup Emerging Tech Valencia Thanks a lot for all your support during this period and counting on it for the years to come!

During the las months Risu team has not found any big issues or functionality that could be missed and worked mostly on performance improvements and some other tests. It was a good timing to align a new year with official release of Risu 1.0.0. We’ve recently also embraced a new telegram chat for our users via https://t.me/RisuUG to contact our team and for driving further development and evolution. Join us in celebrating 2009 with a new full set of opportunities and challenges to rise up!

What’s new? Other posts in this category: What’s new System information summary Thanks to the suggestion of a colleague, we’ve added ‘sysinfo’ as a ‘profile’. The idea of this, together with the RC_INFO code introduced is to leverage some scripts that report information relevant to the system being analyzed, that might or not be a problem, but still gives you context information about what you’re trying to diagnose. Based on this, and by adjusting sysinfo.

What’s new? Other posts in this category: What’s new General anonymizaton We’ve moved this to an independent function and updated the ‘–call-home ’ to use this function (but leaving sosreport path), so that the results can be aggregated later for checking trends on rules detecting issues, etc. metrics As part of above change, we’ve started a small spinoff that we want to integrate back into Nexus on grabbing metrics of execution we can later analyze.

What’s new? Other posts in this category: What’s new General RC_INFO We had discussions in the past about info that we could provide that was not really a Error. After some extra feedback we did add the RC_INFO exit code to the tests, so that for example xsos output is also provided with Risu results so that it can be quickly checked also from the Web UI overrides.json Allows to override fields in the results json with some values, for example to force updates of the titles, urls, etc in the results returned.