For an understanding of what this team is going to be working on take a look at the product vision.
The Verify Team is focused on all the functionality with respect to Continuous Integration and Verification.
This team maps to Verify devops stage.
The following people are permanent members of the Verify Team:
|Elliot Rushton||Engineering Manager, Verify (CI)|
|Grzegorz Bizon||Senior Backend Engineer, Verify (CI)|
|Tomasz Maczukin||Backend Engineer, Verify (CI)|
|Matija Čupić||Junior Backend Engineer, Verify (CI)|
|Steve Azzopardi||Backend Engineer, Verify (CI)|
The following members of other functional teams are our stable counterparts:
|John Hampton||Frontend Engineering Manager, Release (CD) & Verify (CI)|
|John Northrup||Site Reliability Engineer, Verify & Release|
|Dimitrie Hoekstra||UX Designer, Release (CD) & Verify (CI) and Intern Product Manager, Packaging|
|Rayana Verissimo||Senior UX Designer, Release (CD) & Verify (CI)|
|Filipa Lacerda||Senior Frontend Engineer, Release (CD) & Verify (CI)|
|Brendan O'Leary||Senior Product Manager, Verify|
|New Vacancy - Elliot R. (Interim)||Engineering Manager, Verify (CI)|
|Scott Hampton||Frontend Engineer, Verify (CI)|
|Henri Philipps||Senior Site Reliability Engineer, Verify & Release|
Like most GitLab backened teams we spend a lot of time working in Rails on the main GitLab CE app, but we also do a lot of work in Go which is the language that GitLab Runner is written in. Familiarity with Docker and Kubernetes is also useful on our team.
Issues the Verify team works on have the ~"Verify" label. Issues that contribute to the verify stage of the devops toolchain have the ~"devops:verify" label.