Since 2020-05-25 every day at 09AM UTC, we have a pipeline running that syncs the team members who started the day before to the team.yml file.
We fetch all the new team members with a start date of the previous day and check if they opted-in on
being synced to the team page. Opt-in happens by setting
Export Name/Location to Team Page? to
on their BambooHR profile. This is a task on day one for the new team member.
If they selected yes, we grab some data (name, job title, start date, department and country) and format it, so it can be added to the team page entry. If they did not opt-in, we still add an entry to the team page. However that entry is anonymized.
We then create a merge request on
www-gitlab-com project so it can be merged. The merge is not automatically set.
Considering this is a new sync we've added to the automation process we want to check the MRs before setting them to merge.
This check happens by the People Operations Engineer and the Senior Manager, People Operations.
Modern Health needs a weekly update about all our active
team members. This proces has been automated by using their
Upload to AWS S3 functionality. Every Friday
at 1PM UTC we run a scheduled job. This job fetches all the active team members from BambooHR and stores
the following in a CSV file:
This CSV file is then uploaded to a S3 bucket that is maintained by Modern Health. They process the file so the team members can have access to Modern Health
Currently that library covers:
The following results lead to failure of the pipeline:
If your job family fails but the wording used is valid, you can add your file to a list to be skipped. This file can be found on the same project here.
In the following video Lien Van Den Steen, People Ops Engineer talked with Kelly Murdock, Senior Recruiter how they can audit job families. The following is discussed: