| layout |
|---|
default |
You joined a team so it is time to get started. What can you expect when you press the button below to start with the Global DevOps Experience and start the Globoticket intranet
- You will land on the Globoticket intranet where you will find a list of news messages. You can open them and read them.
- The top message contains a small arrow next to read more. This is a special message as it is the trigger to start the challenge.
- When you press Mark as Read, you will get a call that you need to answer. Listen to the instructions and press "start challenge"
- You will be navigate to a GitHub repo. We have provisioned a repository, pipelines and full deployed azure enviroment with the running globoticket website at https://teamname.globoticket.com
- Go through the challenge. Ask help by using the GitOps command /help, /expert-tip, /fix, /verify, /finish in the comments of the issue. You can execute the /verify multiple times
- Once done you can start a new challenge on the intranet
- More information you can find in the Participant Manual.
- Have fun!
To get started with the event, visit the intranet.
You will be onboarded as employees of Globoticket, and will also go through the challenges as such. In this manual we describe the flow of the challenges in detail You can also watch the video that explains this here.
In the previous page you selected a team and now you are on this page. Here we will explain the mechanics of the event. Read through the documentation. You can always come back to this page by clicking Helpdesk button on the Globoticket Intranet.
When you leave this page, after you clicked the [Go to the Intranet portal] button, you will be redirected to the Globoticket Intranet. You can always navigate there in the browser as well.
On the Globoticket Intranet you can find news of Globoticket. You can also see some buttons on top:
Helpdesk- This brings you back to the previous page and explains the mechanics and most important commands.Scoreboard- it shows the Scoreboard. It shows your and other teams' score and other.Directory- It shows some people from Globoticket.Team repository- It shows the name of your team, and a link to our repository
The intranet contains news messages. The most important ones are marked with an icon. You can read the news messages. The top messages are most important because they are the start of the challenges. The news provides you with the context.
Once you read the context, you can press "Mark as Read". This is the trigger to get started. You will get a call from one of the people at Globoticket with some information on your challenge. Once the person hangs up you can press Start Challenge. You will be redirected to your Repository on GitHub that is created for you!
After the call you will be redirected to the GitHub Issues. In the issues you will see an issue Challenge <number> <Title>. Click the issue and read the instructions.
The instructions contain Acceptance Criteria. This is what you need to do!
Before you can get more instructions from your colleague Alex Fletcher, there needs to be a Wiki in the repository. You can create this by navigating to Wiki, click Create the first page. And then press Save page.
Shortly after the issue is created and the wiki is present, you will get guidance from Alex Fletcher. He will provide you with instructions.
To make sure all people know where to get their resources, we created a GitHub Issue Team Info. This contains all secrets, etc. that are needed. THIS IS NOT BEST PRACTICE!!! DO NOT DO THIS NORMALLY!
Globoticket has a full Microservice based website that you can find on https://teamname.globoticket.com
To make sure you can finish the challenge and be successful, you can put comments in the issue at hand. When you put a comment like below, the people will respond:
/help- Alex will give a tip or hint. This can be a blog, a link, or just hints./expert-tip- A detailed Wiki page with step-by-step instructions will be presented to finish the challenge./verify- The acceptance criteria will be checked. Jordan Sparks will show what has been checked, what is OK, and what is not OK. Some things cannot be verified. Verify will also add the score to the scoreboard./fix- If people cannot make it, they can use/fix. A Pull Request with code and instructions will be presented for them to merge./finish- Close the issue, finish the challenge, and go back to the intranet.
If you cannot finish, or want to continue, make sure you fix the challenge, as you might need the code from the current challenge. The /fix command will provide you with a branch, a Pull Request, and instructions to fix the challenge.
If you are done, you can run /verify to see if everything is correct.
If you are done or want to move on, run /verify. This does not end the challenge but merely checks your progress. To end the current challenge and move on to the next, type /finish as an issue comment. This will close the issue, and challenge and allow you to start the next one.
The challenges are in sequence so you need to go through them all. To give a bit of impression on what you are going to learn:
- Challenge 1 - GitHub Codespaces
- Challenge 2 - Actions and controlled Deployments
- Challenge 3 - Using GitHub Copilot
- Challenge 4 - Using GitHub Advanced Security
- Challenge 5 - Using Semantic Kernel and OpenAI
- Challenge 6 - Using Semantic Kernel and RAG
Have a different question and can’t find the answer you’re looking for? Reach out to your local proctor.
- We cannot see the wiki?
- Our automation created an empty Wiki page for you that will automatically be filled with more instructions. If somehow the wiki is not created, you will be notified by Alex Fletcher with instruction to create the wiki. You can create this by navigating to Wiki, click `Create the first page` . And then press `Save page`.
You can find some more instructions on how to do that here! - How can I continue to the next challenge?
- The challenges are in sequence and in some cases, you need things from a challenge to be implemented to be able to continue to the next challenge. The best way to move forward is to run the `/fix` command in the comment of your issue. Then a Pull Request will be provided with a branch that contains all the code you need. You can then merge the code to your main branch. Sometimes there are manual instructions you need to complete or a script you need to run to be able to fix it. After that, run the `/finish` command. It will end the challenge and open the next one.
- How do I start a challenge?
- The news messages on the Globoticket Intranet are the start triggers for the challenges. A news message has an icon next to it. You can read the news message, and press "Mark as Read". This will start a challenge.
- How do I switch teams?
- If you want to switch to another team, you can go back to the Event Day page of the Global DevOps Experience website and press the button "Join the event". This will show the teams available in the venue. Just select a new team and press "Start the event".
- What if I don't know how to proceed?
- There are multiple self-service help features built into the platform, but there are also proctors in the venue that you can ask to help you out!
/help- Alex will give a tip or hint. This can be a blog, a link, or just hints.
/expert-tip- A detailed Wiki page with step-by-step instructions will be presented to finish the challenge.
/verify- The acceptance criteria will be checked. Jordan Sparks will show what has been checked, what is OK, and what is not OK. Some things cannot be verified. Verify will also add the score to the scoreboard.
/fix- If people cannot make it, they can use/fix. A PR with code and instructions will be presented for them to merge.
/finish- Close the issue, finish the challenge, and go back to the intranet. - How does the score work?
-
- Points will be handed out per team per challenge.
- Team gets
20 points(+20) for every check in the acceptance criteria that is green when doing/verify. /helpdeducts score by 20 points (-20)./expert-tipdeducts score by 30 points (-30).- When using
/fixyou get 0 points for the challenge.
- How do I login to Azure?
- Every team has been provided with a GitHub repository with code and pipelines and issues. There is also an Azure environment that has the running Globoticket website. To log in to Azure, you need an Entra ID. The credentials can be found in the GitHub Issue called [Team Info] in your team repository. Typically the username looks like
[email protected]and the password is also stated in that issue. - How can I get my credentials?
- Every team has been provided with a GitHub repository with code and pipelines and issues. There is also an Azure environment that has the running Globoticket website. To log in to Azure, you need an Entra ID. The credentials can be found in the GitHub Issue called [Team Info] in your team repository.
- How can my codespace access all these resources?
- When we provisioned your GitHub repository we also added the most important secrets as a codespace secret in your repo settings. This way you can run without any issues.
- How do I get access to OpenAI?
- We have a number of OpenAI instances running to use in challenge 5 and 6. To get a key to this, we have a proxy tool to hand out keys in a balanced manner. To get a token from Azure OpenAI we use our own central proxy at https://openai.globoticket.com/event/2bbe-5922. You can go to it and authenticate with your GitHub Account. The 'Login in with GitHub' is on the top right. After registering you can scroll down and find the URL and API token you can use to connect to our API.
- How do I get access to Copilot?
- We use GitHub Copilot vouchers. We handed out codes to every venue. When you start Challenge 3, instructions will be provided on how to redeem this Copilot voucher and the code that you can use for that.
- Can I run multiple codespaces?
- Yes, you can run with multiple participants.
- Should I work alone or in a team?
- Global DevOps Experience is all about learning. And the best way to learn is from others. So we highly recommend working in teams. When you work as a team let one person be the driver and solve the challenges with each other. Switch drivers once in a while to let other people participate as well.
- What is Globoticket?
- Globoticket is a fictive company that sells concert tickets online. They need to ramp up their business and they want to become a more developer-centric company.
- Who are Emily, Morgan, Robert, Jordan and Alex?
- These are fictive personas that work at Globoticket.
- Why is Emily telling me to move on after 40 minutes?
- We want you to learn as much as possible. Because a day is short, and we have 6 great challenges for you, we give you a hint after 40 minutes that you can always move on by using the
/fixcommand. This is not required, but merely a heads-up. We want you to see and experience it all! - I did /fix but my code did not change
- The
/fixcommand actually creates a PR and a branch. After running the command, navigate to Pull Request and merge the changes and execute the proposed instructions. - I added stuff in the repo but I do not see it in the codespace
- A codespace is just like a normal IDE connected to Git. To get changes from the repository and to push changes to the repository, you need to do
git pullandgit push. Just like normal. - Who are the organizers?
- Global DevOps Experience is a community event powered by Xebia and sponsored by GitHub and Microsoft.
- How do I get detailed instructions to fix a challenge?
- To get a detailed step-by-step instruction you can run the
/expert-tipcommand in the issue comment. - Will I get access to this after the event?
- No. We provision the materials only on June 15th. It costs a lot of money to keep it up and running.
- I cannot log in with my account to enter the event
- Register yourself at your venue again, or let somebody else join instead. There is no need for all teammembers to log in and work isolated.
