In this help:
We have built a complete website that has everything for you as a team to move through the day. Please read the information on the link below to see help on the website and how this works.
Yes, we have a scoreboard and yes, some of the venues have prizes, but the event is about learning. About experiencing things in a safe environment, that you can later use on your own premises.
Please focus on that. Try out new things, explore alternative solutions and work as a team to get the most out of the day.
The Post Mortem steps in every challenge are your chance to shine. Think about what you want to built to solve a challenge. The proctors can read and judge your post mortem. And, this as well counts for the prizes.
The proctors in all venues are spending their free time to give you a great day. They have done a lot of work to do this. They are experienced and knowledgable. Use them to answer your questions and to solve the challenges. They are happy to help!
THe scoreboard is built to show the status of your website and how you are doing as a team. You can also look at the scoreboard yourself by visiting https://scoreboard.gdbc-challenges.com.
When you click on the team you can see a timeline view of how your team is doing.
Find more information on the scoreboard on this page.
To understand how the scoring works, please check here.
The Blameless Post-Mortem aims to allow organisations or teams to view failures resulting from mistakes, errors, slips or lapses, with a perspective of learning; not only for the individual(s) who may have been implicated in the failure, but for the team and the organisation as a whole. Post-Mortems are a time to be transparent and honest and should not result in “sugar-coating” or omission of small details, nor should they result in a cycle of “witch-hunts” or “blaming & shaming”. There should be an open and honest intent to move forward from a failure rather than attributing blame, yet simultaneously ensuring accountability remains.
The main steps taken in conducting a blameless learning review are detailed below, however the overarching focus is best illustrated by avoiding statements such as: ”Jack (accidentally) caused the failure by deleting the entire source-code repository”, and by instead posing the more productive question: “How was it possible for anyone to delete the entire source-code repository?”
We have done an enormous amount of work to give you the best experience during Global DevOps Bootcamp. The resources in Azure, Azure DevOps, the control plane, the scoreboard and the challenges website are all there for you. Configured and provisioned. When you start a challenge things will start to fail. But, just as in real life and in your challenges things can go wrong. Also on our end. That's why this chapter on disaster recovery is here.
We run every disruption in a Docker container. When this container is started on 1 of our AKS clusters, you will see havoc in your website. When this does not work (can take some minutes), please go to your proctor. The proctors have an admin page in the challenges page, where they can start disruptions manually by running the Docker container locally.
If this also does not work, then you are on your own. The challenge describes what will happen to your website. You can then cause the disruption yourself, by performing the action we do automatically, or you just have to pretend "it happened". You can still perform the quick fix tasks and post mortem tasks to build a solution to overcome this.