Highlights of the OBS frontend development – Sprint 17
We are back!
Since we were preparing for OSC17 we had a little break and suspended our SCRUM sprint for one week. Now we are back! And this is what we have accomplished in sprint 17 (2017-05-29 to 2017-06-09).
It's been a month now, since we started to deploy the rails frontend more frequently. On some days we now deploy multiple times a day. Since this is quite different from what we did before (1 - 2 deployment every two weeks), we have a lot to learn and keep updating our deployment process.
Though this doesn't mean that OBS will be unavailable whenever we deploy. Most of the times we can keep OBS running while deploying the newest codebase. In the rare cases we have to set OBS into maintenance mode, we will drop you a note in IRC.
Blog about the STUDIO import/export feature
Build Schedule Reason on WebUI
Sometimes you want to know why a build got scheduled. For this you can now watch the build reason of a built package. Just go to a package's binary page, via the repository link in the build results, and click the "Build reason" link.
Migrating tests to RSpec
We continued moving tests to our new RSpec based test suite. This sprint we've migrated:
Fix storing last login time of users
The data in the last_logged_in_at field for users was not set in the case of using proxy mode for athentication. We fixed this now. To make sure this won't happen again we added tests for all authentication modes OBS supports.
Get rid of BsRequest.collection
We have refactored the methods that use BsRequest.collection to use the new relationships and scopes. Now the code is more readable and less complex to understand. Have a look on the follows PR's: