Environments

Code repository

The code is stored in Bitbucket as a GIT repository. We are starting with a single one repository. If the system is growing and and the different domains need independent deployment we will spit in different repositories for each domain.

Go to Bitbucket repository ....

Branch Model 

We are using two main branches (develop and master) and feature branch merge policy via pull requests. Pushing into the main branches is not permitted. For any change a pull request is to be created.

Feature branches will be merged to the develop branch first. After successful testing and commitment a new pull requiest is to be created to merge the develop branch to the master.

Hotfix branches will be merged to the master branch first. A new pull request is to be created to merge the master to develop immediately if the bug (hotfix) is solved.

Go to pull requests ....

Go to the branching model settings ...

CI/CD Pipeline

We have definied two pipelines, one for the test environment and one for the production.

The Bitbucket Pipeline definition are stored in the repository root folder.

View bitbucket-pipelines.yml

After successful build the cloud functions are deployed to GCP using the Google deploy node module (@Attila more).

The Pipeline is calling our Google Chat space for development.

The GCP API key and the GChat URL are stored as repository variables.

Go to the Repository Variables ...

GCP Runtime Environments

The application is running in the Google Cloud (GCP) using Google Firebase products.

GCP Access

We are using the jh@jobelhome.com Google account. Please create an own Chrome profile for this account to avoid a mishmash with different account.

Go to the Firebase console ...

We created to similar but completely different projects for test and production.

GCP Service Account

To access service like GCP storage and Google Sheet API a GCP Service Account has been created. The credentials are stored in the Firestore Configuration root collection, for each environment a different one.

On the GCP Console under APIs & Services the Google Sheet API has been enabled.

Here you can create a service account: TEST PRODUCTION

The key file (open the credential, go to the keys tab) is to be downloaded.

This content of this file has been saved in the config / service account node.

To access the Google Sheet the client email is to be invited as an editor user in the sahre settings of the sheet.

Tutorial ....

GCP Payment and Cost Monitoring

Go to the Google Cloud Console ...

Go to the Billing ...

Go to Budgets & alerts

Click on a budget alert in the list

Now you can edit the alerts in the Set alert threshold rules

You can edit the percentages