Highlights of the OBS frontend development - Sprint 40
People of the Builds! Another Sprint is over and here is what the OBS frontend team has achieved in the last two weeks (2018-06-04 to 2018-06-15).
Last week we released OBS 2.9.3. This release mainly targeted two security issues found by Marcus Hüwe, and some other minor improvements. And thanks to Luca Boccassi this release includes a couple of patches for building packages for Debian.
New layout based on bootstrap
A lot of stuff has been going on regarding the layout of OBS. Last sprint we tested some frameworks that could be used. This sprint we agreed to use Bootstrap and what is more important: we can test our progress on implementing the new layout, step by step, thanks to PR#5120. Quoting the description of the same pull request: “For certain actions and certain users we want to switch to a new bootstrap based layout while for everyone else things should stay the same.”. Stay tuned because nice changes are going to arrive soon!
After discussing it in our last Onsite meeting we decided to use salt for the configuration of our production instance. We started using salt last sprint, and in this last two weeks we continued using it. In this sprint in particular we configured the mail server. In the future it will make it easier to manage all the services involved, and to prepare a more automated way of deployments.
Patchinfo removes data (II)
Following the work started in the last sprint another two elements were found not to be preserved after an edition of a patchinfo: package and releasetarget. This was fixed in PR#5079.
Fix rpmlint warnings of new OBS package
We are planning to use the awesome bundled gems service for building our obs-server packages. The bundle gem service includes all gems listed in a Gemfile and bundles them within the vendor directory of a rails project. With that we don’t have to package each gem individually, like we do right now. Well, truth is that most of the gems we use are linked from the devel:languages:ruby:extensions project. But it’s still some effort that continiously goes into that. Consider that we have use more than 200 gems for OBS.
There are a couple of steps involved to make this change. One of them is to silence and / or fix the rpmlint warnings. Rpmlint is a tool for checking common errors and potential issues in rpm packages. Since we are going to include all gems needed by OBS in our OBS packages, we got a lot of warnings caused by gem files. So this sprint we analyzed all these warnings and either solved or silenced them. In addition we also solved a couple rpmlint issues caused by our own packages, e.g., not recommending cron although we ship cron scripts.