After today’s deployment we faced a downtime of our reference server. We want to give you some insight into what happened.
Read more...During yesterday’s deployment we faced some issues. We want to give you some insight into what happened.
Read more...During today's deployment we faced some issues. We had to disable rabbitmq support in build.opensuse.org for some hours.
Read more...During yesterday's deployment we faced some issues. We had to monkey patch some fixes and we want to give you some insight into what happened.
Read more...During deployment, we were facing some issues and build.opensuse.org was not accessible for a couple of minutes.
This sucks and that's why we want to give you some insight in what happened.
Read more...We did it again! Yesterday, on 19th of July 2017, we had an extended deployment time because of an issue during the deployment. Though this time it "only" took 15 minutes;-)
This sucks and that's why we want to give you some insight in what happened.
Read more...On June 30, 2017 we had an extended deployment time of roughly 45 minutes for our reference server because of a couple of problems with one of the data migrations. We implemented a new feature, user notifications via RSS, that included a migration of data in our database. This migration was broken, causing this deployment to go terribly wrong.
The frontend team afterward met to do a post-mortem to identify the problems, solutions and possible take aways for the future. This is the first post-mortem meeting we held, hopefully but not likely the last. Here goes the report.
Read more...