Skip to content

Latest commit

 

History

History
103 lines (88 loc) · 3.07 KB

developer-system-initialization.md

File metadata and controls

103 lines (88 loc) · 3.07 KB
Raw

Developer System Initialization

This is a guide to some first-time activities to run after installing the software in System Requirements.

Gradle setup

If your system's default java version is 17, you can skip this.

java --version
openjdk 17.0.5 2022-10-18
OpenJDK Runtime Environment GraalVM CE 22.3.0 (build 17.0.5+8-jvmci-22.3-b08)
OpenJDK 64-Bit Server VM GraalVM CE 22.3.0 (build 17.0.5+8-jvmci-22.3-b08, mixed mode, sharing)
...

Our build requires Java 17.

  • Ensure Java 17 is installed on your system
  • Find Java 17 home directory, e.g. on mac run: /usr/libexec/java_home -v 17
  • Create a Gradle properties file to point to this directory:
    • Globally for your workstation: ~/.gradle/gradle.properties
    • or, just in the Workbench repo: api/gradle.properties
    # gradle.properties
org.gradle.java.home={YOUR_PATH_TO_JDK17}

# Example:
$ cat api/gradle.properties
org.gradle.java.home=/usr/local/buildtools/java/jdk17

Gcloud Setup

After you've installed gcloud, login using your pmi-ops account:

gcloud auth login

Earlier editions of this document recommended choosing a default project, but this is no longer considered a best practice. Since we have many nearly identical and similarly-named GCP projects, you should instead pass --project=all-of-us-workbench-test to every gcloud command. The reasoning is that by using default projects via gcloud config set project you introduce the ability to operate on the wrong project silently.

Git Repository Initialization

To initialize the Git repository, run the following:

cd ~/my/repositories/directory/whever
git clone https://github.com/all-of-us/workbench
cd workbench
# We have a couple of dependencies pulled in via Git submodules,
# though this mechanism is being phased out. In the meantime, we need
# to run this on every clone (or on certain changes to the upstream
# repositories). 
git submodule update -f --init --recursive

git-secrets

Setup

Download the git-secrets tool. If you are on a mac, run:

  brew install git-secrets

If you are on Linux, run:

rm -rf git-secrets
git clone https://github.com/awslabs/git-secrets.git
cd git-secrets
sudo make install && sudo chmod o+rx /usr/local/bin/git-secrets
cd ..
rm -rf git-secrets

Running

git-secrets by default runs every time you make a commit. But if you want to manually scan:

The Repository

git secrets --scan

A File(s)

git secrets --scan /path/to/file (/other/path/to/file *)

A Directory (recursively)

git secrets --scan -r /path/to/directory

Initial Smoke Test

Before doing any development, you must run the following from /api:

./gradlew compileJava

Before compiling, this will also generate Java files from MapStruct and OpenAPI (Swagger) definitions which the app requires to compile. Depending on your personal development environment, you may need to frequently run ./gradlew clean compileJava to pick up MapStruct/OpenAPI changes, particularly when changing branches.