You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Consider using larger runners or machines with greater resources for possible analysis time improvements.
28
+
runs-on: self-hosted
29
+
permissions:
30
+
# required for all workflows
31
+
security-events: write
32
+
33
+
# required to fetch internal or private CodeQL packs
34
+
packages: read
35
+
36
+
strategy:
37
+
fail-fast: false
38
+
matrix:
39
+
include:
40
+
- language: python
41
+
# CodeQL supports the following values keywords for 'language': 'c-cpp', 'csharp', 'go', 'java-kotlin', 'javascript-typescript', 'python', 'ruby', 'swift'
42
+
# Use `c-cpp` to analyze code written in C, C++ or both
43
+
# Use 'java-kotlin' to analyze code written in Java, Kotlin or both
44
+
# Use 'javascript-typescript' to analyze code written in JavaScript, TypeScript or both
45
+
# To learn more about changing the languages that are analyzed or customizing the build mode for your analysis,
46
+
# see https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning.
47
+
# If you are analyzing a compiled language, you can modify the 'build-mode' for that language to customize how
48
+
# your codebase is analyzed, see https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages
49
+
steps:
50
+
- name: Checkout repository
51
+
uses: actions/checkout@v4
52
+
53
+
# Initializes the CodeQL tools for scanning.
54
+
- name: Initialize CodeQL
55
+
uses: github/codeql-action/init@v3
56
+
with:
57
+
languages: ${{ matrix.language }}
58
+
build-mode: ${{ matrix.build-mode }}
59
+
# If you wish to specify custom queries, you can do so here or in a config file.
60
+
# By default, queries listed here will override any specified in a config file.
61
+
# Prefix the list here with "+" to use these queries and those in the config file.
62
+
63
+
# For more details on CodeQL's query packs, refer to: https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs
- Use option `--deploy-path` to run the container with a deploy path namespace (i.e: `--deploy-path=dhis2` serves `http://localhost:8080/dhis2`)
88
88
- Use option `-k`/`--keep-containers` to re-use existing docker containers, so data from the previous run will be kept.
89
89
- Use option `-auth` to pass the instance authentication (`USER:PASS`). It will be used to call post-tomcat scripts.
90
-
- Use option `--run-sql=DIRECTORY` to run SQL files (.sql, .sql.gz or .dump files) after the DB has been initialized.
90
+
- Use option `--run-sql=DIRECTORY` to run SQL files (.sql, .sql.gz or .dump files) after the DB has been initialized. SQL files containing "strict" in their name will cause `d2-docker start` to stop if an error occurs.
91
91
- Use option `--run-scripts=DIRECTORY` to run shell scripts (.sh) from a directory within the `dhis2-core` container. By default, a script is run **after** postgres starts (`host=db`, `port=5432`) but **before** Tomcat starts; if its filename starts with prefix "post", it will be run **after** Tomcat is available. `curl` and typical shell tools are available on that Alpine Linux environment. Note that the Dhis2 endpoint is always `http://localhost:8080/${deployPath}`, regardless of the public port that the instance is exposed to.
92
92
- Use option `--java-opts="JAVA_OPTS"` to override the default JAVA_OPTS for the Tomcat process. That's tipically used to set the maximum/initial Heap Memory size (for example: `--java-opts="-Xmx3500m -Xms2500m"`)
93
93
- Use option `--postgis-version=13-3.1-alpine` to specify the PostGIS version to use. By default, 10-2.5-alpine is used.
0 commit comments