Skip to content

Public Repository for candidates to fork and push code to

Notifications You must be signed in to change notification settings

BradyPLC/devops-interview

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

12 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

DevOps Engineer - technical interview

Testing goals

With this test, we want to see your ability to create a CI/CD pipeline and supporting infrastructure from scratch, as well as your skills as a system administrator.

The application

The app is a simple weather lookup by user entered locations.

  • The app targets version 3.1 of the dotnet core sdk
  • The app is built using Blazor Server.
  • The app uses AccuWeather API for lcoations lookup
    • You will need to create a free account with AccuWeather in order to register an application and call their API.
  • The startup application is BradyWeather.Blazor.Server.csproj

At the end of the exercise the application should look like below.

Blazor Weather

The task

Your task is to automate the provisioning of resources that host the app provided. It should be hosted in a highly available and scalable web application hosted in Azure. A free account can be created here for Azure. In addition you are required to build and automate the deployment of the application provided. Please use github actions.

You should not have to spend any money to complete this exercise.

Your CI job should:

  • Investigate and understand which values need to be swapped as part of CICD pipeline. This needs to be done for the application to work.
  • Run when a branch is pushed to Github (you should fork this repository to your Github account).
  • Deploy to a target environment when the job is successful.
  • A clean and minimal working infrastructure is preferred.
  • Consider security.
  • Consider tests at all levels.

Submission

  • Fork the Brady repository provided to a public Github repository.
  • Your solution should be pushed here. Please do not submit PRs back to the main repository.
  • Include a README which desribes how the CI pipeline and any IAC works
  • A link to the site that has been deployed.

Bonus Points

  • Commit often - would rather see a history of trial and error than a single push.
  • Versioning of the deployment
  • Write some tests for code and integrate into pipeline

About

Public Repository for candidates to fork and push code to

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published