counterweight/data-dwh-dbt-project
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

add file inventory

Browse source
This commit is contained in:
Pablo Martin 2025-04-02 16:10:12 +02:00
parent 38ee399156
commit 913f001465
1 changed files with 14 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

14
ci/README.md
View file

@ -39,3 +39,17 @@ If you don't have this, it probably means you need to review our Infrastructure
- Open a PR in Devops from the branch.
- If everything is fine, you should see in Devops the pipeline getting triggered automatically and walking through all the steps described in `.azure-pipelines.master.yml`.
- Once you make a commit to `master` or merge PR to `master`, you should also see pipelines getting triggered automatically `.azure-pipelines.master.yml`.
### What the hell are these files
A small inventory of the funky files here:
- `ci-vm-setup.sh`: executes some set up steps that are needed the first time you prepare the CI VM.
- `ci.env`: template for the `.env` file that needs to be placed in the CI VM.
- `ci.profiles.yml`: template for the dbt `profiles.yml` file that needs to be placed in the CI VM.
- `ci-requirements.txt`: CI specific Python packages that need to be installed in CI runs (but not for running or developing on this project).
- `docker-compose.yml`: the docker compose file that defines the Postgres that runs in the CI VM.
- `postgres-initial-setup.sql`: a SQL file that completes set up steps required in the CI Postgres in the one-off initial setup.
- `sqlfluff-check.sh`: a script to check a folder's SQL files and validate them. Fails if any SQL is not parseable.
- `.sqlfluff`: some config for sqlfluff.
- `build-master-artifacts.sh`: a script that generates the `manifest.json` for the master branch and places it in a target folder.
- `.azure-pipelines.blablabla.yml`: the actual pipeline definitions for Azure.