New Hire Checklist

This checklist guides new developers through the onboarding process from your first week through receiving your PIV card.

The timeframes are not strict requirements; you will meet with the Onboarding team to provide updates along the way. This checklist is tailored to application and service developers, but many parts apply to infrastructure development as well.

First Week

Onboarding Requirements

  • Complete e-QIP form (confirm with Amy) and any other onboarding paperwork

  • Respond to and complete any requests related to your onboarding, clearance, or contract requirements. These take priority over any regular work — communicate with the Onboarding team

  • Meet the onboarding team members, introduced by the Onboarding PM. The Onboarding Product Owners (POs) provide mentorship and guidance throughout the process — consider them your "onboarding buddies"

  • Attend the Developer Onboarding presentation

Accounts Setup

  • Read through the Accounts page, focusing on the Early Onboarding Accounts section

Workstation Setup

The setup script does the setup, token, Maven, clone and docker login items below, plus the location-service build, in one run. You still need the credentials and the IDE license first.

  • Review and begin working through your personalized Slack Onboarding Canvas

  • Get a license for your preferred IDE (ask Amy Calvert or Jonathan Williams if you do not already have one). We mostly use IntelliJ IDEA

  • Ask the Onboarding team to share credentials for git access to coderepo.mobilehealth.va.gov (Bitbucket username and token)

  • Ask the Onboarding team to share credentials for dtr.mapsandbox.net (sandbox DTR username and token)

  • Ask the Onboarding team to share credentials for nexus.mobilehealth.va.gov (VA Nexus username and token)

  • Complete the Development Environment Setup

  • Follow the steps for setting up your Token and Environment Configuration

  • Follow the steps for setting up your Maven Configuration

  • Clone a repo — https://coderepo.mobilehealth.va.gov/scm/vdms/location-service.git. Use the Bitbucket credentials provided by the onboarding team to authenticate. To clone other services, see Service Repositories

  • Complete a docker login dtr.mapsandbox.net using the sandbox DTR credentials provided by the onboarding team

  • Test the authentication by running docker pull dtr.mapsandbox.net/ckm/callback-service:1.9.0

Build a Java Service

You should now have all your accounts set up to allow a local build and deployment. Orbstack (or Docker) and Kubernetes should be installed and running with sufficient allocated resources, as specified in the Development Environment Setup.

If all of your configuration is correct, you should have a successful build. If not, work with the onboarding team to resolve the issue.

You will see a warning at the end of the build that says The requested profile "with-skaffold" could not be activated because it does not exist. This is a side effect of the way the service pom file is constructed from tiles during the build process and is expected behavior. You can safely ignore it as long as the build completes successfully.

First Month

When You Have a PIV Card

  • Test your access to Crowd, Jira, Bitbucket, and the VA Wiki

  • Test your access to the MAP Sandbox DTR and Jenkins environments

  • Update your email address in Crowd to your Apothesource email (it defaults to your @va.gov address)

  • Create token values for your account credentials:

  • Verify your credentials are working by following the steps in the Token Verification Checklist

  • Follow the instructions to set up your Smart Card reader and access CAG

  • Access your VA email through Outlook — each week you must keep Outlook open for ~30 minutes to stay compliant with requirements

  • Access your SQA/Staging accounts by navigating to the Admin IDP Web URL. To maintain access, regularly log in through Admin IDP in the SQA/Staging environment

  • Access your Prod accounts by navigating to the Admin IDP Web URL. To maintain access, regularly log in through Admin IDP in the Prod environment. Be sure to access AppDynamics in production as well